← All posts

WhatsApp Automation: The Rules and Timing That Keep You Safe

WhatsApp Automation: The Rules and Timing That Keep You Safe

A WhatsApp number that sends the wrong message at the wrong hour loses more than one customer, because Meta can limit or restrict the account behind it. Good WhatsApp automation is a rulebook about timing, consent and templates, and the AI model is the smallest part of it.

Most guides explain what a bot is and which chats to hand it. This post covers the rules instead: the 24-hour window, template approval, office hours, keyword rules that run before the AI, capped follow-ups and order-event messages.

Tendabot is built around that rulebook, so we use it for examples, but the rules apply to any setup. If you are a small team answering "where is my order" by hand, the rules decide whether automation helps you or gets your number flagged.

Table of Contents

Why Is WhatsApp Not an Email-Blast Channel?

Most small teams do not need more messages. They need the right message at the right moment, and WhatsApp punishes the opposite. Email tolerates a weekly blast to a purchased list. WhatsApp does not, and Meta restricts or bans accounts that spam.

Why Is WhatsApp Not an Email-Blast Channel? - whatsapp automation

Three things decide how much freedom a number keeps. The first is opt-in: the customer must have agreed to hear from you on WhatsApp. The second is template approval, since Meta reviews the wording of business-initiated messages before you can send them. The third is customer behaviour. If people block or report your messages, your account pays for it.

Every rule in this article follows from one line. A conversation starts when the customer writes to you, and you have wide freedom to answer. A notification starts when you write first, and you get narrow freedom, limited to approved templates about something the customer actually asked for or bought.

Automation belongs on the conversation side and on order-event notifications. It does not belong in mass campaigns. If you want campaign detail, our posts on WhatsApp broadcast and WhatsApp Business API pricing cover it, so we will not repeat that here.

The 24-Hour Window and Template Rules

How the customer service window works

When a customer messages you, a 24-hour customer service window opens. Inside it you can send free-form replies: text, images, links, whatever answers the question. Each new customer message restarts the clock.

At hour 25, free-form messages stop. You can only send an approved template, and only for a reason Meta allows. A bot that replies to a message sent yesterday evening may be talking into a closed window without anyone noticing.

Templates versus free-form replies

Free-form is for replying. Templates are for starting or restarting. "Meta-approved" means Meta reviewed the exact wording and category, and approval takes time. A rejected template is the failure that catches people out: your "order shipped" flow looks live in the dashboard, but nothing reaches customers.

Which setup controls the rules

The setup you pick decides who enforces these rules.

  • WhatsApp Business app: free, with greeting messages, away messages, quick replies and labels. It suits one owner replying by hand.
  • WhatsApp Business Platform: the layer for a shared inbox, AI, order lookup, templates and several operators.
  • Coexistence: the number keeps working on your phone while automation runs alongside it. Other vendors now offer this too, and it matters if you still answer from your handset.
  • A separate API number: a clean break, but your old chat history stays behind.

Three cost layers

Costs come in layers. Meta charges per delivered template message, the automation platform charges a fee, and the AI model uses tokens. Under Meta's current rules, free-form replies inside the 24-hour window are free, and so are Utility templates sent inside an open window. Rates vary by market and category.

Marketing templates are billed even inside the window, and Meta revises these rules, so check its published rate card for your market. Judge any tool by cost per resolved request, not the monthly subscription price.

WhatsApp Business Automation Rules That Run Before the AI

The cheapest and safest reply is one the AI never generates. Predictable questions should hit a fixed rule first, and the model only sees what is left. That is the core of dependable WhatsApp automated messages: a small set of rules you wrote, then a model for everything else.

WhatsApp Business Automation Rules That Run Before the AI - whatsapp automation

Office hours

Decide what the bot does in three states. During hours it answers. Outside hours it can collect details such as order number and issue, then queue the thread for a person. The away message should promise only what you control, like "we reply from 9:00 on weekdays", and never an invented response time.

Keyword rules

Rules like "hours", "returns policy" and "track my order" should return a fixed answer written by you. A fixed answer cannot hallucinate and costs no tokens. Keep the list short and test it with typos and plural forms. This is also the fastest way to automate WhatsApp customer support replies without risking a wrong answer on the basics, and a WhatsApp auto reply setup is where most teams start.

Pro Tip: Write keyword answers from your published policy text, not from memory. When the policy changes, the rule and the page change together, and the bot cannot contradict your own site.

Auto-resolve for idle threads

Close threads that go quiet so your inbox shows real work. Pick a wait that fits the topic, perhaps a day or two for order questions and longer for sales talks. The closing message should say how to reopen the chat. A late reply then reopens the same thread, with its history, instead of starting a stranger.

Where takeover sits

A sensible order is this:

  1. If a person has taken over the thread, the bot stays silent.
  2. Keyword rules fire next.
  3. Office hours decide whether to answer or collect details.
  4. Only then does the AI reply, from your knowledge base.

The customer sees one WhatsApp thread on one number. Tendabot gives you a shared team inbox where a teammate can step in and hand the thread back to the AI. Your team's own replies are free and never metered.

Follow Up and Move Pipeline Stages Without Nagging

