Jump to: navigation, search

WhatsApp

This page explains how to create a structured message for WhatsApp.

Structured messages for WhatsApp (also known as highly structured messages) use specific message formats that your company can use to notify customers about things such as an upcoming bill, service outage, or any other notification-type message. You can use eServices Manager to create and format the structured message for WhatsApp.

Warning
Before continuing, you must upload the message to WhatsApp for approval before you can finish creating the structured message in eServices Manager. See the WhatsApp documentation for more information.

Creating a structured message for WhatsApp

  1. Create a standard response.
  2. Go to the Structured Body tab.
  3. Select Structured.
    ESMgr900 CreateHSM.png
  4. In the Media Origin menu, select Genesys JSON.
  5. In the Type menu, select Notification.
  6. Click Edit JSON to configure the structured message. See the Configuring the structured message section below for more information.
  7. Optionally, you can directly edit the JSON associated with the media type in the provided field, or click Open File to load a JSON file from your local machine.
  8. Optionally, add field codes.
    Important
    You must not use double-quotation marks (") for field codes that are used in structured messages. Use single quotation marks (') instead.
  9. Click Create.

Configuring the structured message

After you click Edit JSON, an editor appears that allows you to edit the structured message.

In the ID field, enter the namespace@element_name ID for the structured message (provided in WhatsApp Manager after WhatsApp has approved the message).

In the Content area, compose the content of your message. For example, let's say you want to create a message to let customers know when their account balance is $0. Enter the following message: Hello Customer. Your account balance is now $0. Contact us at 1-800-555-5555 to add more funds.

ESMgr900 CreateHSM3.png

You can use field codes to introduce parameters for known data. For example, instead of Customer, you can use <$Contact.FirstName$>. In the Content area, remove Customer and then click ESMgr900 CreateHSM2.png to add parameters. Notice how a variable has been added to the Content area (as this is the first variable, it's {{1}}). In the Parameters section, you can define the {{1}} variable as such:

  • Name—Enter the name of the variable. For example, Customer.
  • Value—Enter the field code to use. For ease of use, you can:
    1. Enter a temporary value in the Value field.
    2. Click Save to save the message template and return to the New/Edit Standard Response window.
    3. In the JSON Part section, find the temporary parameter value you used earlier (for example, "value": "Sample_Value") and select the sample value.
    4. Click Insert Field Code.
    5. Select a field code and click OK to insert it, together with its required delimiters (<$ $>), into the standard response.
      Important
      Only use field codes in parameter values.

The Content area now looks like this:

ESMgr900 CreateHSM4.png

As you edit the Content area, a live preview appears on the right to show you how the message will appear to the customer. Field codes are rendered when the message is inserted into a WhatsApp interaction by an agent in Workspace. However, when eServices Manager detects a field code in the message, you can click Render (located above the live preview area) to render the field code with its default value.

Optionally, you can use the toolbar in the Content area to use bold (B), italics (I), strikethroughs (S), and highlights (<>).

When you are done, click Save.

Dark mode

Optionally, you can select Dark to use dark mode. Below is a comparison:

  • Dark off:
    ESMgr900 HSMLight.png
  • Dark on:
    ESMgr900 HSMDark.png
Retrieved from "https://docs.genesys.com/Documentation:ESDA:ESMgr:HSM:9.0.0 (2019-10-23 18:31:55)"
This page was last modified on May 8, 2019, at 09:58.

Feedback

Comment on this article:

blog comments powered by Disqus