Genesys Cloud - Main

 View Only

Sign Up

  • 1.  WhatsApp Template Variables - no caps

    Posted 3 days ago

    Looking for solution to Meta requiring variables in WhatsApp templates to be lower case only. Old templates have variable formatted like Genesys such as {{AGENT_ALIAS}} and then agent name is properly inserted in Genesys canned message. New WA templates require lowercase so only {{agent_alias}} and it doesn't work. Is there a way to do variable mapping in canned messages? I tried substitution but default value is text and literal value so {{AGENT_ALIAS}} in that field is what is literally populated in canned message field.


    #DigitalChannels

    ------------------------------
    Mark Kastner
    Gate 1 Travel
    ------------------------------


  • 2.  RE: WhatsApp Template Variables - no caps

    Posted 3 days ago

    Hello Mark, 

    When you use lowercase variable names in your WA templates that match Genesys standard naming conventions they should automatically populate with the correct values. The an example list is here:

    {{agent_alias}}
    {{agent_name}}
    {{customer_name}}

    Now how it works in a canned response is pretty much the same. When you create or edit your WA template the template variables from your approved WA template should appear as pill buttons when you save the message. All you have to do is click the pill button to configure the variable settings. If the variable name matches the special names, like above, then Genesys should automatically populate these. 

    Hope this helps. 



    ------------------------------
    Cameron
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: WhatsApp Template Variables - no caps

    Posted 3 days ago

    Hi Cameron,

    Thanks for the reply. The behavior you described is not what I'm experiencing in Genesys. For this new WA template that only allows lower case names, the variable is stated as {{agent_alias}}. In Genesys canned messages>Message Template it appears as the bubble with {{agent_alias}}. When the agent uses the canned message, the variable field appears blank. However, in an older WA template that was previously approved when they allowed upper case variable names, in the Genesys canned message for that template, the agent name is auto-filled. 

    image


    ------------------------------
    Mark Kastner
    Gate 1 Travel
    ------------------------------



  • 4.  RE: WhatsApp Template Variables - no caps

    Posted 3 days ago

    Hello Mark, 

    This is an interesting behavior, and it seems its not working as expected. I recommend opening a case with product support. There might be something going on in the backend with canned responses that we cant troubleshoot here in a public forum. 

    Cheers, 



    ------------------------------
    Cameron
    Online Community Manager/Moderator
    ------------------------------



  • 5.  RE: WhatsApp Template Variables - no caps

    Posted 3 days ago

    Hi Mark

    I see this was added/updated on the 23rd of Feb, not sure if this might help.

    https://help.genesys.cloud/articles/add-a-whatsapp-template-message/

    https://help.genesys.cloud/articles/substitutions-overview/

    Hopefully someone in the community can share some ideas on how to address this.

    Regards



    ------------------------------
    Stephan Taljaard
    EMBEDIT s.r.o
    ------------------------------



  • 6.  RE: WhatsApp Template Variables - no caps

    Posted 3 days ago

    The variabkle sin the WABA messenger template need to match the template variable you have in the WABA Template.

    I used this in a Data Action for a Agentless message. the whole text of the Waba template need to match the text in the Messaging Template. Hope this helps



    ------------------------------
    Raymond Marchand
    Sr. Principal PS Consultant
    ------------------------------



  • 7.  RE: WhatsApp Template Variables - no caps

    Posted 2 days ago

    I've been advised that after Meta changed to lowercase variable names, previous approved templates continue to work but new templates will not and Genesys is not providing a variable name mapping to overcome this loss of function. Instead, they say the only workaround is to use lowercase names and agents have to manually complete the field even though the data could have been auto populated with a variable name map. I 



    ------------------------------
    Mark Kastner
    Gate 1 Travel
    ------------------------------