If you want to bypass the 24-hour rule by WhatsApp, you can send WhatsApp template messages to your end-users, as long as they have already reached out to your business by opening a ticket via WhatsApp.
This article covers the following topics:
Requirements
To submit and send WhatsApp template messages to end-users, you must have at least one phone number connected to the WhatsApp Business API. If you haven't already done this, then complete the self-service process to create your WhatsApp Business account and to connect a phone number to it (see Adding WhatsApp channels to the Zendesk Agent workspace).
Creating and submitting WhatsApp template messages via the WhatsApp business account UI
After you've connected your phone number to the WhatsApp Business API, you can create and submit WhatsApp template messages within the WhatsApp Business account UI (see Meta Business templates). For more information about the process, see Meta's documentation, Create message templates for your WhatsApp Business account.
If you submit a WhatsApp template message with a variable, parameter, and/or media, you must submit the actual content as a sample, otherwise WhatsApp will reject it.
“Hi {{1}},
Welcome to the {{2}}, we wish you a great stay. If you need anything, feel free to reach out to {{3}} and they’ll be happy to assist you.
Have a great day,”
In this example, the variables are:
{{1}}
The end-user name
{{2}}
The hotel name
{{3}}
The team name
Using shorthand syntax to send WhatsApp template messages
Bypassing the WhatsApp 24 hour rule
If you can't reply to a message sent via WhatsApp within 24 hours, consider bypassing the WhatsApp 24 hour rule so you can still reply later.
To bypass the WhatsApp 24 hour rule
- An end-user has messaged your business and opened a ticket.
- Use Sunshine Conversations shorthand syntax (see Sunshine conversations WhatsApp).
- After the WhatsApp template message is approved, create a macro to send the WhatsApp template message to end-users who have already opened a ticket.
Here are two examples of how to create the content of the macro:
&((namespace=[[namespace]] template=[[template]] fallback=[[text_fallback]] language=[[language]] body_text=[[param_1]]))&
or
&(( namespace=[[namespace]] template=[[template]] fallback=[[fallback]] language=[[language]] body_text=[[param_1]] ))&
-
namespace
- the unique ID for your WhatsApp Business account. You can find your namespace on the toolbar of your WhatsApp Business account, click Namespace. -
template
- enter a name for your template. -
language
- for the language code, see Supported languages in the Meta for developers documentation.
-
- Thoroughly test the functionality of each WhatsApp template message macro, before deploying to production.
Note: WhatsApp template message content is not reconstructed within the ticket after you have sent it (it appears only as shorthand syntax to the agent). However, your end-users will see the content of the WhatsApp template message.
Testing your macro functionality
To test text without variables
- Create a macro.
- Under Actions, paste the following example in the Rich content field and insert the relevant information for your namespace, template, fallback text, and language.
&((namespace=[[namespace]] template=[[template]] fallback=[[text_fallback]] language=[[language]]))&
To test text with variables
- Create a macro.
- Under Actions, paste the following example in the Rich content field and insert the relevant information for your namespace, template, fallback text, language, and for example the ticket requester’s first name.
&((namespace=[[namespace]] template=[[template]] fallback=[[text_fallback]] language=[[language]] body_text=[[ticket.requester.first_name]]))&
To test text with variables and a media image
- Create a macro.
- Under Actions, paste the following example in the Rich content field and insert the relevant information for your namespace, template, fallback text, language, and for example the URL location of the header image.
&((namespace=[[namespace]] template=[[template]] fallback=[[text_fallback]] language=[[language]] header_image=[[image_location]] body_text=[[param_1]] body_text=[[param_2]]))&
To test text with quick reply buttons
- Create a macro.
- Under Actions, paste the following example in the Rich content field and insert the relevant information for your namespace, template, fallback text, language, and for example the content of your buttons.
&((namespace=[[namespace]] template=[[template]] fallback=[[text_fallback]] language=[[language]] button_index=[[0]] button_payload=[[<paste the content>]] button_index=[[1]] button_payload=[[<paste the content>]] ))&
To test text with variables, media, and buttons
- Create a macro.
- Under Actions, paste the following example in the Rich content field and insert the relevant information for your namespace, template, fallback text, language, and for example the URL location of the header image, two different types of body text, the button index, and the URL location of the button.
&((namespace=[[namespace]] template=[[two_variable_media_buttons]] fallback=[[text_fallback]] language=[[language]] header_document=[[document_location]] body_text=[[param_1]] body_text=[[param_2]] button_index=[[1]] button_url=[[url]]))&
Using Sunshine conversations API to send WhatsApp template messages
If the end-user has not yet messaged your business, you can still send an outbound message to them by using the Notifications API feature, see the How to start conversations section of Sunshine Conversations: WhatsApp. You or your Engineering team can do this by using the Sunshine Conversations API.
Troubleshooting WhatsApp templates
WhatsApp rejected my WhatsApp template
To find out why your template was rejected, click the template. Depending on the reason for rejection, you can either edit the body, the variable, and the media of your WhatsApp template message, or appeal the decision. However, if your template keeps being rejected, you must create a new one with a new name and content. For more information, see Message template guidelines in the Meta for developers documentation.
5 Comments
This is a very relevant feature for Zendesk customers looking forward to bypassing Meta's 24-hour reply rule. With a deep knowledge of Zendesk, you can also create triggers and automations to send WhatsApp notifications in several ways.
In case you need further capacities such as:
You can start using Respira's WhatsApp Connector, a Zendesk app with the first 1000 notifications for free.
Where are you pulling the relevant information fallback from? I am struggling to get this working
Hi Richard Basteed,
Thanks for reaching out! The fallback value is set by the business. You can find the descriptions of these key values used for sending WhatsApp Message Templates via shorthand syntax here.
Hope this helps!
I’m trying to bypass the 24-hour rule from WhatsApp. I followed all the instructions in this post:
The problem is: when I try to execute the macro, the message with the shorthand syntax doesn’t appear in the “public comments” section, so I cannot send the WhatsApp template. I get this warning message instead, which doesn’t allow me to write new public comments after the 24h window:
I tested the macro within the 24h period and it worked perfectly. The end-user recived the pre-approved template just as intended, but after the 24h limit it is imposible to execute the macro properly.
Any idea how can I solve this ?
I can see you already opened a ticket with us regarding this, thank you! Let's coordinate together there 😉
Please sign in to leave a comment.