Compliant WhatsApp Outreach: How to Vet a Vendor

If your sales team's WhatsApp number has ever been restricted two days into a campaign, you know how costly the lesson is. The problem is rarely the message — it's the plumbing underneath it. Founders, ops leads and CTOs at Indian B2B firms are now pitched by a dozen "WhatsApp automation" vendors who look identical on a slide deck, and the difference between a compliant setup and one that gets your number banned only shows up after you have paid.

What does compliant WhatsApp outreach actually mean?

Compliant outreach means three things held together: a verified WhatsApp Business Account on Meta's official Cloud API (directly or through an approved BSP), documented opt-in for every number you message, and template copy Meta approved before it went out.

Anything else is a shortcut with a fuse. Tools that drive WhatsApp Web or reverse-engineered clients look cheap because they are — Meta actively detects them, and the penalty lands on your number, not the vendor's. On consent, the DPDP Act 2023 expects a recorded lawful basis, a notice, and a working way to withdraw, per contact. A vendor who says "DPDP doesn't apply to B2B" has just told you something useful about how they will behave when a customer complains.

Why should you interrogate the pricing model first?

Because WhatsApp quotes are rarely comparable — most vendors fold Meta's pass-through fee, platform charges and per-seat pricing into one per-message rate that hides what you are actually buying.

Ask for the quote split into three lines: Meta's template fee at cost, the platform fee (flat, per message, or per seat), and setup. Then run your own numbers. Say you plan 15,000 marketing template sends a month and Meta's India marketing rate is around ₹0.80 per template at the time of writing — that is roughly ₹12,000 of pass-through cost. A vendor quoting ₹2.00 all-in is billing you ₹30,000, so about ₹18,000 of it is platform fee. That can be perfectly fair, but you should see the figure before you sign for twelve months. Utility templates cost a fraction of marketing ones, so any blended rate flatters whichever mix the vendor assumes. If you want to see what that level of itemisation looks like, the pricing page breaks a quote down the same way.

What should you ask about opt-in and consent records?

Ask the vendor to show you, inside the product, where an individual's opt-in lives — with a timestamp, the source (landing page, enquiry form, event badge scan) and the exact wording they agreed to.

That record has to be exportable, because it is your defence, not the vendor's, if a complaint reaches Meta or someone exercises rights under the DPDP Act. Then test the exit path: is a STOP or withdrawal processed immediately across every campaign, or does the contact sit in a suppression list that a new campaign can quietly override? Finally, confirm in writing whether the WABA and the phone number are registered in your name. If you leave, the number, template history and quality rating should leave with you.

How do you check the plumbing before signing?

Insist on a paid pilot on your own number, with your own templates and a stated success metric — two to four weeks is usually enough to see the truth.

Get these answered in writing before the pilot starts:

• Is the WABA verified on the official Cloud API, and which BSP sits underneath it?
• What is the current messaging limit on the number, and how does it get raised?
• Is this a dedicated number, or a pool shared with other clients?
• What is the quality rating today, and what happens to our account if it falls to red?
• Which template categories are we approved for, and who writes and submits them?
• What does the bill look like at 10,000, 50,000 and 100,000 sends a month?
• On exit, do we keep the number, the template library and the contact history?

A vendor who hesitates on the third and fourth questions is either sharing infrastructure or has not looked at it lately. Both answers matter.

What does a well-run first campaign look like?

A compliant first campaign is small, traceable and slightly boring: a narrow list, one approved template, one measurable next step.

Start with 300-500 contacts who have a real reason to hear from you — existing customers, webinar attendees, inbound form fills — not a purchased list. Review three numbers weekly: delivery rate, reply rate, and block or report rate. Block rate is the one to watch; a spike is Meta's early warning, and it will pause templates long before it restricts the number. In our experience a warm B2B list in India can reply at 25-40% when the first message is short, names a specific context and makes it easy to say no. Treat confident promises about cold, scraped lists as a warning sign rather than a benchmark. If you want to see how one of these rollouts is scoped and measured end to end, the case studies are a reasonable reference.

Where to start

Before you take another vendor call, write down three things: your monthly send volume by template category, the sources your contacts came from, and who owns the WABA. Those answers turn a vague "we need WhatsApp outreach" brief into a set of questions a vendor cannot dodge. If you would rather have someone scope the compliance and integration work alongside you, Maysan Labs does exactly this, usually alongside the email and CRM systems it already runs for Indian B2B teams.