SalesforceLabs / survey-force

86 stars 61 forks source link

Feature request: Link Survey Taker to other object(s) #139

Open charles-thompson-salesforce-com opened 2 years ago

charles-thompson-salesforce-com commented 2 years ago

I have a need to attach surveys to Voice Call records.

My customer is implementing Service Cloud Voice and wants a survey to go out to the customer after a voice call. This is recorded in a Voice Call object and I'd like to avoid having to create a Case record just so that the survey can be associated with this customer interaction.

I expect this will require a new custom lookup on Survey Taker, a new parameter in the URL and some Apex code change to get the parameter and pass it to the Survey Taker.

clemfernandez commented 2 years ago

Need the exact same feature, will try to implement it and keep you updated if successful

jrattanpal commented 2 years ago

I talk about this at https://github.com/SalesforceLabs/survey-force/issues/85. You can take a look and see how you can do it. You need to add minimal code to add another object

charles-thompson-salesforce-com commented 2 years ago

Thanks, @jrattanpal!

Yes, this is a good conversation. As we expand on our Service Cloud channels, we should support non-Case customer interactions such as Bot conversations, voice calls, chat transcripts and social posts. These are all supported currently only if you create and match a Case record for each one. For high-volume customers, this adds significantly to storage usage.

Linking Survey Takers to other such records would be great long-term enhancement for SurveyForce.

Dhruv-Ladani commented 5 months ago

@jrattanpal and @charles-thompson-salesforce-com is there limitation for custom object? Like currently I have added lookup of one custom object in Survey Taker object and done changes in code as mentioned in #85, now i am adding another custom object lookup and modified code but it's giving error while submitting survey that Invalid Id. FYI, I have removed new custom object lookup from code and only keep previous loookup then it works fine. It gives issue when there is two custom object lookup.

jrattanpal commented 5 months ago

I replied this in the other issue that you created