Follow-ups are where automation turns into spam. Three limits keep them polite: space them out, cap the attempts, and stop the moment the customer replies or opts out. Two or three attempts over several days is a courtesy. Ten is a complaint waiting to happen.

Pipeline moves

A lead can move between stages automatically based on what was said or done. A B2B buyer who gives company size and a timeline can move from "new" to "qualified", and a WhatsApp sales bot for B2B can collect those details before a person ever calls.

Anything touching price, discounts or commitment should wait for a person to confirm. If you want the stages tracked in one place, a WhatsApp CRM view keeps them next to the conversation.

The template trap

A follow-up sent after the 24-hour window needs a template. One template follow-up is fine. A habit of sending them to everyone who went quiet looks like marketing, and Meta treats unwanted marketing as spam. Reserve template follow-ups for leads who asked for a quote or a callback.

What a follow-up sequence costs

We can describe the shape without inventing figures. While the plan has included bot replies left, each follow-up draws from that allowance. Meta's delivered-message charge applies on top for template sends. When the allowance runs out, the bot pauses politely instead of generating an overage bill, and your team keeps replying for free. Read the included reply count on the pricing page, then multiply by your real sequence length.

A WhatsApp Automation Tool for Shopify and WooCommerce Orders

Order updates are the safest proactive messages, because the customer just bought something. Each event maps to a Meta-approved template filled with data from the store's own order record. This is the practical side of WhatsApp order updates for Shopify and WooCommerce stores.

  • Order confirmed: receipt and expected next step.
  • COD confirmation: asks the buyer to confirm a cash-on-delivery order.
  • Shipped: sent when the store adds tracking to the order.
  • Out for delivery: sent when the store records that status.
  • Delivered: sent when the store records the order as delivered.

COD confirmation as a rule

Treat this as a rule, not a conversation. The customer gets a short question with a clear confirm or cancel answer. Decide in advance what silence does. We would hold the order for a person to review rather than cancel it automatically. The result lands in the shared inbox where your team can see it.

Identity-verified lookup

On Pro and Scale, order lookup verifies the customer before reading out any status. The customer gives the order number plus the email or phone used at checkout, and both must match before anything is shared. Address changes, cancellations and refunds become structured requests that go to a person, with an email transcript. The AI collects details but does not decide.

What may be answered, collected or handed off

  • Answer: policies, hours, product questions, and order status after verification.
  • Collect: address changes, cancellation requests, refund reasons.
  • Always hand to a person: refund approval, complaints, delivery exceptions, upset customers.

Where the data travels

  1. The customer writes on WhatsApp, and the message passes through Meta.
  2. The agent reads your knowledge base and, after verification, your store's order data.
  3. The selected model provider receives the prompt and returns a draft reply.
  4. The thread appears in the shared inbox for your team.

Ask any vendor about retention, model training, subprocessors, deletion and payment-data redaction.

Scope matters. Updates come from the store's order data. Tendabot does not track carriers or print labels. When a customer asks about a delivery exception, the bot should say it cannot see carrier details and pass the thread to a person.

Where This Setup Falls Short

A solo owner who answers a few chats a day does not need any of this. The free WhatsApp Business app, with a greeting and an away message, is enough. Add automation when repeat questions eat real hours.

Some limits are plain:

  • Templates need approval time, so submit them before you need them.
  • Rules cannot read a customer's mood, so angry messages need a person.
  • A stale knowledge base produces a confident wrong answer.
  • Model choice affects answer quality, speed and cost, so test before you commit.

A first-week rollout keeps risk low:

  1. Read your last 100 chats and list the five most repeated questions.
  2. Set office hours and a few keyword rules.
  3. Turn on order confirmation templates.
  4. Review real transcripts daily and fix wrong answers.
  5. Add capped follow-ups only after that.

Tendabot runs one AI agent across website chat, WhatsApp and email, with a shared human inbox. It runs on a choice of models from many providers, billed at the provider's real token cost with no markup. Compare options at tendabot.com/models. When the plan's replies run out, the bot pauses instead of billing overage. To try this WhatsApp automation rulebook on your own number, start with the 300 free credits, no card needed.

Frequently Asked Questions

Can I automate WhatsApp without losing the number I already use on my phone?

Yes, through coexistence. The number keeps working on your phone while automation runs alongside it. Check what carries over, such as chat history, before you connect.

Do automated replies cost money, and who charges what?

Three parties can charge. Meta bills delivered template messages by category and market, the platform bills a fee, and the AI model uses tokens. Add them up per resolved request.

What happens to a message that arrives after the 24-hour window closes?

A customer's new message opens a fresh window, so you can reply freely again. The problem is only when you write first after hour 24. Then you need an approved template.

Can I send a promotion to everyone who messaged me last year?

No. WhatsApp is not an email-blast channel, and Meta restricts accounts that spam. Marketing needs opt-in and approved templates, and mass sends to old contacts risk blocks and reports.

How do I stop the bot from promising a delivery date it cannot know?

Give it only the store's order data and tell it to say what it cannot see. For delivery exceptions, add a rule that hands the thread to a person. The bot should never guess at carrier status.

Try it

Put an AI agent on your site in minutes.

300 free credits. No card. Cancel whenever.

Start free
Ready when you are

Your first agent, answering in five minutes.