We would love the ability to link a CTA that is created in Gainsight to the Opportunity in Salesforce. Currently, the only option is for the Opp to be linked to the CTA and have it only appear in Gainsight (and not in SFDC).
The use case is:
When a CSM creates a CTA in Cockpit and logs a task, that does sync to Salesforce and appears in the Activities section, which is great. However, the issue is that the log in SFDC shows that the "Related To" field is whatever that CTAs name was. Instead, we would want that field to be synced to the correct opportunity in SFDC.
So, for example, a CTA was created with a name of 'Opt Out Tomorrow'. The activity/task would be logged in SFDC with the "Related To" field = 'Opt Out Tomorrow'. However, there is no way to tell what opportunity within the account this is for. If, there was a way to sync this to the correct opp, so for this example, the "Related To" fieldin SFDC would reference the opportunity of "Renewal 1".
We need this because our company works out of the Opportunity page and it would be a great benefit for everyone to be able to associate these tasks to specific opps. This is due to our opps being yearly renewals and we want the ability to consolidate on an annual basis. This would allow for better tracking of CSM activities and lead to a higher adoption rate.
I have not been able to figure out a way to do this yet. Would love some help!
+2Hi Manmeet, have you checked out the functionality to link objects (including opportunities) to CTAs? This article has the details: https://support.gainsight.com/Product_Documentation/CTAS_Tasks_and_Playbooks/Admin_Configuration/Con...
Hi Dan,
I have looked that article over. My understanding was that is more for getting the opportunity from SFDC into the CTA view in Cockpit?
Would the bidirectional association option allow for the CTA to be linked/pushed to the correct Opportunity in SF? So, instead of the "Related To" field in SF containing the name of the CTA, it would link/push it to the Opportunity?
I have looked that article over. My understanding was that is more for getting the opportunity from SFDC into the CTA view in Cockpit?
Would the bidirectional association option allow for the CTA to be linked/pushed to the correct Opportunity in SF? So, instead of the "Related To" field in SF containing the name of the CTA, it would link/push it to the Opportunity?
+2It will essentially let you 1) establish a link to another SFDC/Gainsight object 2) view and/or edit fields from that linked object directly in the CTA detail window and 3) report on the associations.
You can see some more details in the second half of this recorded webinar: https://vimeo.com/217883313
And your Gainsight CSM would be happy to provide some more guidance specific to your environment/use cases.
You can see some more details in the second half of this recorded webinar: https://vimeo.com/217883313
And your Gainsight CSM would be happy to provide some more guidance specific to your environment/use cases.
Thanks for the response!
Not sure if this would help in what we need. Basically, the issue is that when the Tasks (from the CTA) log back into SFDC, under the 'Activity History' section.. that the "Related To" field for that Task references the CTA name. For example, if the CTA name was "Opt Out Tomorrow" and the task was to "Call Joe", when that task syncs to SFDC, the "Related To" field just references the CTA name mentioned above.
What we would like is for this "Related To" field to reference the Opportunity, the Opp would be the one that is linked to the CTA using the CTA Linked Objects functionality you provided documentation on.
Not sure if this is possible or not?
Not sure if this would help in what we need. Basically, the issue is that when the Tasks (from the CTA) log back into SFDC, under the 'Activity History' section.. that the "Related To" field for that Task references the CTA name. For example, if the CTA name was "Opt Out Tomorrow" and the task was to "Call Joe", when that task syncs to SFDC, the "Related To" field just references the CTA name mentioned above.
What we would like is for this "Related To" field to reference the Opportunity, the Opp would be the one that is linked to the CTA using the CTA Linked Objects functionality you provided documentation on.
Not sure if this is possible or not?
+1While this is not possible out of the box, you could achieve this using a rule that would read tasks under CTAs linked to Opportunity and then create tasks where "Related to" is mapped to the corresponding opportunity.
Few more detail on how to setup the rule is available here - https://community.gainsight.com/gainsight/topics/ability-to-be-able-to-log-a-call-in-gainsight
Few more detail on how to setup the rule is available here - https://community.gainsight.com/gainsight/topics/ability-to-be-able-to-log-a-call-in-gainsight
Hi Sidhu,
Thanks for the response. I am reading through that set up and don't quite understand how to apply it to my situation. Could you provide a little assistance, if possible?
So the rule would be to 'Load to SFDC Object', where I would be pushing the linked Opportunity from Gainsight to the "Related To" field in SFDC? Not sure exactly how to set that up though.
Also, reading through that link, it seems like this would only work for Closed CTAs, is that correct? We would need it to be for both Open and Closed CTAs.
Thanks for the response. I am reading through that set up and don't quite understand how to apply it to my situation. Could you provide a little assistance, if possible?
So the rule would be to 'Load to SFDC Object', where I would be pushing the linked Opportunity from Gainsight to the "Related To" field in SFDC? Not sure exactly how to set that up though.
Also, reading through that link, it seems like this would only work for Closed CTAs, is that correct? We would need it to be for both Open and Closed CTAs.
1 person likes this
+2Hi Manmeet,
I'm providing a few steps below that I think should address your problem:
Hope this helps!
PS: If further changes are made to Gainsight Tasks (change of status, for example), 'Related To' would revert to its original value (CTA). But this should change as soon as the rule runs again. Possible to work around this by creating a custom Opportunity lookup in Salesforce to write to.
Thanks,
Manu
I'm providing a few steps below that I think should address your problem:
- Let Gainsight Tasks sync to Salesforce the way they are already -- manually or automatically, with field mapping configured under Admin -> Tasks.
- Create a Data Space on our 'CS Task' object, and make sure we are pulling in: (1) 'CS Task -> Related Record Id' to find the corresponding Salesforce Task; and (2) 'CS Task -> Call To Action -> Opportunity Id' to extract the Opportunity the CTA is linked to.
- Build a rule and use the above Data Space as your source. We can filter for records where 'Related Record Id' is not null, to restrict to only those Gainsight Tasks that have been synced to Salesforce.
- The action of this rule would be 'Load to SFDC Object' as you pointed out. But we'd only have to 'update' existing records, not create new. 'Related Record Id' works as the unique identifier, and 'Opportunity Id' is mapped to 'Related To'.
Hope this helps!
PS: If further changes are made to Gainsight Tasks (change of status, for example), 'Related To' would revert to its original value (CTA). But this should change as soon as the rule runs again. Possible to work around this by creating a custom Opportunity lookup in Salesforce to write to.
Thanks,
Manu
Thanks for the detailed response, I appreciate the help! Since the Opportunity ID is being mapped to the 'Related To' field in SFDC, would the Id populate that or would the actual name of the Opp appear?
I will give this a try to see if this gets us what we need. Thanks!
Our SFDC Admin was able to set up rules in SFDC, that allowed for the Opportunity to be linked to the Task in the 'Related To' field, the only issue being that it would only populate that field if the Opportunity was already linked to the CTA using the Linked Object option in GS. Causing any CTAs with Playbooks associated to not sync those associated tasks to SFDC because the Opp was linked after creation.
I will give this a try to see if this gets us what we need. Thanks!
Our SFDC Admin was able to set up rules in SFDC, that allowed for the Opportunity to be linked to the Task in the 'Related To' field, the only issue being that it would only populate that field if the Opportunity was already linked to the CTA using the Linked Object option in GS. Causing any CTAs with Playbooks associated to not sync those associated tasks to SFDC because the Opp was linked after creation.
+2Once the Id is populated, you should the see the actual name in Salesforce, like so:
1 person likes this
Sounds good, thank you for the help! I will try and set this up and see if this works out for us. Appreciate the assistance.
1 person likes this
Really interesting thread. Could the same infrastructure/rules be used to create [i]new [i]opportunities from a CTA?
The use case is that the CSM sees an Upsell opportunity with an existing account, creates a CTA for a CS-qualified lead, and the specific type/reason used for that CTA is picked up by a rule that creates a new Opportunity in SFDC. Once the Opportunity moves to a certain stage (Qualified), the CTA is Closed Success.
Does anyone have experience with this or know if this would be possible?
The use case is that the CSM sees an Upsell opportunity with an existing account, creates a CTA for a CS-qualified lead, and the specific type/reason used for that CTA is picked up by a rule that creates a new Opportunity in SFDC. Once the Opportunity moves to a certain stage (Qualified), the CTA is Closed Success.
Does anyone have experience with this or know if this would be possible?
+2Hi John,
We could definitely have Rules Engine do that for us. Or, we could use the 'Linked Objects' functionality to link Opportunities to these expansion CTAs. We'd then be able to, from within the same CTA, either create a new Opportunity record or link one that already exists. Here's a document and a video that might help.
Thanks!
We could definitely have Rules Engine do that for us. Or, we could use the 'Linked Objects' functionality to link Opportunities to these expansion CTAs. We'd then be able to, from within the same CTA, either create a new Opportunity record or link one that already exists. Here's a document and a video that might help.
Thanks!
1 person likes this
Reply
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.