We use the external source instruction to send multiple WhatsApp messages based on specific transition conditions. In contrast, a simpler workflow without the external source instruction would limit us to sending only one communication per trigger event.
Setup and Trigger configuration
The data source that will be used in the trigger is configured in the data sources page, which creates and links a source name to a unique external source ID. While the external source instruction does not have to be named, the function must be named and include the Javascript command:
function abcd() { return true; }
abcd is the name of the function
WhatsApp action setup
We have configured 8 different WhatsApp actions, each linking to a unique WhatsApp template. These templates are triggered based on specific conditions met by the customer.
Each customer's status is transmitted to EngAIge in a payload from the source, enabling the appropriate WhatsApp message to be sent to the customer’s phone number using InputData.Phone.ToString() in the MSISDN field.
Conditional Transitions setup
Conditions for Triggering WhatsApp Messages
- InputData.Status.ToString() === 'AccountActivated'
- InputData.Status.ToString() === 'AppDownload'
- InputData.Status.ToString() === 'AppNotLoggedIn'
- InputData.Status.ToString() === 'KYCDocuments'
- InputData.Status.ToString() === 'KYCNotVerified'
- InputData.Status.ToString() === 'KYCPending'
- InputData.Status.ToString() === 'NoTransactingActivity'
- InputData.Status.ToString() === 'TransactingActivity'
Example of one condition transition:
