WhatsApp automation for businesses and support
WhatsApp automation for businesses: send an approved template when an inquiry arrives, a status changes or a set time passes, or hand the chat to your AI agent.
In short
WhatsApp automation in StoreChart sends automated messages in response to business events: a new lead, a status change, time elapsed, an incoming message or an order. Each rule sends an approved template or activates the AI agent, while follow-up steps continue the conversation when the customer replies.
One automated rule for every matching business event
Set it up once, and it runs in the background for your business
- Automations fire from real business events: a new lead, a status change, time elapsed, an incoming message or a purchase
- Each rule sends an approved WhatsApp template or hands the conversation to an AI agent, and follow-up steps can send free-form messages once the customer replies
- Conditions like 'customers tagged VIP' or 'deal status' ensure messages only reach relevant recipients
- Built-in delays let you send follow-ups and review requests at the exact right moment instead of immediately
WhatsApp automation features
Ongoing customer messaging without sending each message by hand
Set up an automation in 3 steps
From trigger to run log
Pick the business event that fires the automation: new lead, status changed, time elapsed or incoming message: from the available list.
Add conditions like a minimum deal amount or a customer tag, then choose the action: an approved WhatsApp template or activating the AI agent.
Activate the automation and it runs from that moment on every matching event; check the run log to confirm everything is firing as expected.
WhatsApp Business automation for your store: where to start
Five ready starting points
The automations screen offers five starting points. Each one pre-fills the trigger and the type of action, and you choose the template and the status.
- Order confirmation: for every new order.
- Shipping update: when the status changes to shipped.
- Review request: three days after an order.
- New lead greeting: for anyone who left their details.
- Incoming message routing: to an AI agent.
A sensible order to switch them on
A store that's just starting can turn automations on in this order:
- Shipping update: one of the most common questions on WhatsApp, and its content is pure service.
- Order confirmation: right after it.
- Lead greeting: if you get enquiries from forms on your site.
- Reviews and marketing: last, once it's clear customers respond well to messages from the store.
Start every new automation with a narrowing condition, such as one store or a certain total. Widen it after a few days of a clean log.
Branches and conditions in one rule
A rule can hold several branches. The system checks them in order and runs only the first one that matches, so a customer never gets two messages from the same event.
- Order conditions: total, number of items, SKUs, product names, shipping and payment method, coupon and sales channel.
- Customer conditions: tags, number of orders, total spent, time as a customer and time since the last order.
- Lead conditions: status, channel, estimated value and next step.
- Branch with no conditions: catches everything else, so it can only be the last one.
Example: an "order placed" rule
Illustrative only. One rule with three branches:
- Customers with more than three previous orders get a personal thank-you template.
- Orders over $120 shipping to a particular city get a reminder to arrange delivery.
- The last branch, with no conditions, sends the standard order confirmation.
Without a last branch like that, an order that matches no condition gets no message. Sometimes that's exactly what you want.
Follow-up steps on customer replies
Each branch can have steps that wait for the customer's reply.
- What fires a step: any reply, or a tap on a specific quick-reply button, such as "Yes, let's arrange it" or "Not now".
- When the wait starts: only after the previous message was sent.
- Expiry: after 24 hours without a reply, so a step never fires a week late.
- Free-form message: the customer replied and the window is open, so a follow-up step can send free text with variables in square brackets.
Dry test and run log
Before switching a rule on, run a dry test. The system takes the most recent order or lead that matches and shows the message exactly as it would go out, without sending anything.
- Pick an order: test against a specific order too, such as one without a tracking number. A variable that won't fill in shows up front.
- Counters: each rule counts runs, messages sent and runs skipped.
- Log per run: which branch was chosen, how each condition came out and the text actually sent.
- Delivery and cost: the delivery status Meta reported, and whether the message went out as a session message or a billable template.
- No duplicates: each event runs a rule once only, even if it arrives twice.
Who it's for and what's not included
Automations run on events that reach StoreChart: orders from your connected stores, leads in the CRM and incoming WhatsApp messages.
- Good fit: an online store that wants regular WhatsApp updates, alongside templates, the shared inbox and the AI agent.
- Incoming message: a trigger with no delay that switches on the agent or sends a template straight away. Its conditions check the text, whether it's the first message and whether the sender is already a customer.
- No outgoing triggers: StoreChart doesn't send webhooks from automations to outside systems.
- WhatsApp only: no SMS and no email.
- No sending hours: a delay counts from the event. An order placed at midnight with a two-hour delay gets its message at 2 a.m.
Integrations
Frequently asked questions about WhatsApp automations
Which events can start an automation?
The available triggers are a new order, an order status change (optionally from and to a specific status), a set time after an order, a new lead, a lead status change, and an incoming WhatsApp message. Branches and conditions let one automation cover more complex scenarios.
Can I send an automatic WhatsApp message to a customer?
Yes. The first message in a rule is always a template Meta has approved, because the automation contacts the customer on its own initiative. Once the customer replies, follow-up steps can also send a free-form message with variables, and if the window has closed by the time the step runs, the message isn't sent and the run log shows why.
Can an automation be limited to VIP customers only?
Yes. Add a condition on customer tags so the automation only fires for customers tagged VIP, while everyone else continues receiving standard handling.
How many automations can run at the same time?
Automations are included in the plans that offer them, and there's no separate cap on how many rules you create. Each rule belongs to one store and can be switched on or off on its own.
Can I check that an automated message was sent?
Yes, every automation run is logged with its status (scheduled, sent, skipped or failed), its timing, and a trace of the trigger and conditions it evaluated, so you can check at any moment that the automation is working as designed.
Can one trigger lead to more than one message?
Yes, through a multi-step flow: the first message goes out when the trigger fires, and follow-up steps run when the customer replies, with anything, or by tapping a specific quick-reply button. Branches can also send different customers different messages from the same trigger.
Can I pause an automation without deleting it?
Yes, toggling an automation off keeps its full configuration and history intact, so you can pause it during a promotion or system change and re-enable it later with no rebuilding required.
Related capabilities
WhatsApp Business automation for every store event
Pick an event and a condition, and the message goes out


