Hi Vikki,
You can make this much simpler - there is no need to build a "message inside another message" or a little nested-variable matryoshka. π
In the button action, select:
Data Actions β Execute Data Action
After selecting your Data Action, configure its SMSBody input as Interpolated Text.
Genesys Cloud documents that Data Action inputs in a script can be populated with variables, static values, or interpolated text. Interpolated Text allows you to combine regular text with script variables, and Genesys inserts each variable's runtime value when the action executes. (Help My PureCloud)
Your input could therefore be configured directly as:
We are reaching out to confirm your appointment on {{ApptDateTime}}.
If you need to change your appointment, please contact me by email at {{Scripter.Agent Email}} or call {{PhoneReply}}.
The flow is simply:
{{ApptDateTime}} β
{{Scripter.Agent Email}} βββ> Interpolated Text ββ> SMSBody ββ> Data Action
{{PhoneReply}} β
{{Scripter.Agent Email}} is the documented built-in variable for the current agent's email address. (Genesys Cloud Resource Center)
So, in this scenario, I would skip RawBody and the additional substitution step. Let the SMSBody input itself be the template: Genesys Cloud will combine the fixed text with the current variable values and submit the completed input when the Data Action runs. (Help My PureCloud)
Sometimes the easiest solution really is the right one: three ingredients, one Interpolated Text field, and off the message goes. π
------------------------------
Fernando Sotto dos Santos
Consultor de Atendimento Senior Grupo Casas Bahia
------------------------------