WhatsApp Business API for Sales: Setup, Rules, Reply Rates
Last verified: 2026-09-15A practical account of what Meta actually requires, what it actually costs, and which of the reply-rate numbers in every other guide you can safely ignore.
You have decided WhatsApp is where your buyers actually reply. Then you open the documentation and hit a wall of Business Manager verification, template categories, quality ratings and a pricing page that points at a rate card it does not contain. Most guides to a WhatsApp Business API sales setup skip straight past this to a screenshot of a chatbot, which is how teams end up three weeks in with an approved number they are not allowed to use the way they planned.
This is the version with the constraints left in. What you need before you start, what Meta's rules let you send, what it costs per message, and what the reply-rate evidence actually supports.
What a WhatsApp Business API sales setup really involves
There is no application form that a salesperson fills in alone. The API is gated behind Meta's business infrastructure, and each gate has a queue.
| Step | What it means | Where teams stall |
|---|---|---|
| Meta Business Portfolio | A verified business entity, not a personal account | Business verification needs incorporation documents and a matching public web presence |
| Access route | Meta's Cloud API directly, or a Business Solution Provider that wraps it | Direct means you build the inbox, the queueing and the retries yourself |
| A dedicated number | A phone number not currently active on the consumer WhatsApp or WhatsApp Business app | Migrating a number your team already uses wipes its existing chat history |
| Display name | Reviewed by Meta against your verified business name | Rejections for names that read as a campaign rather than a company |
| Message templates | Every message you start must be pre-approved and categorised | Approval is per template, so each new play is a new review |
Budget a week or two of calendar time, most of it waiting. The build is not the hard part.
The rules that decide what you can send
Three of Meta's rules do more to shape an outbound motion than any feature comparison.
You need opt-in, and you have to say who you are. Meta's requirement is that the person gave you their phone number and gave permission to receive messages. The opt-in does not have to be collected inside WhatsApp, and it does not have to be WhatsApp-specific, but it must "clearly state that a person is opting in to receive communication from the business" and "clearly state the business's name." Meta also pushes compliance with local law back onto you, which is where GDPR, TCPA and regional consent regimes enter the picture. A scraped list is not an opt-in under any reading of that sentence.
Outside a live conversation, you can only send an approved template. When someone messages you, a 24-hour customer service window opens and you can reply freely with anything. Once it closes, the next thing you send has to be a template, in one of four categories: marketing, utility, authentication, or service.
Your sending volume is rationed by quality. New numbers start at 250 unique customers per 24 hours. The first step up is 2,000, and Meta gates it on message quality — you either verify your business identity or deliver 2,000 messages cleanly. Above that, increases are automatic when you are sending high-quality messages and using at least 50% of your current limit over the previous seven days, with the increase landing within six hours.
Read those together and the conclusion is uncomfortable but useful: WhatsApp's platform is engineered for messaging people who asked to hear from you. It is not a cold channel with better deliverability. Teams who treat it as one collect blocks, watch their quality rating fall, and lose the number. The same pattern that killed cold email reply rates plays out faster here, because the recipient's complaint mechanism is one tap and it feeds straight back into your sending limit.
What it costs
Meta moved from per-conversation to per-message billing on 1 July 2025, and charges on delivery rather than on send. Four things matter for a budget:
- Service messages are free for all businesses, and have been since 1 November 2024.
- Non-template messages inside an open customer service window are free. So is a utility template delivered in that window.
- There is a 72-hour free entry point. If someone reaches you through a click-to-WhatsApp ad or a Page call-to-action, everything you send them for the next 72 hours is free.
- Marketing templates are always charged. There is no free allowance.
Rates vary by market and category, and Meta changes them on a quarterly cadence — the current rate card took effect 1 April 2026, following changes on 1 January 2026, 1 October 2025 and 1 July 2025. Utility and authentication rates drop as monthly volume rises.
Here is the part no other guide will tell you: the country rates quoted across third-party blogs do not agree with each other. For UAE marketing templates this session, one vendor page quoted $0.0385 and another $0.0816 — a 2x spread, and the cheaper one described it as a per-conversation rate, a model Meta retired over a year ago. Do not budget from a blog. Pull your own markets off Meta's rate card and check the effective date on it.
The arithmetic that actually matters is cost per conversation started, not cost per message:
| Line | Example | Your number |
|---|---|---|
| Marketing template rate (your market) | $0.05 | |
| Provider per-message markup | $0.005 | |
| Provider platform fee, monthly | $49 | |
| First-touch messages per month | 2,000 | |
| Messaging spend | $110 | |
| Total monthly | $159 | |
| Replies at a 10% reply rate | 200 | |
| Cost per reply | $0.80 |
The example rate and markup above are illustrative placeholders, not quoted prices — provider fees in the $0–$299/month range with roughly half-cent per-message markups are common, but replace every row with your own numbers before you present this to anyone. Even at three times this cost, the channel is cheap next to the real cost of an SDR. Channel cost has never been the constraint in outbound. Permission and relevance are.
Reply rates: what the evidence supports
Almost every WhatsApp guide opens with a 98% open rate. That number has no study behind it. It traces back to marketing copy from a single vendor, MessengerPeople, now Sinch Engage, with no published methodology, sample size or measurement window. It has been quoted so many times that it now looks like consensus.
It is also not comparable to the email number it gets set against. A WhatsApp read receipt fires when a human opens the thread. An email open fires when a tracking pixel loads, which Apple Mail Privacy Protection does automatically. One measures attention, the other measures a network request.
The figures worth using come with methodology attached:
| Source | Sample | Finding |
|---|---|---|
| SendPulse broadcast benchmarks | 355 SMB accounts, 8.4M broadcast messages, Nov 2025 to Apr 2026 | Median read rate 63% per account, 66% pooled. Reply rates not reported — not tracked consistently across channels |
| Chatarmin KPI study | 30+ e-commerce brands | 45–55% reply rate and under 0.5% opt-out on segmented, opted-in lists |
Note what the better-sourced dataset says: 63%, not 98%, and it declines to publish a reply rate at all because the measurement is not consistent. The 45–55% reply figure comes from a much smaller e-commerce sample messaging people who subscribed, which is a different activity from B2B prospecting. Treat it as an upper bound for warm, permissioned lists and nothing more.
For cold B2B, published figures cluster in the low single digits, but every one I could find this session was unattributed vendor data with no methodology. So the honest answer is that nobody has published a credible cold WhatsApp B2B reply benchmark. Run 200 messages, measure your own, and distrust anyone quoting a number to one decimal place.
Three metrics are worth instrumenting from day one: read rate segmented by list quality, replies per 100 first touches, and cost per qualified conversation. The third is the only one that survives contact with a CFO.
Where this leaves a small sales team
WhatsApp works for sales when there is already a reason for the person to hear from you: an inbound enquiry, an event badge scan, a form fill, a referral, a lapsed customer. In MENA, South Asia and much of LatAm it is the default business channel, and a reply there arrives in minutes rather than days. It does not work as a cold-list channel, and Meta has built the quality machinery to make sure of that.
The practical shape is usually multi-channel: email or LinkedIn earns the first permission, WhatsApp carries the conversation once it exists. That is also where the compliance work lives — consent capture, honouring opt-outs, and keeping a record of both. Our outbound compliance handbook covers that ground, and this is informational rather than legal advice.
BOSRAI sits in that gap deliberately. It sources leads, drafts the outreach and runs follow-up across email, LinkedIn and WhatsApp, with a human approving messages before they go out — which matters more on WhatsApp than anywhere else, because a bad send costs you sending capacity, not just a reply. Plans run Free, Starter at $79.99, Growth at $199, Scale at $499 and Pro at $999, discounted annually. We have no published case studies or customer benchmarks to point at yet, so hold the channel maths above to the same standard you would hold any vendor's: replace our example numbers with yours, and check Meta's rate card yourself.
Sources
- Pricing on the WhatsApp Business Platform — Meta for Developers — per-message billing from 1 July 2025, free service messages from 1 November 2024, 72-hour free entry point, rate-card change dates including 1 April 2026.
- Get opt-in for WhatsApp — Meta for Developers — the opt-in requirement and the two mandatory disclosures.
- Messaging Limits — Meta for Developers — the 250 and 2,000 unique-customer tiers, the 50%-utilisation automatic scaling rule and the six-hour increase.
- SendPulse broadcast benchmarks — 63% median and 66% pooled WhatsApp read rates across 355 SMB accounts and 8.4M messages, November 2025 to April 2026.
- Skolbot: WhatsApp's 98% open rate is a myth — traces the 98% figure to MessengerPeople, now Sinch Engage, and explains why read receipts and email pixel opens are not comparable.
- Chatarmin WhatsApp KPI benchmarks — 45–55% reply rate and sub-0.5% opt-out from a study of 30+ e-commerce brands.
- Setsmart: WhatsApp Business API per-message rates — UAE marketing quoted at $0.0816 and typical provider platform fees of $0–$299/month with about $0.005 per-message markups.
- Ominiflow: UAE WhatsApp API pricing — the conflicting UAE marketing figure of $0.0385, described as a per-conversation rate.