What the official WhatsApp Business API actually is
Meta’s WhatsApp Business Platform lets businesses send messages through Cloud API or a Meta-approved Business Solution Provider. You verify a business, register a phone number for API use, and work inside Meta’s messaging rules — templates outside the session window, free-form inside it.
Indian SMEs typically buy through a BSP that handles onboarding, template submission, and billing in INR. The BSP is not “unofficial”; it is a partner layer on top of Meta. Your ops team still owns opt-in proof and CRM field quality.
Quality rating and throughput matter more than “unlimited.” Spammy templates and high block rates throttle you even on the official path — discipline beats volume.
Cloud API vs BSP for Indian teams
Cloud API suits teams with engineering bandwidth and international cards; BSPs suit SMEs that want INR invoices, local support, and template help. Either way, the protocol is official — choose based on who maintains day two, not on who promises free blasts.
What “approved template” really means
A template is a pre-approved message shape with variables. Marketing and utility categories differ in approval friction and conversation pricing. Never invent a “template” by sending free-form text outside the window — that is how unofficial tools fake compliance.
How unofficial WhatsApp APIs usually work
Most unofficial products automate WhatsApp Web: a headless browser or local client stays logged in and types messages as if a human were clicking. Some wrap multi-device tricks or shared sessions. None of this is Meta’s Business Platform.
Sellers market “no template approval” and “broadcast to your entire Sheet.” That is exactly the behaviour Meta polices. When the session cookie dies or Meta detects automation, the number can be restricted or permanently banned.
There is also no clean webhook contract for delivery receipts and template analytics — your CRM ends up guessing whether the buyer saw the message.
Why “it worked for six months” is not a strategy
Many grey stacks run until a quality spike or a competitor reports spam. Surviving quietly is not proof of safety; it is delayed risk. Festival volume is when bans hurt most.
Ban risk, brand risk, and legal exposure in India
A banned WhatsApp number is not just an IT ticket. Buyers who saved that number stop receiving OTPs, booking confirmations, and support replies. Ad campaigns that promised “WhatsApp us” suddenly look broken.
Opt-in and consent records matter for marketing messages. Unofficial blasts often drip from purchased lists with no timestamped consent — hard to defend if a complaint lands.
Agencies that push unofficial APIs rarely put ban liability in writing. Ask who pays for number recovery and CRM rebuild before you sign.
- Primary business number on unofficial stack = single point of failure
- No Meta support path when Web automation is detected
- CRM history may not match what was actually sent
- Rebuilding trust after spam blocks takes longer than template approval ever did
Separate OTP/transactional from marketing early
Do not put OTPs and festival offers on the same fragile unofficial session. Official utility templates for transactional alerts, and carefully opted-in marketing templates for promos, keep failure modes isolated.
Feature reality: templates, windows, and media
Official API: templates, session messaging, media, interactive buttons (where enabled), delivery webhooks, and quality metrics. Unofficial: whatever the browser can pretend to click — until it cannot.
Interactive flows and catalog features that matter for commerce belong on the Business Platform. If your roadmap includes Shopify order updates, start official — see patterns around Shopify WhatsApp order automation.
Media size limits, rate limits, and category pricing are documented on Meta’s side. Unofficial docs are marketing PDFs that change when the seller rebrands.
Session window vs outbound template
Inside the customer-care window you can reply freely (still with policy sense). Outside it you need an approved template. Unofficial tools blur this line; Meta does not.
Multi-agent inbox needs
Sales teams in Chennai often need several agents on one brand number. Official BSP inboxes and CRM sidebars support assignment; a single Web session shared on a laptop does not scale safely.
CRM and automation glue: official only
The healthy pattern is CRM or form trigger → workflow tool → official BSP/Cloud send → write-back of message ID and template name. That is what we implement with Zapier, Make, or n8n.
Unofficial senders rarely give reliable message IDs. Support then cannot answer “what did we already promise on WhatsApp?” — the exact failure that creates angry tickets.
Compare channel choices with WhatsApp automation vs chatbot before you buy a bot that sits on a risky transport.
Logging fields every SME should keep
Store BSP message ID, template name, send timestamp, opt-in source, and CRM owner. Without those five, audits become guesswork after a complaint.
Cost comparison that includes failure modes
Unofficial monthly fees look low. Add: risk of full-number loss, emergency agency hours, paused ads, and re-onboarding a BSP under pressure. Official pricing is conversation-based and predictable once templates are approved.
Brevia floors: WhatsApp automation from ₹18,000 OTP for a scoped first workflow; Zapier glue from ₹15,000 OTP; n8n/Make from ₹18,000 OTP. We do not quote unofficial rebuilds. Full context: how much AI automation costs in India.
Cheapest compliant path is usually one utility template + CRM owner alert — not a 20-step nurture on day one.
Migration path off unofficial stacks
Freeze new broadcasts. Export contacts with consent notes if any exist. Register or reclaim a number on a BSP. Rebuild templates to match real use cases (booking, order update, lead reply). Reconnect CRM writes before turning marketing templates back on.
Run a parallel week: official for new leads, unofficial only for emergency support if you must — then cut unofficial entirely. Do not run both marketing blasts in parallel; buyers will get doubles.
Appointment and booking flows should land on official send from day one of migration — see how to automate appointment booking.
- Inventory every Sheet and Zap that calls the old sender
- Re-approve templates; do not assume copy-paste approval
- Train sales on the new inbox before go-live
- Kill shared QR logins for the old Web session
When to change the phone number
If the old number is already restricted or tied to spam reputation, migrating a fresh API number and updating website CTAs may be faster than fighting a dead reputation. Plan website and Google Business Profile updates in the same change window.
How to spot a risky vendor pitch
Red flags: “no Meta approval needed,” “broadcast 50,000 overnight,” “we use WhatsApp Web so it is free,” refusal to name the BSP, and contracts that ignore ban liability. Green flags: Meta partner language, template categories explained honestly, and CRM write-back demos.
Ask for a live send that shows a BSP dashboard message ID landing in your CRM. If they can only show a phone screen recording, walk away.
Hiring criteria for automation partners generally: how to hire an AI automation company in India.
Questions to put in writing
Who is the BSP? Who owns the WABA? What happens on ban? Where is opt-in stored? Can we export conversation metadata? Vague answers are answers.
Chatbots, humans, and the official channel
A chatbot can sit on WhatsApp only if the transport is official. Bot logic does not legalise an unofficial pipe. Prefer FAQ and qualification bots that hand off to humans with CRM context.
Many Indian service businesses need templates + human reply more than a full bot in month one. Sequence wisely: channel compliance first, conversation design second.
Where AI drafting fits safely
Draft replies inside the session window with human approval for high-ticket sales. Keep the send step on Business API. Hub: AI Automation.
How Brevia scopes WhatsApp work from Chennai
Bring current number status, CRM, monthly outbound volume, and whether any unofficial tool is live. We recommend BSP vs Cloud, template list, and workflow tool after that — not a tool logo first.
Deliverables for a first package: one production send path, CRM logging, kill switch, and a runbook. Phase-two nurture waits until quality rating is stable.
Start via consultation or contact. Service page: WhatsApp Automation in India.
What we will not build
WhatsApp Web scrapers, purchased-list blasts, or dual unofficial + official marketing sends. If that is the brief, we will decline and explain why — clearer than a silent ban later.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.