Automations
Build a WhatsApp workflow that sends messages on its own after a customer action, choose its trigger, assemble its blocks, start it and follow its results.
An automation, also called a workflow, sends WhatsApp messages without you having to step in. It starts from a trigger, meaning a customer action such as starting checkout or placing an order. Each customer who takes that action enters the workflow and goes through its steps one by one, for example wait an hour, send a message, check whether they bought, then send a reminder.
Fullmetrix looks for new events every two minutes. An active automation therefore reacts a few minutes after the customer's action.
Before you start
Each WhatsApp Message block sends an Approved template. Prepare them in Templates.
The customer must have agreed to receive WhatsApp messages. Before each message, Fullmetrix checks that they are WhatsApp subscribed. If they are not, they exit the workflow and the history shows that WhatsApp consent is required. Ways to collect that consent are described in WhatsApp.
The customer must also be reachable by phone. Cart and order triggers only keep carts and orders that have a phone number.
The automation list
In the sidebar, open WhatsApp, then Automations. The page is titled Automations, with the line "Automate your WhatsApp messages based on customer actions." The counter shows the number of workflows and how many are active.
The Search... field filters by name. All statuses filters between Active and Inactive. All triggers filters by trigger. The button on the right switches between grid view and list view.
In list view, the columns are Workflow, Status, Trigger, Sent, Contacts and Date. Sent counts messages sent, Contacts the number of people who entered the workflow.
Each automation's menu offers Stats, Edit, Activate or Deactivate, and Delete. Deletion asks for confirmation and is permanent.
Available triggers
The trigger decides who enters the workflow and when.
| Trigger | Who enters | Good to know |
|---|---|---|
| Started checkout | Customers who started checkout without finishing. | The cart must have a phone number. This is the default trigger of a new automation. |
| Added product to cart | Customers with an open or abandoned cart. | The cart must have a phone number. |
| Placed order | Customers who just placed an order. | An order created awaiting payment enters once paid, within the following week. Statuses you exclude from your reports trigger nothing. |
| Viewed product | Known contacts who viewed a product page. | Requires the tracking script. The Target product field limits the trigger to one product. Leave it empty for all products. |
| Product back in stock | People subscribed to a back-in-stock alert, when the product returns. | Only accepts back-in-stock templates. See the Back in stock guide. |
| Subscribed to marketing | Contacts who just accepted your email, SMS or WhatsApp communications. | The contact must have a number, and only gets the message if they accept WhatsApp. |
| Entered segment | Contacts who join a segment. | Choose the segment in the trigger filters. |
| Exited segment | Contacts who leave a segment. | Choose the segment in the trigger filters. |
Segments are compared from one pass to the next
For Entered segment and Exited segment, Fullmetrix compares the member list with the one from the previous pass. On the first pass after starting, nobody enters, because there is no list to compare yet. To include people already in the segment at start, turn on Trigger retrospectively.
The automation builder
Click Create workflow. The builder opens full screen. It has three areas.
At the top, the bar holds the workflow name (Automation name...), its Active or Inactive state, an orange dot while there are Unsaved changes, then the Close, Save and Start automation buttons (or Pause when it is running).
On the left, the Blocks panel lists the steps you can add, grouped under Messages and Actions. In the middle, the canvas shows the workflow from top to bottom, from the trigger to End. On the right, the Properties panel shows the settings of the selected element.
To add a step, drag a block from the Blocks panel and drop it on the Drop here area, or click the + button between two steps and choose the block. Click a step on the canvas to set it up in Properties.
Setting up the trigger
Click the trigger card at the top of the canvas. The Edit trigger panel opens. Choose the trigger in the Trigger list. Its settings appear below, grouped in sections you expand with a click.
Affected sites appears for store-related triggers. By default the switch is on and the automation covers your connected stores. Turn it off to tick the stores one by one. If you turn it off without ticking anything, saving is refused with Select at least one site or use default sites.
Trigger filters narrows down which events count. The heading says what you filter for the trigger, for example Filter by cart properties or Filter by order properties. Click Add trigger filter to set a rule, for example a cart above 50 €. For segment triggers, this is where you pick the segment.
The same section holds Trigger inactivity time, ticked by default at 60 minutes, for all triggers except back in stock and segments. Unticking it opens a confirmation that recommends keeping it. To be sure to wait before the first message, also place a Delay block at the top of the workflow. That block is what holds the customer before the next step.
Audience filter limits who can enter. It applies to the contact record, for example their country or tags. Without a filter, the section shows This trigger applies to everyone. The filter is checked on entry, then before each step. A contact who no longer matches exits the workflow.
Exit conditions removes a contact as soon as an event happens after they entered. Click Add exit condition and choose among Placed an order, Viewed a page, Started checkout, Added to cart, Message delivered, Message read, Message delivery failed, Order fulfilled, Order canceled, Order refunded and Unsubscribed. Several conditions combine with or. Fullmetrix checks them before each step.
Frequency avoids messaging the same person too often. The Skip contacts who have already been in this automation option is on by default, set to In the last 1 day. Choose At any time so a contact only ever enters once. The Skip contacts who are currently in or have recently completed other automations option stops a contact from entering if they entered another automation in the last 7 days. This section does not exist for back in stock, where each subscription gets its alert.
Trigger retrospectively only appears for Entered segment. When on, contacts already in the segment enter at start.
The WhatsApp Message block
This block sends a template. Choose it in Template. The list only shows approved templates that match the trigger. A cart recovery template only appears with a cart trigger, and the Product back in stock trigger only accepts back-in-stock templates.
For each variable in the header or the Message body, choose the Variable type, for example First name, Product name or Cart link, or Custom for fixed text. Fullmetrix fills them for each contact at send time, from their record, their cart, their latest order or the product concerned.
The block ends with Send a test. Enter a number and send the message to yourself to check how it looks.
Attaching a promo code
If the template has a Copy code button or a Promo code variable, set up the offer in the block.
When the offer is already set on the template, the Template offer box shows it as inherited. It goes out automatically. The Override for this step link lets you change it for this message only, and Back to the template offer undoes that change.
Otherwise, turn on Attach a promo code. Fullmetrix creates a unique code in your store for each customer. Choose the Discount type (Percentage, Fixed amount on cart, Free shipping or Free product) and its amount, then set Expiration (days), Minimum cart, Max uses, Max per customer, Exclude sale items and Free shipping bonus if needed. The Fallback code (optional) goes out if code creation fails. With several stores, choose the Coupon source site.
In a second message, Reuse the code from the previous message sends the same code again instead of creating a new one. This is useful for a reminder such as "your code expires tomorrow".
Saving is refused if the template announces a code while the option is off, or if a message reuses a code that no earlier message creates.
The Delay block
This block makes the contact wait before the next step. Set the Duration in Minutes, Hours or Days. The canvas shows the duration on the card.
The Condition block
This block checks a situation when the contact reaches it. Choose the Condition type.
| Condition | It is true when |
|---|---|
| Cart converted | The cart that made the contact enter turned into an order. |
| Message read | The last message sent was read. |
| Message delivered | The last message sent was delivered or read. |
Under If true, then, choose Exit workflow to stop there, or Continue. With Continue, a contact for whom the condition is true skips the step that follows the condition. If the condition is false, the contact simply moves on to the next step.
For example, place Cart converted with Exit workflow before a reminder, so you do not chase someone who already bought.
The Tag contact block
This block adds or removes tags on the contact record. Choose Add tag or Remove tag, then type the names in Tag. Enter adds a tag, Backspace removes the last one, and Create tag creates a tag that does not exist yet. Tags can then be used in your segments and filters. To manage them, read Tags.
Saving and starting
Click Save. An automation without a name or without steps cannot be saved. A new automation is saved as Inactive.
When everything is ready, click Start automation. The Start this automation? window reminds you that real messages will go out as soon as a customer meets the conditions. Click Start.
To stop it, click Pause. Nobody new enters, but contacts already in the workflow go on to their last step. The list menu does the same with Activate and Deactivate.
Test before starting
Send each message as a test from its block, check the filters and exit conditions, then start. A badly set automation can message many customers within minutes.
Following results
Choose Stats in an automation's menu. The page shows Total, Unique contacts, Active, Completed, Exited, Failed and the Completion rate, then Attributed revenue and Attributed conversions. Revenue counts orders placed within 7 days after a message was read (60 days for a back-in-stock automation), or with a promo code created by the automation.
The Enrollment history table lists each contact who entered, with their status. The All, Active, Completed, Exited and Failed tabs filter the list.
| Status | What it means |
|---|---|
| Active | The contact is in the workflow, for example during a delay. |
| Completed | The contact went through all the steps. |
| Exited | The contact left before the end, through an exit condition, a Condition block, the audience filter or missing WhatsApp consent. |
| Failed | A message could not go out, for example because the template is no longer approved or sending failed three times. |
Workflow examples
To recover a cart, start from Started checkout, add a one-hour Delay, a WhatsApp Message with a cart recovery template, a Placed an order exit condition, then a second delay and a reminder with a promo code. The Cart recovery guide covers every setting.
To say thank you after a purchase, start from Placed order, add a three-day Delay and a message asking for a review. A Tag contact block at the end marks the customers you followed up with.
To win back inactive customers, create a "no order in the last 90 days" segment, then start from Entered segment with a message and a promo code.
Frequently asked questions
Campaigns
Send a WhatsApp template to your subscribers or to a segment, estimate its cost before sending, schedule it and follow its results recipient by recipient.
Widget
Show a floating WhatsApp button on your site so visitors can message you in one click, and turn on new message notifications in your browser.