Brands launch WhatsApp the way they launched email in 2003, broadcast-first, permission-second, recipient-last. The channel forgives nothing. A noisy launch can burn your sender reputation in one campaign, tank your Meta Business Account standing, and train your best customers to mute you permanently.
The engagement numbers are seductive. Ninety-eight percent read rates. Response rates north of 30% on well-constructed flows. Conversion rates that make email look slow. But those numbers belong to programmes built with discipline, not to the channel itself. The channel will punish you just as fast as it rewards you.
What follows is the framework we use for every WhatsApp launch. It costs you 30 days and requires restraint at every step. The brands that follow it have opt-out rates below 2% at six months. The brands that don't usually come to us after a noisy start trying to fix the damage.
Choosing your BSP
The WhatsApp Business API isn't accessed directly. You need a Business Solution Provider, a Meta-approved intermediary who manages your connection to WhatsApp's servers. Your choice of BSP affects your message costs, your template approval speed, your analytics depth, and your ability to do conversational (two-way) flows.
Established BSPs with full-featured APIs: Twilio, MessageBird, 360dialog, Vonage. Newer players with better UI but less API flexibility: Zoko, Respond.io, Wati. For brands running everything through an existing CRM, check whether your CRM vendor has a native BSP integration, Salesforce, HubSpot, and Braze all have one. Using a native integration saves a data-sync layer, which matters at scale.
Don't choose a BSP based on price per message alone. The real cost is in failed template approvals, slow escalation support, and brittle API documentation. Pay for a vendor with a track record. The per-message savings rarely cover the cost of a delayed launch.
The permission stack
Permission is not a tick-box on a privacy policy. It's a value exchange made visible. The recipient needs to know what they're signing up for, when they'll hear from you, and what it will be worth to them.
Our rule: opt-in collected only at checkout or at a named subscribe moment, with a single-line value statement. Never inferred from a previous email opt-in. Never pre-ticked. Never bundled into a general "marketing communications" clause. If you can't summarise what you'll send in one sentence, your opt-in proposition isn't ready.
Two-touch maximum per week, per recipient. No exceptions in the first 90 days. No promotional sends until you've run at least three transactional or content messages and your opt-out rate on those is below 0.5%. You earn broadcast rights. You don't start with them.
Template economics
Meta requires pre-approved message templates for any outbound promotional send on the WhatsApp Business API. This is a feature, not a limitation. Template approval forces you to write your message before you have the urgency of a campaign deadline. That tends to produce better copy.
Keep templates short. The medium is a messaging app, 180 characters is enough for a promotional hook. Link to a landing page for everything else. Variable fields (first name, order number, product) should be in the template, not added by concatenation. Meta will reject templates that use variables to build sentences from scratch rather than personalise a pre-written one.
Plan your template library before launch: one transactional template (order confirmation), one post-purchase content template (usage tip, how-to, or review request), one promotional template (offer or event). Submit all three in the first week so approval delays don't hold up your ramp.
The kill switch
Set an opt-out threshold before launch. We use 3% as the absolute ceiling and 1.5% as the warning level. Watch it daily for the first 30 days, not weekly, daily. WhatsApp reputation is faster-moving than email.
If you hit the warning level on a single send, pause and review that message specifically before sending anything else to that cohort. If you hit the ceiling, stop all broadcast sends and audit the full programme: template copy, frequency, send timing, and whether the opt-in proposition was honest about what you'd send.
The brands that build durable WhatsApp programmes treat opt-out rate as a credit score. It's hard to build, easy to damage, and very slow to recover.
Reading the signals before they become exits
WhatsApp gives you three early-warning signals that precede opt-outs: delivery failures on accounts you know are valid (often means the recipient has proactively blocked your number), template rejection rates increasing (Meta's quality scoring is dropping), and reply rates falling sharply on content that previously prompted replies.
Any one of these in isolation is worth monitoring. Two happening together is a signal to pause and assess. All three at the same time means something structural has changed, either your audience has fundamentally shifted, or a recent message caused enough quiet rejection to suppress the whole relationship.
Build an alert on each of these three signals from day one. The brands that catch problems at warning level rather than ceiling level save months of reputation repair work.
The 90-day ramp
Month one: transactional only. Order confirmations, delivery updates, appointment reminders. These messages are expected, time-relevant, and valuable. They establish your sender identity in the recipient's mind before you ask for anything.
Month two: add one content message per fortnight. Not promotional, a tip, a how-to, an insight relevant to the product they bought. Measure reply rate. If replies are low, the content isn't landing. Adjust before adding frequency.
Month three: first promotional send to the cohort with the cleanest engagement signals from months one and two. One message. One clear offer. One link. Measure opt-out rate within 24 hours.
If you've followed this sequence, your opt-out rate on that first promotional send will be under 1%. You've earned the channel. Now you can build.