We build WhatsApp automation on the official Business API: order updates, support replies, lead capture, appointment reminders, connected to your store, your CRM, and your helpdesk. Compliant with Meta's rules, costed before you commit, and monitored after launch.
Live in 3–4 weeks · Official Business API, no unofficial workarounds
Your Business
via WhatsApp Business Platform
Hi, where's my order #4482?
Your order shipped yesterday and is on the way. Tracking: SPX-4482. Arriving Thursday.
It says delivered but I never got it. This is really frustrating.
I'm really sorry about that. I've flagged this to Priya on our support team, she'll message you within the hour.
Trusted by teams in the US, UK, and India
Siddhraj
Unoloft
Kofeko
3nStar
Veda
Cerata
Shubham
Consultup IndiaSiddhrajUnoloftKofeko3nStarVedaCerataShubhamConsultup IndiaIn October 2025 Meta updated the WhatsApp Business Solution terms to prohibit AI providers from using the platform where an open-ended AI assistant is the primary thing being offered. The clause took effect on 15 January 2026, and ChatGPT, Copilot, and Perplexity all left the platform on that date.
Here's what got lost in the headlines: the restriction targets standalone assistants distributed through WhatsApp as a product. It does not touch a business automating its own customer conversations.
An open-domain chatbot that answers arbitrary questions, writes content, or acts as a general conversation companion, where that assistant is the product being delivered over WhatsApp. If someone offers you "ChatGPT on WhatsApp" as a service in 2026, they're selling you something Meta removed.
Automation that serves your own customers as part of a real business relationship: order confirmations and shipping updates, support triage and replies, appointment booking and reminders, lead qualification, authentication codes, and AI used to understand and route those conversations.
And the unofficial route was never allowed, either. Reverse-engineered libraries and browser automation that drive a personal WhatsApp account have always breached Meta's terms. They're cheaper right up until the number is permanently banned, and you can't appeal your way back to a number your customers have saved. We only build on the official Business API. If a cheaper quote you've received doesn't say which BSP it runs through, that's the question to ask.
The short version: if the AI is incidental to a genuine business service, you're fine. If the AI is the service, you're not. Everything on this page is the first kind.
Confirmations, dispatch notices, and tracking sent automatically from your store, with the customer able to reply in the same thread and reach a person if something's wrong.
Incoming questions classified on arrival. Order status answered from your own data. Returns and refunds handled against your policy. Complaints escalated to a human immediately, with the account history attached.
Recovery messages that respect opt-in and Meta's marketing category rules, sent through approved templates rather than the workarounds that get numbers restricted.
Enquiries from Click-to-WhatsApp ads, website widgets, and QR codes captured, qualified through a short structured conversation, and logged straight to your CRM with the transcript attached.
Slots offered, booked into your calendar, confirmed, and reminded, with rescheduling handled in the thread instead of over three phone calls.
Payment links, reminders, and receipts sent as utility messages, with status written back to your billing system.
Escalations, stock alerts, and approval requests pushed to the people who need them, in the app they already have open.
Every conversation logged against the right contact in HubSpot, Zoho, Salesforce, or your helpdesk, so WhatsApp stops being the one channel with no record.
Not sure which of these applies? Bring us a month of your WhatsApp history and we'll tell you which conversations are automatable, which shouldn't be, and roughly what each would cost to run.
WhatsApp is not an open channel you can broadcast on. Meta enforces these, and a build that ignores them gets rate-limited or banned rather than politely warned.
You need documented consent before messaging someone. It can be collected at checkout, on a form, via a QR code, or through a Click-to-WhatsApp ad, but it has to exist and it has to be recorded. We build the capture and the audit trail as part of the project, not as an afterthought.
When a customer messages you, a 24-hour window opens in which you can reply freely. Outside it, you can only reach them with a pre-approved template. This single rule shapes the entire design of a WhatsApp automation, and any vendor who hasn't mentioned it hasn't designed one.
Outbound messages use templates that Meta reviews. They fall into marketing, utility, and authentication categories, and the category drives both what's permitted and what it costs. Getting an order update classified as marketing rather than utility is an expensive mistake, repeated at volume.
Meta scores your number on how recipients react. Blocks and spam reports push the rating down, which caps how many people you can message per day. A campaign that annoys people doesn't just underperform, it reduces what you're allowed to do next month.
Sending at scale requires a verified Meta Business account, and your display name has to meet Meta's rules. The green verified badge is separate again, discretionary, and not something any vendor can promise you.
A number connected to the Business API can't also be used in the consumer WhatsApp Business app. Deciding which number to migrate, and what happens to the history on it, is a decision to make deliberately, before anyone starts building.
Two bills run alongside each other: what Meta charges to deliver messages, and what we charge to build and run the automation. Most vendors quote the second and stay quiet about the first, which is how a project comes in on budget and then costs three times what anyone expected to operate.
Since July 2025, billing is per message, not per conversation, and the rate depends on the recipient's country and the message category.
Promotions, broadcasts, cart recovery, win-backs. The most expensive category by a wide margin, and deliberately so. No volume discounts at any scale.
Order updates, shipping alerts, appointment reminders, payment confirmations. Far cheaper, with volume tiers that reduce the rate as you grow.
One-time passcodes and verification. Tightly formatted, cheap, and rule-bound.
Your free-form replies inside the 24-hour window. Free today. Not from October 2026.
Rates are set per country by the recipient's number, not your location, and Meta revises them roughly quarterly. Your Business Solution Provider adds a markup on top of Meta's rate. Current rates are published on Meta's own pricing page, which is where we check them rather than repeating figures here that would go stale.
Today
Free-form replies inside the window are free.
From 1 October 2026
Every reply inside the window is billed per message, at the utility-template rate for that country.
Meta announced on 1 July 2026 that from 1 October 2026, service messages become billable. Every free-form reply your business sends inside the 24-hour window, whether typed by a person or generated by a third-party automation, is charged at the same per-message rate as a utility template in that customer's country. There's no volume discount. Utility templates sent inside the window become chargeable too. Meta committed to publishing the country rates by 1 September 2026.
If your WhatsApp volume is mostly inbound questions rather than outbound campaigns, almost all of it has been free since November 2024. From October, almost none of it is. Clinics, property managers, and delivery businesses should be modelling this now.
Splitting an answer across four short messages used to be free and friendly. From October it costs four times what one message costs. Automation design changes accordingly.
Order and shipping updates belong in utility, not marketing. Misclassification is the most common and most expensive error we see.
One complete reply instead of three fragments. Post-October, message count is the bill.
Conversations started from a Click-to-WhatsApp ad or a Page CTA button open a 72-hour entry-point window with free delivery, which survives the October change.
Blocks and spam reports cost you rate limits as well as goodwill, and you still pay for a delivered message someone reports.
We model this with you before you commit. On the discovery call we take your realistic monthly volumes by category and destination country and produce a running-cost estimate alongside the build quote. If the numbers don't work, that's worth knowing in week one rather than month four.
We map the conversations you want to automate, check them against Meta's category and policy rules, and build the running-cost estimate. You get that model whether or not you hire us.
Business verification, choosing and migrating the number, and BSP setup. We handle the submissions; the review timeline belongs to Meta and we won't pretend otherwise.
Templates written, categorised correctly, and submitted for approval. Opt-in capture built into your checkout, forms, or ads, with the consent record stored properly.
The conversation flows, the routing logic, the escalation rules, and the connections to your store, CRM, and helpdesk. Tested against real scenarios in a sandbox before a customer ever sees it.
Live to a small segment first, watching quality rating, delivery, and how people actually reply. Problems at 200 recipients are cheap. The same problems at 20,000 cost you your messaging limits.
Delivery and read rates, quality rating, escalation rates, and spend per category tracked monthly. Templates revised as they underperform, and the cost model revisited when Meta changes its rates, which it does roughly quarterly.
A WhatsApp automation that can't see your order data is a chatbot with nothing to say. Everything we build is wired into what you already run.
No strong opinion on which BSP to use? We'll recommend one based on your volume, your destination countries, and your markup tolerance, and we'll tell you what each one adds on top of Meta's rate. You contract with them directly, not through us.
It's cheaper, it works, and then the number is banned with no appeal. Every contact who saved that number now has a dead line to your business. The saving is real until the day it isn't.
WhatsApp reaches people in a way email doesn't, which is exactly why misusing it is punished. Blocks and spam reports lower your quality rating and cut your daily messaging limit. The channel gets less useful the more you abuse it.
A polished automated reply to an angry customer is worse than a slow human one. We'll tell you which categories to leave alone, and we'd rather leave them alone than automate them badly.
A project quoted without a per-message model is a project whose real cost you'll discover in month three. This was survivable when service replies were free. From October it isn't.
Meta's message fees are separate and go directly to your BSP, based on your volumes and destination countries. See what it costs to run above for the categories, and we model your real numbers with you before you commit.
Our own pricing is fixed and quoted in writing before we start, no hourly billing. We'll walk you through it on the call.
Your customers already message you there, you're selling into markets where it's the default channel (the UAE, India, Latin America, much of MEA and Southeast Asia), and the conversations are transactional enough to survive Meta's rules.
Your customers are mostly US-based and reach you by email, your volume is low enough that per-message fees never justify the build, or what you actually want is broadcast marketing to a cold list, which is precisely what Meta's pricing is designed to discourage.
And sometimes the channel isn't the problem. If mail is piling up rather than messages, that's email and inbox automation. If the bottleneck is what happens after the conversation, that's workflow automation, and if what's needed is judgement calls the steps can't predict in advance, that's AI agent development. We'll say so on the call.
Honest answer: WhatsApp is a front door. It's only worth building if there's something useful behind it, your order data, your CRM, your booking system. A WhatsApp bot connected to nothing is a slower way to answer questions your website already answers.
See what the monthly plan actually covers, the monitoring and re-costing work that keeps quality rating and spend from drifting.
Book a 30-minute call. We'll map the conversations worth automating, check them against Meta's rules, and build you a running-cost model for your real volumes. If WhatsApp isn't the right channel for you, we'll tell you that instead.
