Guides
WhatsApp auto reply and automation: a practical guide with recipes
Automation on WhatsApp is less about clever bots and more about getting the basics right: the 24-hour window, approved templates and a clear way to reach a person. Here is how it works, and eight recipes you can build today.
The Buddy Team · · 14 min read
Guides
Auto replies
A WhatsApp auto reply is a message your business sends automatically when something happens: someone subscribes, sends a keyword such as "price", or replies in a way that shows they are interested. On the official WhatsApp Business Platform you can automate replies inside the 24-hour customer service window. Outside it, including a welcome to a brand-new web subscriber, you must use a Meta-approved template.
That one rule explains most automations that fail silently. This guide covers the rules, how Buddy's automations work (the exact triggers, actions and branches), eight recipes you can copy, how to give people a route to a human, and what automated replies cost now that Meta charges for service messages.
What is a WhatsApp auto reply?
In practice, "auto reply" covers four jobs. Most businesses need all four before they need anything cleverer.
Welcome
Confirm a new subscription and tell people what they will get and how often. Sets expectations and reduces blocks later.
Keyword reply
Answer the questions you get every day (prices, opening hours, delivery areas, the course link) the moment someone asks.
Sort and tag
Label people by what they said, so the next campaign goes to the right group and the hot leads get a person fast.
Hand-off
Tell the team when a conversation needs a human, and tell the customer when to expect one.
The free WhatsApp Business app has simple greeting and away messages for a single phone. Once you have a team or a subscriber list, you need automations on the WhatsApp Business Platform that react to what people say and update your audience data as they go. Our guide to WhatsApp marketing platforms compares the options in detail.
What rules apply to WhatsApp automation?
Four rules from Meta decide what an automation may send and when.
1. The 24-hour customer service window
When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts. If the user messages or calls you again before the timer expires, the timer resets to 24 hours.
Inside the window you can send free-form text. When it closes, Meta's own documentation is blunt: "you can only send pre-approved template messages." That applies to automations exactly as it applies to people. A keyword reply is fine, because the customer just wrote to you. A follow-up three days later is not, unless it uses an approved message template.
2. A clear escalation path to a human
You may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths.
The policy lists acceptable routes: an in-chat transfer to a human agent, a phone number, email, web support, an in-store visit or a support form. Every automation that answers customers should make one of these obvious.
3. Opt-outs must be honoured
The same policy says you must respect every request "to block, discontinue, or otherwise opt out of communications from you via WhatsApp", whether it arrives on WhatsApp or anywhere else. Automations must never keep messaging someone who has asked you to stop.
4. No general-purpose AI chatbots
From 15 January 2026, WhatsApp's business terms bar general-purpose AI chatbots, where an AI assistant is the main thing being offered, from the WhatsApp Business Solution (TechCrunch). Structured business automation, the kind in this guide, is not affected.
Why must a WhatsApp welcome message be a template?
When someone subscribes on your website, opt-in page or QR code, they have given you permission, but they have not messaged you. No customer service window is open. So the first message you send them, the welcome, has to be an approved template. Free text sent at that moment will not be delivered.
The good news is that a plain confirmation can often be a utility template. Meta's categorisation guidelines list "Confirm opt-in to receive messages on WhatsApp as a follow-up to opt-in collected via other channels" as a utility use case, with the example "Thanks for confirming opt-in! You'll now receive notifications via WhatsApp."
Keep it that way. The same guidelines say templates with mixed content, such as a utility message with a promotion inside, are categorised as marketing. That matters for three reasons: marketing templates are always charged, WhatsApp may hold back marketing templates from people who already get a lot of them (per-user limits), and WhatsApp "does not currently deliver marketing template messages to WhatsApp users with United States phone numbers". A welcome with a discount code may simply never reach a subscriber in New York.
| Welcome wording | Likely category | Why |
|---|---|---|
| "Hi {{1}}, thanks for subscribing to Ada's Kitchen on WhatsApp. We'll send our weekly menu on Thursdays. Reply STOP at any time to unsubscribe." | Utility | Confirms the opt-in the person just made, sets expectations, no promotion. |
| "Welcome {{1}}! Here's 15% off your first order with code HELLO15." | Marketing | Contains an offer, so it is promotional. |
| "Thanks for joining, {{1}}. Our summer sale ends Sunday, shop now." | Marketing | Mixed content: a confirmation plus a promotion. |
How do Buddy automations work?
Every Buddy automation is a trigger followed by steps. You can build one as a simple list ("Quick") or on a visual canvas ("New flow"), where you drag steps, connect them and add if/else branches. Each automation can be switched between Active and Paused, and shows how many times it has run.
The three triggers
| Trigger (as shown in Buddy) | When it fires | Good to know |
|---|---|---|
| When someone subscribes | The first time a person opts in through your Buddy opt-in page or the Buddy Embed form on your website. | Does not fire for contacts you import by CSV, add by hand or add through the API, or for someone re-subscribing. No service window is open, so send a template. |
| When a message comes in | Any incoming WhatsApp message, or only messages containing a keyword you set. | Keyword matching is case-insensitive and matches anywhere in the message. Leave the keyword blank to match every message. |
| When a reply is categorized | An incoming message is sorted into Interested, Question, Purchased, Not now or Follow up. | Uses Buddy AI to read intent when it is enabled, and falls back to keyword rules when it isn't. |
One detail worth knowing: a message that is exactly STOP, unsubscribe or opt out is handled by Buddy's consent system first. The person is unsubscribed, the opt-out is logged on your Consent page, and no automation runs on that message.
The steps
| Step | What it does |
|---|---|
| Send a message | Sends free text, or an approved template with its variables filled in. Use {name} and {phone} in template variables to personalise. Templates with an image, video or document header are for campaigns, not automations. |
| Add a tag | Adds a tag to the subscriber, for example interested or vip. |
| Remove a tag | Removes a tag, for example moving someone out of interested once they buy. |
| Wait | Pauses the run for a number of minutes, up to 30 days, then carries on with the next step. |
| Notify the team | Posts an in-app notification to your workspace with a title and optional details. |
| Branch (if/else), canvas only | Splits the flow into Yes and No paths based on: the reply category is X, the message text is exactly or contains X, or the person has tag X. |
Buddy also includes three presets to start from: Welcome message, Keyword auto-reply (set up for "price") and Tag interested leads (adds an interested tag and notifies the team). Open one, adjust it and save.
Eight WhatsApp automation recipes you can build today
Each recipe below uses only Buddy's real triggers and steps. The businesses are hypothetical, but the set-ups work exactly as written once your number is connected and any templates are approved.
Recipe 1: Welcome every new subscriber
A bakery in Manchester puts a QR code on its boxes. Anyone who scans it and subscribes should get a confirmation straight away.
- 1Create a utility template such as "Hi {{1}}, thanks for subscribing to Crumb & Co on WhatsApp. We'll send our weekend bakes every Friday. Reply STOP to unsubscribe." and wait for approval.
- 2Create an automation with the trigger When someone subscribes.
- 3Add Send a message, choose the approved template and set {{1}} to
{name}. - 4Add Add a tag with the tag
new-subscriber, so you can greet this group in your next WhatsNew.
Recipe 2: A two-step welcome series
A course creator in Lagos wants new subscribers to get a confirmation now and a useful free lesson two days later.
- 1Trigger: When someone subscribes.
- 2Send a message with your approved welcome template.
- 3Wait 2,880 minutes (two days).
- 4Send a message with a second approved template that links to the free lesson. Two days have passed, so free text would not deliver. If the second message promotes a paid course, expect Meta to treat it as marketing.
Recipe 3: Keyword auto-reply for your most common question
A gym in Dubai gets "price?" twenty times a day. The customer has just messaged, so the window is open and free text works.
- 1Trigger: When a message comes in, keyword
price. - 2Send a message as free text: "Thanks for asking! Monthly membership is on our site: [your link]. Want a free trial class? Reply TRIAL and one of our team will book you in."
- 3Optional: Add a tag
asked-priceso you can follow up in a later WhatsNew.
Duplicate the automation for your next most common questions: hours, menu, delivery, link. Keep each keyword specific (see the mistakes section below).
Recipe 4: Tag interested leads and alert the team
A furniture shop in Mumbai sends a WhatsNew about a new collection. Anyone who replies with interest should reach a salesperson quickly.
- 1Trigger: When a reply is categorized, category Interested.
- 2Add a tag
interested. - 3Notify the team with the title "Hot lead" and details such as "Replied to the autumn collection".
- 4Optional: Send a message as free text: "Lovely! One of our team will message you shortly with sizes and prices."
Recipe 5: The human hand-off for questions
This is your escalation path in automation form. When someone asks a question, confirm a person will answer and tell the team.
- 1Trigger: When a reply is categorized, category Question.
- 2Send a message as free text: "Thanks for your question. A member of our team will reply here within two working hours. If it's urgent, call us on [number]."
- 3Notify the team with the title "Customer question waiting".
Only promise a response time you can keep. The reply itself happens in your team inbox.
Recipe 6: Move buyers out of your sales audience
A skincare brand in São Paulo targets its launch offers at the tag interested. People who say they have bought should stop getting the offer and start getting customer care.
- 1Trigger: When a reply is categorized, category Purchased.
- 2Remove a tag
interested. - 3Add a tag
customer. - 4Send a message as free text: "Thank you for your order! Reply here if you have any questions about using it."
Recipe 7: Respect a "not now"
Someone who replies "maybe later" is telling you something. Take them out of the push, without unsubscribing them.
- 1Trigger: When a reply is categorized, category Not now.
- 2Remove a tag
interested, so they drop out of the tag-targeted offer audience. - 3Add a tag
not-now, so you can send this group something gentler, such as your monthly newsletter, later on.
Recipe 8: One flow that routes every message (canvas)
A salon in London wants a single flow that answers booking requests, fast-tracks VIP clients and leaves everything else for the team. Build it on the visual canvas.
- 1Trigger: When a message comes in with the keyword left blank (every message).
- 2Branch: message text contains
book. Yes path: Send a message with the booking link. No path: go to the next branch. - 3Branch: has tag
vip. Yes path: Notify the team with "VIP client messaged". No path: end.
How do you give customers a route to a human?
Meta's policy requires a prompt, clear and direct escalation path whenever you automate. In Buddy that usually means three things working together.
- 1Say it in the message. Any automated answer should tell people how to reach a person: "Reply HUMAN", a phone number or a support email.
- 2Catch it. Add a keyword automation for
human(andagent,person) that uses Notify the team and replies with a realistic response time. - 3Answer it. Everyone on your team sees the conversation in the shared inbox and replies from the same number.
What do automated WhatsApp replies cost from 1 October 2026?
Until now, replies inside the customer service window were free, which made automated replies feel costless. That changes on 1 October 2026. Meta's pricing update says it "will charge on a per-message basis for service messages, consistent with how Meta charges for template messages", and utility templates sent inside the window become billable too, at the same rate. Messages sent in the 72-hour free entry point window after a Click-to-WhatsApp ad or a Facebook Page call-to-action stay free.
So every automated reply is now a line on your Meta bill. That doesn't make automation a bad idea, since an instant, accurate answer is usually worth far more than it costs, but it does reward tidy design:
- Answer in one message, not three.
- Avoid overlapping automations that reply to the same message twice.
- Use tags and team notifications (which cost nothing on Meta's side) for the sorting work, and send messages only when the customer benefits.
- Check where your costs come from in WhatsApp Manager, and read our breakdown of Meta's October 2026 pricing change.
Meta bills message fees directly to your own WhatsApp Business account. Buddy doesn't add a markup; Buddy's own plans are on the pricing page.
Common WhatsApp automation mistakes
| Mistake | What happens | Fix |
|---|---|---|
| Free-text welcome for web subscribers | The message is not delivered, because no window is open. | Use an approved template. Buddy warns you in the editor when a subscribe automation uses free text. |
| Free text after a long Wait | Anything sent more than 24 hours after the customer's last message fails. | Use a template for any step that runs after the window may have closed. |
| Very short keywords | Keywords match anywhere in the message, so hi also matches "this" and "which". | Use distinctive words (price, menu, booking) or ask people to reply with a code word. |
| A promotion inside the welcome | The template is treated as marketing: charged, subject to per-user limits, not delivered to US numbers. | Keep the welcome a pure confirmation and save offers for a WhatsNew. |
| No human route | Frustrated customers block or report you, which lowers your quality rating. | Add the escalation pattern above to every customer-facing automation. |
| Forgetting it's paused | Nothing runs. | Check the Active or Paused toggle and the run count on the Automations page. |
WhatsApp automation without a chatbot: where AI fits
You don't need a chatbot to automate WhatsApp well. Think of good automation as a well-organised receptionist: rules built from triggers, tags and templates answer the predictable, route the rest and behave the same way every time.
Buddy uses AI in two narrow places today. When Buddy AI is enabled, it reads the intent of incoming replies for the When a reply is categorized trigger, which copes better with typos, slang and other languages than keyword rules do. And in the Inbox, Suggest a reply with AI drafts a short answer from the recent conversation, which a person reviews and sends. Buddy never lets AI send on its own. We explain the approach, and what is planned next, in our guide to WhatsApp AI agents.
Frequently asked questions
Can I send an automatic welcome message on WhatsApp?
Yes, but when the person subscribed through a website, form or QR code rather than by messaging you, the welcome must be an approved template, because no 24-hour customer service window is open. A plain opt-in confirmation can often be approved as a utility template.
How do I set up a keyword auto reply on WhatsApp?
In Buddy, create an automation with the trigger "When a message comes in", enter a keyword such as price, and add a "Send a message" step with your answer. Because the customer has just messaged you, a free-text reply is allowed.
Are WhatsApp auto replies free?
Not from 1 October 2026. Meta now charges per message for service replies and for utility templates inside the customer service window. Messages in the 72-hour free entry point window after a Click-to-WhatsApp ad or Facebook Page call-to-action remain free.
Is WhatsApp automation allowed under Meta's policy?
Yes. Meta's Business Messaging Policy allows automation during the 24-hour window, as long as people have a prompt, clear and direct way to reach a human. General-purpose AI chatbots are barred from 15 January 2026, but structured business automation is not.
Can Buddy automations trigger on purchases or abandoned carts?
Not today. Buddy automations start when someone subscribes, when a message comes in, or when a reply is categorised. Store and payment triggers depend on Buddy Connect integrations, which are coming. Until then, you can tag buyers and send scheduled WhatsNews to a tag.