WhatsApp automation glossary: triggers, steps, takeover, the 24-hour window and more
WhatsApp automation has its own vocabulary. A trigger decides what starts an automation: a message, a tag or a webhook call, steps decide what goes back, takeover pauses it when a person replies from the phone, and the 24-hour window decides when replies other than templates may go out. Templates, opt-in, run statuses, skip reasons and signed webhooks complete the picture, and each term here takes one line.
easyCoexistence connects your WhatsApp Business number to Meta's Cloud API through Coexistence and runs automations on it with the vocabulary above: four matches, 19 step types, takeover when you reply from the phone, and a 30-day run log with skip reasons.
Ways a WhatsApp automation can pick incoming messages: Every message, Has keyword, First message and After hours.
Step types on a number, from Reply with text and Send a template to Ask a question, Split into paths and Agent answers.
Most steps one line of an automation can hold, 60 in all, with branches nested up to 4 deep.
Meta's customer service window: non-template messages are allowed only within 24 hours of the customer's last message.
Meta's template categories: marketing, utility and authentication.
Skip reasons a run can show, from a recent reply from your phone to an AI key that stopped working.
Which terms describe the connection behind automations?
Automations run on a number that is connected to Meta's API while it stays in the WhatsApp Business app. These six terms describe that connection and where the number's incoming messages go:
- Coexistence: Meta's onboarding that connects a number already in the WhatsApp Business app to the Cloud API, so the app and software share the number and its chats.
- Cloud API: Meta's hosted API for sending and receiving WhatsApp Business messages; the official route for software.
- Inbound mode: where a number's incoming messages go, shown on its page under Where incoming messages go as Through easyCoexistence or Straight to your system.
- Through easyCoexistence (managed): Meta delivers to easyCoexistence, automations and Conversations can use the messages, and an optional Forward URL gets a signed copy.
- Straight to your system (direct): Meta posts the number's messages straight to your own webhook destination, and automations are off.
- Forward URL: your HTTPS endpoint that receives each incoming change of a managed number, signed with X-EC-Signature.
What are the building blocks of an automation?
An automation is a trigger and a flow of steps on one number. The trigger names the event and the match narrows it down; only one automation answers a given message, by priority. These are the names the editor uses under "When a message arrives":
- Automation: one trigger plus a flow of up to 30 steps per line, 60 in all, on one number, switched On or Off as a unit.
- Trigger: the event that starts an automation; on a WhatsApp number, A message arrives, A contact gets a tag or Your system calls a URL.
- Every message: the catch-all match, for whatever the customer writes.
- Has keyword: runs when the message matches one of up to 30 keywords; capital letters do not matter.
- Keyword mode: Contains (anywhere in the message), Starts with (at the start) or Is exactly (the whole message).
- First message: runs on a chat with no history, including a regular's first message after automations go on, or after about 30 quiet days.
- After hours: runs while you are closed, from a Timezone, Open on days and From / To times in 24-hour format.
- Priority: the order that picks one automation: keyword, then First message, then After hours, then the catch-all, oldest first.
What does each step type mean?
Steps run in order, top to bottom, after the Trigger block, and two of them branch: Split into paths (by rules on text, fields, tags or hours) and AI picks the path (by meaning) each hold a line of steps per path plus an Otherwise line. A line holds up to 30 steps, 60 in all, with branches nested 4 deep. A number takes 19 step types; besides the ones below, the editor offers Ask a question (up to 3 tappable buttons, waits for the answer and saves it in a contact field), Agent answers, Hand to a person (pauses the bot on the chat and emails you), Notify me, Send a picture or file, Save to contact, Tag, AI saves details, Call an API, Start automation and Go back to a step. These are the core step types and their words:
- Reply with text: a fixed message of up to 4,096 characters, sent as written.
- Variables: {{
first_name}}, {{name}}, {{message}} and {{phone}}, plus {{contact.field}} for a saved contact field and {{vars.name}} for an earlier step's answer, filled in when the step runs. - Send a template: sends an approved template of the number, with positional body variables; works outside the 24-hour window.
- Reply with AI: your own model, on your Anthropic, OpenAI or OpenRouter key, writes the reply.
- Instructions: the AI step's prompt, or an agent's, up to 20,000 characters; an agent can also draw on knowledge files, links and text.
- Call my webhook: posts the message and up to 10 recent messages of the chat to your URL, and sends back a reply received within 20 seconds.
- Wait: pauses the run for 1 to 1,380 minutes, which is 23 hours, before the next step.
- Stop: ends the run; allowed only as the last step of its line.
Which rules and limits have their own names?
Some words come from Meta and apply to any business on WhatsApp; others are settings under Advanced in the automation editor. Both decide whether a reply goes out at all, so they are worth knowing by name:
- 24-hour window: Meta's customer service window; messages other than templates are allowed only within 24 hours of the customer's last message.
- Template: a message format Meta reviews in advance, in the marketing, utility or authentication category; needed to write first or after 24 hours.
- Opt-in: the person gave you their number and agreed to receive your messages, which Meta requires before you message first.
- Echo: Meta's
smb_message_echoeswebhook, reporting a message you sent from the app or a linked device. - Takeover: the pause after you reply from the phone or from Conversations, set in "Pause on a chat after I answer it (hours)", 4 by default, 0 to 168.
- AI reply limit: "AI replies per chat per hour, at most", 10 by default, 1 to 60.
- Tokens: the units AI providers bill; "Longest reply (tokens)" caps one reply, 600 by default, 50 to 2,000.
- 14-day rule: Meta disconnects a Coexistence number whose app is not opened on the phone for about 14 days.
What do the run log terms mean?
Each time an automation starts on a message, it leaves a run in the Runs tab, kept for 30 days, with every step's output, timing and tokens. These words explain what you see there:
- Run: one execution of an automation on one incoming message, tag or webhook call, or on a test.
- Run status: Queued, Running, Waiting (parked in a Wait step), Done, Failed or Skipped.
- Skip reason: why a run stopped on purpose, such as "You answered this chat from your phone recently".
- Test it / Try it: runs the saved steps on a sample message; nothing is sent, but the AI and webhook really run.
- Paused: the status of an automation whose AI key the provider refused; it restarts once a working key is saved.
- Superseded: a waiting run cancelled because a newer customer message started the same automation again.
Common mistakes
- Reading Paused as Off. Paused means the AI key stopped working; the automation restarts by itself once a working key is saved, while Off stays off until you switch it.
- Treating the app's away message and After hours as the same thing. One lives in the phone app and software cannot see it; the other is an automation on the API side.
- Expecting First message to fire only for brand-new contacts. It fires for any chat with no stored history, regulars included.
Build them yourself in the editor or by asking your AI, on your own key. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
What is the difference between an automation and an AI agent?
An automation is a trigger and steps, even when it branches: every path is one you drew. An AI agent decides its own next action. An Agent answers step puts one of your agents inside an automation, with its instructions, knowledge and tools such as saving a contact field or handing the chat to a person, while a Reply with AI step only writes the reply. A full agent of your own can also sit behind Call my webhook or a Forward URL.
Where do these terms appear in the dashboard?
Matches and keyword modes are in the Trigger block of the automation editor, and steps in the + menu between blocks. Takeover and the AI reply limit are under Advanced, runs and skip reasons in the Runs tab, and the inbound mode on the number's page.
Which of these terms come from Meta?
Coexistence, Cloud API, the 24-hour window, templates and their categories, opt-in, echoes and the 14-day rule are Meta's. Matches, steps, takeover, run statuses, skip reasons and X-EC-Signature are names used in the easyCoexistence dashboard and API.
What does X-EC-Signature mean?
It is the header that proves a webhook call or a forward came from easyCoexistence: t=<unix seconds>,v1=<HMAC-SHA256 of "<t>.<body>"> made with a secret only you hold. Your server recomputes it and compares before trusting the request.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on