Helper ⭐️⭐️⭐️

New Idea

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

Forum|Forum|7 years ago
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.

john_apple

Expert ⭐️

I would like to see this.

Right now, I have a Conditional Wait that checks to see if the owner changed and then sends an alternative email if it has. Since we can't use the calculated field in the email header fields, the message is sent from a generic email and sender name rather thant the specific person.

kate_green

Helper ⭐️⭐️

I 100% agree Alex!

For another example, we want to start a participant along a Program if their upcoming renewal is within 30 days AND if their renewal opp is not in a certain stage. If, within the time between the 30 day and 15 day mark, the renewal opp moves into a certain stage, I want them to drop from the program so that they don't get the second "reminder" email at day 15.

john_apple

Expert ⭐️

I think you can already do this:

Add Opportunity ID to the participant query
Make a new Custom Mapping and map it to the Opportunity ID from your query
Make a New Calculated field based on the Opportunity Object. Show "Stage" and set filter to SFDC Opportunity equal to the Field "Opportunity ID"
Add the Calculated Field to a Conditional Wait step and set the Condition to equal whatever Stage should continue to get reminder emails or set Condition to Not Equal whatever Stage should be dropped from receiving emails.

john_apple

Expert ⭐️

For Example

Custom Mapping:

Calculated Field:

Conditional Wait Step:

kate_green

Helper ⭐️⭐️

@john_apple I'm having trouble understanding whether what you described would look at the updated stage of the opportunity, rather than the stage of the opportunity when the participant entered the program. The stage of the opportunity could change between the first and second emails sent.. so will the calculated field refresh and pull the new data from the source object during the conditional wait period?

kate_green

Helper ⭐️⭐️

One issue I'm running into in testing this is that the field "Id" from the Opportunity object is not available as a filter when I create a calculated field.

john_apple

Expert ⭐️

Hi @kate_green

When you make the initial query, that will pull the Opportunity Stage at the time of the sync (snapshot in time).

When the participant reaches the Conditional Wait, the logic of the Calculated Field will find the matching opportunity from the initial query and then provide the current Stage of the opportunity to compare to the initial query - like comparing a before and after snapshot.

If they are the same, then the participant would continue in the Program. If they are not the same, then they would be dropped.

kate_green

Helper ⭐️⭐️

Where you say "If they are the same, then the participant would continue in the Program. If they are not the same, then they would be dropped."...

Could I also have them dropped if the Stage is now a specific value - "Closed Won" or "Signed Paperwork Received" for example?

john_apple

Expert ⭐️

Do you see SFDC Opportunity ID as a field from the Opportunity Object?

john_apple

Expert ⭐️

"Could I also have them dropped if the Stage is now a specific value - "Closed Won" or "Signed Paperwork Received" for example?"

Yes - Set the Calculated Fields on the Conditional Wait to be Stage DOES NOT Equal "Closed Won" AND Stage DOES NOT equal "Signed Paperwork Received"

Show more replies

Didn't find what you were looking for?

Sign up

Welcome to the Gainsight Community