WhatsApp automation that knows which rule to run
Most platforms flatten four very different things into one word. ChatSetu AI keeps keyword flows, drip journeys, status follow-ups and away messages separate, because you need them for separate jobs.
The problem
Answering by hand works right up until it doesn't
Early on, WhatsApp feels effortless. One phone, one person, a few dozen conversations a day. Then the volume climbs and the same five questions arrive over and over, enquiries go cold because nobody chased them, and a message that lands at 10pm sits unread until the next morning — by which point the customer has messaged a competitor too.
The instinctive fix is to hire another person for the phone. That buys you a few months. The real problem is that the work is repetitive and time-bound: the same reply, the same reminder three days later, the same nudge when a deal stalls. Repetitive and time-bound work is exactly what software is good at, and it is exactly what your team resents doing.
What makes this harder than it should be is vocabulary. Vendors call everything “automation”, so it is genuinely difficult to tell whether a product replies to keywords, sends timed sequences, reacts to a change in your pipeline, or just posts an out-of-office notice. Those are four different mechanisms. Below is how each one works and when to reach for it.
How it works
Four mechanisms, four different jobs
Each is triggered by something different. Get the trigger right and the automation feels helpful; get it wrong and it feels like spam.
Trigger and keyword flows
A flow is a reusable automation with a trigger and a set of keywords attached to it. Someone messages a word you have registered, the flow fires, and the conversation follows the path you designed. Each flow carries its own name, description and status, so you can build one, duplicate it as a starting point for the next, and activate or deactivate it without deleting anything.
Scheduled drip journeys
A journey is a multi-step sequence that plays out over time rather than in a single conversation. You define the steps, set the trigger type, and the journey walks each contact through them on schedule. Activate it, deactivate it, or run it now when you want a sequence to go out immediately instead of waiting for its next window.
Date-event journeys
Journeys can also be triggered by a date on the contact record rather than by an action. Date of birth and anniversary are first-class contact fields, so a birthday message or an anniversary note is a journey with a date-based trigger — not a spreadsheet you remember to check on Monday mornings.
Status-driven follow-ups
Follow-ups start when a contact's status changes. Move someone from enquiry to quoted, or from trial to churned, and the matching follow-up sequence begins. Steps run in the order you set them, can be filtered by date, and can be scoped by role so the right team owns the right sequence.
Business hours and away messages
Set your working schedule and timezone once. Outside those hours WhatsApp automation answers with your away message, or with an approved template if you would rather send something richer than plain text. Nobody gets silence at 11pm, and your team is not pressured into replying at 11pm either.
Basic replies for the obvious questions
Not everything needs a flow. Basic replies are canned answers tied to keywords — opening times, address, refund policy, the link to your form. They handle the questions that arrive twenty times a week and free your flows and journeys for work that actually branches.
The parts that keep automation honest
Sending is the easy half. These are the controls that stop a sequence quietly costing money or annoying people for months without anyone noticing.
Per-step funnel stats
Every journey reports step by step, so you can see where people carry on and where they stop. Automation that you cannot measure is just guesswork with a schedule attached.
Budget controls on journeys
Journeys carry budget controls, which matters because template messages are billed by Meta per conversation. You set the ceiling rather than discovering it on an invoice.
Auto-assignment
When a conversation needs a person, auto-assignment settings decide who picks it up instead of leaving it in a shared queue nobody owns.
Duplicate and iterate
Flows can be duplicated, so a working automation becomes the template for the next one. Deactivate rather than delete while you test a replacement.
Worth a section of its own
Describe the automation, get a flow back
The slowest part of automation has always been the building. Dragging nodes around a canvas to express something you could have said out loud in ten seconds is a tax on getting started, and it is the reason a lot of automation plans die at the blank-canvas stage.
ChatSetu AI includes AI flow generation. You write what you want in plain language — a sentence, not a specification — and it builds the automation flow graph for you: the trigger, the steps and the branches, assembled and ready to open.
It is a starting point, not a black box. The generated flow is an ordinary flow. You open it, read what it did, change the wording, remove the branch you don't want, and activate it when you are happy. The AI removes the blank canvas; you keep the editorial control.
What that looks like in practice
“When someone messages the word DEMO, ask which city they are in, save the answer, and hand the chat to the sales team.”
One sentence in, a structured flow out — trigger, question step, the field it writes to, and the handover. You review it, adjust the copy to sound like your business, and switch it on. If it is not quite right, editing three steps is far quicker than drawing seven from scratch.
Typical setup
A sensible order to switch things on
Businesses that try to automate everything on day one usually end up switching it all off again. This order builds confidence, and each step is useful on its own even if you stop there.
- 1
Get the account connected
Automation runs on the official WhatsApp Business Platform, so the first job is connecting your number and getting your message templates submitted and approved. Templates are what let you start a conversation outside the 24-hour service window, and approval takes time — start here so it is not the thing blocking you later.
- 2
Set business hours and the away message
The smallest change with the biggest immediate effect. Enter your schedule and timezone, write an away message that says when you will actually reply, and attach an approved template instead if you want something richer. From that evening onwards, nobody messages you into silence.
- 3
Cover the repeat questions with basic replies
Spend twenty minutes in your inbox listing the questions you answer most. Opening times, location, delivery windows, what your pricing depends on. Turn each into a keyword reply. This alone tends to take a meaningful bite out of daily message volume.
- 4
Build your first real flow
Pick one entry point that matters — a keyword from an ad, an enquiry about a specific product — and build a flow that qualifies the person and routes them. Describe it to AI flow generation if you want a head start, then edit it. Test it on your own number before activating it.
- 5
Add follow-ups to your pipeline statuses
Now connect automation to how you actually work. Decide what should happen when a contact moves to quoted, to no-response, to won. Build an ordered follow-up sequence for each status that deserves one, and scope it to the role that owns those contacts.
- 6
Layer journeys on top, then read the numbers
Onboarding drips, re-engagement sequences, birthday and anniversary messages using the date fields on the contact record. Set a budget on each. Then come back to the per-step funnel stats in a fortnight and cut the steps people are clearly ignoring.
One rule worth keeping
Every automation needs an exit to a human. Opt-in and the 24-hour service window are Meta's rules and they apply to automated messages exactly as they apply to typed ones — but the rule your customers care about is simpler: when the bot runs out of answers, a person should appear.
Where this fits
Automation doesn't work alone
Follow-ups fire on a status change, and statuses live on the contact record — so your contact database and custom fields are what makes status-driven automation possible at all. The same record holds the date of birth and anniversary that date-event journeys read.
When a flow reaches its limit, the conversation has to land somewhere staffed. That is the shared team inbox, where auto-assignment routes it to an agent or department. For open-ended questions rather than fixed paths, an AI chatbot trained on your own documents handles what a keyword never could.
Automation is one-to-one and reactive. When you want to reach a whole segment at once, that is a template broadcast campaign instead, and it needs approved templates and a connected WhatsApp Business API account. Running a store? Order updates and cart recovery are handled by the Shopify integration.
Reading further: what WhatsApp automation actually means covers the concepts from scratch, and automating customer support on WhatsApp goes deeper on support specifically. If templates are new to you, start with the message templates guide.
FAQ
Frequently asked questions
The questions people ask before they automate anything.
What is WhatsApp automation?
WhatsApp automation means letting software send and reply to WhatsApp messages according to rules you set, instead of a person typing each one. In practice it covers several distinct mechanisms: keyword-triggered flows, timed drip sequences, follow-ups that start when a contact's status changes, and automatic away messages outside business hours. They solve different problems, so most businesses end up using more than one.
What is the difference between a flow, a journey and a follow-up?
A flow is triggered by something the contact does right now, usually a keyword they send, and plays out inside that conversation. A journey is a multi-step sequence spread over time, triggered either on a schedule or by a date on the contact record such as a birthday. A follow-up is triggered by a change of status on the contact — moving from enquiry to quoted, for example — and runs its steps in order from there.
Can I automate birthday and anniversary messages?
Yes. Date of birth and anniversary are standard fields on the contact record in ChatSetu AI, and journeys can use a date-based trigger, so the sequence fires relative to that date for each contact. You build the journey once and it keeps running as your contact list grows.
Will automated messages break Meta's rules?
Not if you follow the platform rules, which apply to automated and manual messages equally. You need opt-in before messaging someone, and outside the 24-hour customer service window you can only send an approved message template in the right category — marketing, utility or authentication. Automation does not change those rules; it just means the software applies them consistently.
Do I need to know how to code to build an automation?
No. Flows, journeys and follow-ups are configured rather than programmed. ChatSetu AI also includes AI flow generation, where you describe the automation you want in a sentence and the system builds the flow graph for you to review and edit before anything goes live.
What happens when automation cannot answer the question?
It should hand over to a person, and the handover is the part most setups get wrong. In ChatSetu AI the conversation moves into the shared team inbox, and auto-assignment settings decide which agent or department receives it, so the customer is not left waiting on a bot that has run out of answers.
Put the repetitive half of WhatsApp on autopilot
Create your account, or message us on WhatsApp and we'll help you build your first flows when we onboard you.