On this page
- How to read the evidence labels in this guide
- What "WhatsApp automation" actually means
- WhatsApp Business app vs WhatsApp Business Platform
- The messaging rules to understand first
- A WhatsApp automation decision flow
- What to automate and what to keep human
- Two workflow concepts
- WhatsApp, CRM and n8n: how the pieces could connect
- A worked example
- Failure and handover points
- What we have actually tested at AI Spark
- A beginner checklist before you automate WhatsApp
- Want help planning this?
- Frequently asked questions
- Sources
Many businesses get enquiries on WhatsApp, and answering the same questions again and again is tiring. Automation can help with that. It can also go wrong in ways that are easy to miss: messaging people who never agreed to be messaged, sending a confident reply that is simply wrong, or leaving a customer talking to a bot with no way to reach a person.
This guide is for owners who want to understand WhatsApp automation before they build or buy anything. It explains the two WhatsApp products, the messaging rules that matter, what to automate and what to keep human, and how a WhatsApp, CRM and n8n set-up could fit together. It also says plainly what we have tested ourselves, which for WhatsApp is nothing yet.
Key takeaways
- There are two products: the WhatsApp Business app (built-in tools such as greeting and away messages) and the WhatsApp Business Platform (an API for connecting WhatsApp to other software).
- You need permission before messaging people, and outside the 24-hour customer service window only pre-approved template messages are allowed.
- Save the lead first, then decide what to send, and keep a person in the loop for anything sensitive.
- Always give customers a clear way to reach a human.
- Ai Spark has not completed a production WhatsApp automation test. The platform details here come from official documentation.
How to read the evidence labels in this guide
| Label | Meaning |
|---|---|
| TESTED BY AI SPARK | We ran it ourselves and saw the result. The limits are stated. |
| OFFICIAL SOURCE ONLY | It comes from Meta's, WhatsApp's or n8n's own documentation, listed under Sources. We did not test it. |
| ILLUSTRATIVE EXAMPLE | Made up to explain an idea. Not a client, not a result. |
| NOT TESTED | We have not tried it, so we do not describe how it behaves. |
Platform rules change. Everything marked official was checked on 29 October 2026, and you should check the current pages before you build.
What "WhatsApp automation" actually means
People use the phrase for three quite different things. Separating them makes every later decision easier.
| Layer | What it is | Example |
|---|---|---|
| 1. Built-in app tools | Simple automatic features inside the WhatsApp Business app. | A greeting message, an away message, saved quick replies. |
| 2. Workflow behind the scenes | Software reacts to a message or an enquiry and does admin work. | Save the lead to a sheet or CRM, create a task, alert a person. |
| 3. Automated replies | Software, sometimes an AI model, writes or sends a message to the customer. | A drafted answer to an opening-hours question. |
Layer 2 is usually the safest place to start, because nothing is sent to a customer. Layer 3 is where most of the risk sits.
WhatsApp Business app vs WhatsApp Business Platform
WhatsApp's own pages describe the app as a set of built-in business tools: a business profile, a catalog, labels, quick replies, a greeting message and an away message. OFFICIAL SOURCE ONLY. The Platform is different. Meta describes it as a developer-facing set of APIs for messaging customers at scale, built on its Graph API, where incoming messages and delivery updates arrive through webhooks. OFFICIAL SOURCE ONLY.
| WhatsApp Business app | WhatsApp Business Platform | |
|---|---|---|
| What it is | An app with built-in business tools | APIs that let software send and receive WhatsApp messages |
| Automation you get | Greeting, away message, quick replies, labels | Whatever the software you connect can do |
| Connecting to a CRM or n8n | Not part of the built-in tools listed above | Yes, through the API and webhooks |
| Who sets it up | You | A developer, or a third-party tool that handles the connection |
The Meta page we read is written for developers and points non-technical businesses to WhatsApp's separate business website for non-API options. It does not explain third-party providers, so we cannot tell you how any particular provider works, what it costs or whether you can keep your current number. Ask the provider and read its own documentation.
Start with the app if you can. If a greeting, an away message and a few quick replies already cover your busiest questions, you may not need the Platform yet.
The messaging rules to understand first
We summarise Meta's and WhatsApp's documentation in our own words. This is general information, not legal advice. You are responsible for following the laws that apply to your messages, and they differ by country.
- Permission comes first. Meta's documentation says a business must have a person's permission before messaging them on WhatsApp. The opt-in should make clear the person agrees to hear from you and name your business. You choose how to collect it, such as a website form, SMS, in person or on paper, as long as it complies with the laws that apply to you. OFFICIAL SOURCE ONLY.
- Stop requests must be honoured. WhatsApp's business policy says you must respect requests to block you, stop messages or opt out, whether the request is made on or off WhatsApp. Meta also suggests separate opt-ins for different message types and clear opt-out instructions. OFFICIAL SOURCE ONLY.
- The 24-hour customer service window. A 24-hour period starts when a person messages you, and each new message from them restarts it. Inside the window you can send free-form service messages, so a template is not required. Outside it, only pre-approved template messages are allowed. OFFICIAL SOURCE ONLY.
- Templates are reviewed. Templates fall into marketing, utility or authentication categories and are reviewed when created or edited. Meta says review can take up to 24 hours and that an approved template's status can still change later. OFFICIAL SOURCE ONLY.
- Automation needs a route to a person. WhatsApp's business policy allows automated replies within the 24-hour window, but expects you to give customers clear ways to reach a human. OFFICIAL SOURCE ONLY.
- Bad behaviour gets limited. Meta describes escalating enforcement, from warnings to temporary restrictions and, in serious cases, removal. Excessive negative feedback from users can also trigger limits. OFFICIAL SOURCE ONLY.
- Avoid unofficial tools. WhatsApp's messaging guidelines restrict unofficial clients and automation used to harm WhatsApp or its users. Tools that imitate a person on an ordinary account are a risk. Use the official app or the official Platform. OFFICIAL SOURCE ONLY.
A WhatsApp automation decision flow
Before any message is sent by software, a lead passes through six questions. This is our own planning model, not a Meta diagram.
Which messaging path applies?
| Situation | What the documentation says you can do | Safe default |
|---|---|---|
| The customer messaged you in the last 24 hours | Free-form replies are allowed, so a template is not required. | Reply, with a way to reach a person. |
| The window has closed, and the customer gave permission | Only an approved template message. | Use a template, or let a person decide. |
| You have no clear permission | Permission is required before you message them. | Do not message. Collect consent properly first. |
| The customer asked you to stop | You must honour the request. | Stop automated messages, and record it. |
What to automate and what to keep human
Not every conversation should be automated. Use automation for tasks that are repetitive and low-risk, and keep a person on anything where a mistake is costly or the customer needs judgement.
| Area | Automate or assist | Keep human |
|---|---|---|
| Capturing the lead | Save name, number, enquiry and source to a sheet or CRM. Alert a person. | Judging whether the lead is a fit. |
| Common questions | Opening hours, location, how to book. A saved answer or a draft a person approves. | Anything the saved answer does not cover. |
| Booking and reminders | A booking link, and reminders to people who agreed to receive them. | Rescheduling exceptions. |
| Prices | Sharing a published price list. | Custom quotes, discounts and pricing exceptions. |
| Complaints and refunds | Alert a person and log it. | The whole conversation. |
| Sensitive topics | Nothing automatic. | Legal, medical, financial or safety statements. |
| AI-written replies | Drafts only, for a person to read. | Approval before anything high-risk is sent. |
| Customers who ask for a person | Hand over at once. | Yes, always. |
On AI replies: Anthropic's documentation says AI models, including Claude, can produce text that is factually incorrect, and that its techniques reduce this without removing it. OFFICIAL SOURCE ONLY. That is why we treat AI output on WhatsApp as a draft until you have checked it for your own business.
Two workflow concepts
These are concepts, not systems we have built.
A lead-response workflow
- A new enquiry arrives from a form or an incoming WhatsApp message.
- The lead is saved to a sheet or CRM before anything else happens.
- The workflow checks whether the person has given permission and whether the 24-hour window is open.
- It prepares a draft reply from a template or saved answer.
- A person reads, edits and sends the reply.
- The status is updated, and a follow-up reminder goes to you, not automatically to the customer.
A support workflow
- A customer asks a question.
- The workflow matches it to a saved answer, such as opening hours.
- If there is a clear match, it prepares or sends that answer inside the window. If not, it alerts a person.
- Keywords such as "refund", "complaint" or "speak to someone" always go to a person.
WhatsApp, CRM and n8n: how the pieces could connect
n8n's documentation lists a WhatsApp Trigger node that starts a workflow when events happen in WhatsApp, including incoming messages, and a WhatsApp Business Cloud node that can send a message, send a template and send a message then wait for a response. Both use WhatsApp Business Cloud credentials. OFFICIAL SOURCE ONLY. The "send and wait" option supports an approval response, which matches the human-review step in our flow.
Customer message
→ WhatsApp (Platform / Cloud API webhook)
→ n8n WhatsApp Trigger
→ save the contact and message to a sheet or CRM
→ check consent, the 24-hour window and stop words
→ prepare a draft reply
→ send for approval (a person)
→ send the approved reply, or hand over to a person
→ update the statusn8n's documentation also warns about real setup traps. WhatsApp allows one webhook per app, and switching between n8n's test and production URLs overwrites the registered one, so a published workflow and a test run cannot both receive events. Publishing registers a webhook on your Meta app but does not subscribe the app to your WhatsApp Business Account, and if it is not subscribed, messages never arrive. OFFICIAL SOURCE ONLY. We mention them so you know to test early. We have not hit them ourselves.
If you have never built an n8n workflow, start with our tested lead follow-up tutorial. It uses a form, Google Sheets and a Gmail draft, not WhatsApp, but it shows the "save first, then draft, then review" pattern. See also CRM automation workflows and, for the basics, What is AI automation?
A worked example
ILLUSTRATIVE EXAMPLE — NOT A CLIENT CASE STUDY. "Maple Street Alterations" is a made-up clothing repair shop. Ai Spark has not built or run this workflow. No message volumes, response times, revenue or conversion results are claimed.
| Step | What happens |
|---|---|
| New enquiry | A customer sends a WhatsApp message asking whether the shop can shorten a coat and how to book. |
| Data capture | The workflow saves the phone number, the message text, the time and the source "WhatsApp" to a sheet, with the status "New". |
| Automation decision | The customer messaged first, so the window is open. The question matches a saved answer about booking. The coat repair needs a price, so the workflow does not guess one. |
| Human review | The owner gets an alert with a draft: the booking link and a line saying a price will follow after the coat is seen. The owner edits and approves it. |
| Message and follow-up concept | The approved reply goes out. The status becomes "Replied". If there is no answer, a reminder goes to the owner, who decides whether to follow up. |
| Stop or handover condition | If the customer writes "complaint", "refund" or "speak to someone", or asks to stop, automation stops and a person takes over. A stop request is recorded so no later message is sent. |
A draft the owner might approve, written as a concept:
Hi, thanks for getting in touch with Maple Street Alterations.
You can book a fitting here: [booking link]
We will confirm the price once we have seen the coat.
Reply "person" at any time and someone will take over.Failure and handover points
| What can go wrong | Why it matters | Safe default |
|---|---|---|
| The customer asks for a person | Automation is expected to offer a route to a human. | Hand over at once. |
| The 24-hour window has closed | Free-form replies are no longer allowed. | Template only, or a person decides. |
| A template is rejected or its status changes | You cannot send it. | Alert a person, and do not retry blindly. |
| The customer opted out | You must honour the request. | Record it and stop automated messages. |
| An AI draft is wrong | AI text can be factually incorrect. | A person reads it before it is sent. |
| Messages stop arriving in n8n | The webhook or subscription may not be set up correctly. | Alert a person if no message arrives when one is expected, and check the setup. |
| The same message is handled twice | A duplicate can confuse a customer. | Save the message first and check for duplicates. |
What we have actually tested at AI Spark
Ai Spark has not completed a production WhatsApp automation test. We have not deployed a WhatsApp automation for a client, and this guide does not claim we have.
| Item | Status | What this means |
|---|---|---|
| WhatsApp Platform set-up, templates and webhooks | NOT TESTED | Everything about them here is OFFICIAL SOURCE ONLY. |
| n8n WhatsApp Trigger and Business Cloud nodes | NOT TESTED | We describe them from n8n's documentation only. |
| AI-written WhatsApp replies | NOT TESTED | Treat them as drafts. |
| Third-party WhatsApp providers, pricing and number migration | NOT TESTED | Ask the provider and check current rates. |
| TESTED BY AI SPARK (not WhatsApp): an n8n lead follow-up workflow, run on 18 October 2026 on self-hosted n8n Community Edition 2.33.6 | Execution #2689 succeeded in 5.076 seconds. The lead was saved first and a Gmail draft was created. No email was sent. | It shows the save-first, draft-for-review pattern on one test run. It did not include WhatsApp, publishing, live sending or AI. See the tutorial. |
A beginner checklist before you automate WhatsApp
- Write down your ten most common questions and your best answers. This helps whatever you choose.
- Set up the free app tools first: a greeting message, an away message and quick replies for the common questions.
- Decide what stays human using the table above.
- Check permission. How will people agree to hear from you, and where will you record it?
- Plan the stop route. What happens when a customer asks you to stop or asks for a person?
- Choose the route (the app, a provider, or the Platform with a developer) after you know what you need.
- Save leads before replying, so a failure never loses an enquiry.
- Test with your own number and fake data before any customer is involved.
- Start with drafts and approval before any fully automatic reply.
- Review the results and read real conversations, not only counts.
For the free app, two short messages in your own words are enough to start. For example, a greeting such as "Thanks for contacting [Business name]. Tell us what you need and a team member will reply soon", and an away message such as "We are closed right now and will reply from [time]". Keep them honest about when a person will answer.
If you are still deciding what is worth automating at all, our automation audit is a good place to start.
Want help planning this?
If you would like a second pair of eyes on your lead capture, follow-up and messaging process, Ai Spark can map it on paper with you and tell you what we think is worth automating and what is not. We make no promise about results, because they depend on your business. Get in touch and tell us how customers contact you today.
Frequently asked questions
Is the WhatsApp Business Platform free?
Not entirely. Meta's pricing page says it charges per message for messages from businesses to customers, based on the message category and the recipient's country, while messages from customers are free. It also lists free service-message allowances and says rates can change. Check the current rate card, because we do not quote prices here.
Do I need permission before I reply to a customer?
Meta's documentation says a business needs permission before messaging people on WhatsApp. When a customer messages you first, a 24-hour window opens in which free-form replies are allowed. We have not found documentation that says more than that, so check the current rules and the laws where you operate, and get clear permission before you start a conversation yourself.
Can I automate my normal WhatsApp account with a browser extension?
We recommend against it. WhatsApp's guidelines restrict unofficial clients and automation used to harm WhatsApp or its users, and the risk to your number is not worth it. Use the official Business app or the official Platform.
Can AI answer my customers on WhatsApp?
Technically it can be connected to the Platform, but we have not tested it, and AI text can be wrong. Start with drafts that a person approves, and always offer a way to reach a human.
Do I need n8n to automate WhatsApp?
No. The built-in app tools need no extra software, and other tools and providers can connect to the Platform. n8n is one option with documented WhatsApp nodes, which we have not tested ourselves.
Can I keep using my current number?
We do not know, and we have not verified it. It depends on the route you choose, so ask the provider or check Meta's current documentation before you change anything.
Sources
- Meta for Developers: About the WhatsApp Business Platform (checked 29 Oct 2026)
- Meta for Developers: Service messages (checked 29 Oct 2026)
- Meta for Developers: Template fundamentals (checked 29 Oct 2026)
- Meta for Developers: Get opt-in for WhatsApp (checked 29 Oct 2026)
- Meta for Developers: Policy and spam enforcement (checked 29 Oct 2026)
- Meta for Developers: Pricing on the WhatsApp Business Platform (checked 29 Oct 2026)
- WhatsApp Business Policy (checked 29 Oct 2026)
- WhatsApp Messaging Guidelines (checked 29 Oct 2026)
- WhatsApp Business: Small business use of the WhatsApp Business app (checked 29 Oct 2026)
- n8n Docs: WhatsApp Trigger (checked 29 Oct 2026)
- n8n Docs: WhatsApp Business Cloud node (checked 29 Oct 2026)
- Claude Platform Docs: Reduce hallucinations (checked 29 Oct 2026)
Ai Spark is not affiliated with Meta or WhatsApp. Last reviewed 29 October 2026. Our own tests are described in the section "What we have actually tested at AI Spark".