OMNI can be integrated with WATI via Shopify Flow to send WhatsApp messages when specific loyalty events happen on your Shopify store.
Pre-requisites
You will need the following to enable the WATI integration with OMNI
An active subscription of WATI (https://www.wati.io/)
"Shopify Flow Trigger" integrations enabled in your OMNI settings
Integration
Once you satisfy the pre-requisites, you can choose from our range of pre-built Shopify Flow templates that can be configured to send out WhatsApp template messages.
We currently support the following pre-built Shopify Flows with WATI
When a customer registers for an account, send a welcome message
On the 1st day of a customer's birthday month, send a birthday message
When a customer enters new tier, send a congratulations message
When a customer earns points from a purchase, send a update point balance message
When a customer has points expiring in 30 days, send a reminder message
You may also build your own Shopify Flows and trigger WATI to send out a message. If you need assistance on building additional custom flows, contact support and we can assist for an extra fee.
Setup instructions
Step 1 - Create your own WhatsApp template messages within WATI and submit for review
Within WATI, navigate to Broadcast > Your Templates and Click "New Template Message"
Configure your template message with Title, body text, footer, and buttons.
Configure the WhatsApp message to fit your needs. A preview will be shown on the right of the screen.
You can also use variables from WATI or your own custom variables to make your messages more personalized by inputting the name of the custom variable inside a double bracket. For example - {{tierBonusPointsGranted}}
You will need to configure these variables in Shopify Flow in the next step in order for WATI's template to pickup these variables and populate them in your messages.
Additionally, you can also refer to the parameters section in our Shopfiy Flow template for WATI flows for useful variables that is passed into WATI when the Flow runs.
Example - Tier entry template
Configure the Template Name, Category, and Language
The template name will be referenced when you configure the Shopify Flow in step 2. So make sure it is unique and you can identify what this template message does from the name.
The category must be specified as either - marketing, utilities, or authentications. You should select this based on the content of your message. You can refer to Meta's guidelines on template message categorization here. Make sure you select the correct category as Meta will review your content and categorization before approving your template.
Our sample messages as configured as the following categories for your reference:
- Welcome: Marketing
- Birthday: Marketing
- Tier entry: Marketing
- Points added from purchase: Utilities
- Points expiring: Utilities
The Language should be selected to reflect the language of your message
Save and submit for review
Once you have confirmed all above configurations, you can save the template and submit for review. Meta will review the template and notify you if it is approved or rejected.
If your template is rejected, you will need to create a new template and submit it for review again. Only approved templates can be sent out to customers.
For a more detailed guide on configuring template messages on WATI, please refer to - https://support.wati.io/l/en/article/r1spg2n4j9-how-do-i-create-a-template-message
Step 2 - Clone our Shopify Flow template into your store
Based on the flow you want to set up, you can contact our support team to help you clone any of the supported Shopify Flow templates into your store and further modify it complete the set up.
Step 3 - (Optional) Configure the conditions of the Flow for your needs
If the flow you are setting up contains certain conditions, you may want to update those conditions to better suit your store's setup. For example, if you are setting up the Tier entry flow then you will want to update the conditional splits to reflect the tier names used in your loyalty program
Step 4 - Update the HTTP Request action with your WATI client ID and Access tokens within the "URL" of the Send HTTP Request action
For each "Send HTTP request" action inside the Shopify Flow template you will need to update the following fields to make sure the integration is made to your own WATI account
URL - Update the highlighted string of numbers with your own WATI client ID.
You can find the WATI client ID inside your WATI account after clicking on the profile icon on the top right corner
Headers > Authorization - Update the value of the Authorization header with your own WATI access token.
You can find the WATI access token inside your WATI account within"API Docs" on the top navigation
Step 5 - Update the "Body" of your HTTP request with the right template name and parameters
Within the "Body" section of each of your HTTP requests you need to update the value for
template_name: The value should match that the name you created inside WATI in Step 1 of this guide for that template
broadcast_name: This can be any value but we suggest keeping it similar to your template name so you can reference specific send outs of the template message in the future
parameters: You can include any of the parameters listed here into your WATI template messages by using
{{name_of_the_parameter}}within the WATI template in Step 1.
You can also add your own parameters by following the syntax and adding additional rows shown in the example
{
"name": "name_of_the_parameter"
"value": "value_of_the_parameter"
},
The value of the parameter can be configured using variables from Shopify Flow or it can be a static value depending on your need.
Step 6 - Save and turn on the Shopify Flow
Once you are confirmed with the above configurations, make sure you save the workflow and click "Turn on workflow" to enable the integration
Reminder - make sure that you have enough credits within your WATI account to send template messages to your customers. For more information on conversation pricing, please refer to - https://support.wati.io/l/en/article/1ytkxyyie9-what-is-conversation-based-pricing-pricing-pricing