Skip to main content
alex_legay
Helper ⭐️⭐️⭐️
May 6, 2019
New Idea

Programs - Designate participant fields to be updated if changed e.g. CSM

  • May 6, 2019
  • 26 replies
  • 359 views
Right now, when a participant field is synced it will not be updated once the program is active. For example, say a CSM changes between emails in a program where it is configured to send from a CSM, I can't think of any ways to make it so this change is reflected within this program. I am not sure how this would be built but it would be nice to designate some fields to be always up to date.

Seems calculated fields can be used as a token in the email but the From Name and From email address don't accept calculated fields.

    26 replies

    alex_legay
    Helper ⭐️⭐️⭐️
    March 11, 2020

    Can we open this back up? This request was more for updating specific fields used in the program. Like say you are sending the email from the CSM or tokenizing their name in the email and then the CSM changes. That would need to be reflected in the program emails.

     

    lila_meyer
    Gainsight Employee ⭐️⭐️⭐️
    March 11, 2020

    Hi @alex_legay Is this really a feature request?

    Lila Krutel, Dir. Global Education Services
    alex_legay
    Helper ⭐️⭐️⭐️
    March 11, 2020

    Hi @alex_legay Is this really a feature request?

    Yes, Can we change this to an idea? As this was a while ago I am not sure if I made this a question but it seems to be one now.

     

    The request is to allow some way to update participant fields of an active program. Say the CSM changes and the program is sending emails out from the CSM, we would need that to change to the new CSM.

    spencer_engel
    Expert ⭐️
    March 12, 2020

    Once this is made into a feature request, it might be good to notify the people on this thread @lila_meyer. https://community.gainsight.com/jo-email-notifications-10/are-programs-participant-field-values-static-6097

     

    Also, this is becoming a more and more requested feature, at least in my interactions. I’ll be sure to forward this thread to interested customers. 

    lila_meyer
    Gainsight Employee ⭐️⭐️⭐️
    March 12, 2020

    Hi everyone, I converted this post to an Idea, so please vote for it if it’s a key request for you. 

    Lila Krutel, Dir. Global Education Services
    spencer_engel
    Expert ⭐️
    March 12, 2020

    @nitisha_rathi This is what I brought up earlier today. Can you confirm if this is indeed on the roadmap?

    heather_hansen
    VIP ⭐️⭐️⭐️⭐️⭐️
    March 13, 2020

    @alex_legay I ran into this exact scenario, and I didn’t find a way to replace with the new CSM, but I did add a conditional wait with a calculated field to check and see if the CSM was the same, and if not, to remove the customer from the program. Not ideal, but fixed the immediate problem of the email coming from an old CSM.  

    lila_meyer
    Gainsight Employee ⭐️⭐️⭐️
    March 13, 2020

    I believe this will be addressed in the April 6.13 release for both NXT and Salesforce edition. Gainsight will support the addition of Calculated fields in the Email Addresses fields. This allows the system to pick up the correct receiver and sender at the time of sending the email, even if it has changed since the participant entered the Program. 

    Stay tuned for more details in the upcoming release notes...

    Lila Krutel, Dir. Global Education Services
    Helper ⭐️⭐️⭐️
    April 16, 2020

    Hello Everyone! 

    Happy to announce that your request has been considered and included as part of the v6.13 release. Gainsight now supports the use of Calculated fields in the Email Address fields of a Program. This allows the system to pick up the correct receiver and sender at the time of sending the email. 

    This feature is implemented in both SFDC & NXT versions.

    Thanks for posting!

    sarahmiracle
    VIP ⭐️⭐️⭐️⭐️⭐️
    June 22, 2022

    Hi there - just came across this which is incredibly helpful, but I learned something when trying to implement this myself:

     

    In a program, the Recipient Email Address field does not need to be an Email data type field to be mapped to Recipient Email Address. For example we occassionally have datasets where it is a String value that contains an email address, and I’m still able to map this String value to Recipient Email Address and send emails.


    However, if planning to use Calculated Fields for the To, Reply To, or From fields on the Send Email step, the field does need to be an Email data type field, and cannot be string. I am trying to use this Calculated Field method to dynamically change the recipient of the email, but I cannot accomplish this as my field containing the email address for the recipient is a String value.

     

    Can I add to this request to also allow for String values?

    Customer Success Systems Admin @ Amplitude, 3x Gainsight CS Ops Product Council Member