WhatsApp Cloud API vs BSP: Which Route Should Indian SMBs Pick

Last month a client in Coimbatore called me in a panic. Her textile export business had built a decent WhatsApp automation flow through a vendor she found on Instagram, and one morning it just stopped. Messages weren't going out, the template approvals were stuck, and the vendor's "support" was a WhatsApp number that showed two grey ticks and never a blue one. She was paying ₹8,000 a month and had no idea whether the number even belonged to her or to the vendor.

This is the single most common mess I clean up when SMBs come to me about the WhatsApp Business API for SMBs. They picked an onboarding route without understanding what they were signing up for. There are essentially two doors: Meta's own Cloud API, which you can wire up directly, and a Business Solution Provider (BSP) who sits between you and Meta. Both work. Both are legitimate. But choosing wrong costs you money, control, or sanity, and sometimes all three.

Here's a number that surprises most owners: Meta charges nothing for the Cloud API hosting itself. The famous per-conversation fees still apply, but the software layer that vendors sometimes bundle at ₹5,000–₹15,000 a month? That's their markup, not Meta's floor. In this post I'll break down cost, setup time, compliance, and support for both routes, show you a real migration I did for a Pune business, and give you a checklist so you brief your vendor like someone who knows the game.

Key Takeaways

• Meta's Cloud API is free to host; you only pay per-conversation charges. A BSP adds a platform fee on top, typically ₹2,000–₹20,000/month depending on features.
• Go direct with Cloud API if you have a developer or technical partner and mostly need transactional notifications. Go with a BSP if you need a no-code dashboard, team inbox, or campaign tools yesterday.
• Always insist the WhatsApp Business Account (WABA) sits under your Meta Business Manager, not the vendor's. This is the number one lock-in trap.
• From July 2025, Meta shifted to per-message pricing for marketing/utility categories in India. Budget on message volume, not just conversations.
• DPDP Act 2023 compliance for consent and data handling is your responsibility regardless of route. A good BSP helps; a cheap one leaves you exposed.
• Setup with a BSP takes 1–3 days. Direct Cloud API takes 1–2 weeks including verification, unless you have prior Meta Business verification done.

What actually is the difference between Cloud API and a BSP?

Let me strip out the jargon. The WhatsApp Cloud API is Meta's own hosted version of the messaging API. You connect to Meta's servers directly, generate access tokens, register your phone number, and start sending. No middleman. You need someone who can call REST endpoints and manage webhooks, which means a developer or a technical vendor.

A Business Solution Provider (BSP) is a Meta-approved company that has built a layer on top of the API. Think Gupshup, Wati, Interakt, AiSensy, Kaleyra, or Zoko. They give you a login, a dashboard, a template manager, a shared team inbox, chatbot builders, and often analytics. You never touch code. You pay them for that convenience plus the underlying Meta charges.

The crucial thing most owners miss: both routes use the same underlying WhatsApp infrastructure. The message delivery, the blue ticks, the delivery reliability, all identical. What differs is who manages the plumbing and how much hand-holding you get. If you already work with a technical partner for your custom software development, direct Cloud API often makes more sense than most vendors will admit.

A quick analogy that helps owners decide

Direct Cloud API is like leasing a commercial shop and doing your own fit-out. Cheaper long-term, full control, but you need to know electricians and contractors. A BSP is a managed co-working space: you walk in, desk is ready, someone fixes the AC. You pay more per month but you're running from day one.

How much does each route actually cost in rupees?

This is where vendors get slippery, so let me be concrete. As of Meta's 2025 pricing shift in India, WhatsApp moved from conversation-based to per-message pricing for marketing and utility categories. Rough indicative rates (these change, always verify):

• Marketing messages: around ₹0.78–₹0.88 each
• Utility messages: around ₹0.11–₹0.16 each (and free within a 24-hour service window in many cases)
• Authentication (OTP) messages: around ₹0.11–₹0.14 each
• Service/user-initiated conversations: free within the 24-hour customer service window

These per-message costs are the same whether you go direct or via a BSP. Meta bills them either way. The difference is the platform fee layered on top.

Criteria	Direct Cloud API	Entry BSP (e.g. Interakt/AiSensy)	Enterprise BSP (e.g. Gupshup/Kaleyra)
Platform fee/month	₹0 (hosting free)	₹1,500–₹5,000	₹15,000–₹50,000+
Per-message charges	Meta rates (billed direct)	Meta rates + small markup sometimes	Meta rates, often at volume discount
Setup time	1–2 weeks (self/dev)	1–3 days	1–2 weeks (assisted)
No-code dashboard	No (build your own)	Yes	Yes, advanced
Team inbox	No	Yes, limited agents	Yes, unlimited/CRM-grade
Best for	Devs, transactional flows	Small marketing teams	High-volume, contact centres

So if you send 10,000 utility messages a month, your Meta cost is roughly ₹1,100–₹1,600 regardless of route. On direct Cloud API that's basically your whole bill. On an entry BSP add ₹1,500–₹5,000 for the dashboard. On enterprise, add a lot more, but you get the tooling to justify it.

How do you set up WhatsApp Business API directly with Meta?

If you or your tech partner can handle a few API calls, here's the actual sequence. This isn't theory, it's the checklist I hand to development teams.

1. Create a Meta Business Manager account at business.facebook.com if you don't already have one. Use a company email, not a personal one.
2. Complete Meta Business Verification. You'll upload GST certificate, company PAN, or a utility bill matching your registered address. This is the step that trips people up. If your registered address is shaky, sort it out first. Some SMBs use a proper virtual office address for GST and company registration to keep verification clean.
3. Set up the WhatsApp Business Account (WABA) inside the App Dashboard, add your product, and get your temporary access token.
4. Register a phone number that is not already active on the consumer WhatsApp or WhatsApp Business app. You'll verify it via SMS or call OTP.
5. Generate a permanent System User token so your integration doesn't break every 24 hours. This is easy to miss and causes the "it worked yesterday" outages.
6. Configure your webhook to receive incoming messages and delivery status. You need an HTTPS endpoint. This is where a developer earns their fee.
7. Submit message templates for approval. Marketing and utility templates get reviewed by Meta, usually within minutes to a few hours.
8. Complete display name approval and set your business profile. Then start sending in test mode before going live.

Common Mistake: Registering your main business number that's already on regular WhatsApp. Once a number goes onto the API, it leaves the consumer app permanently, and migration back is painful. Use a fresh number, or a dedicated line for your API traffic. I've seen a Jaipur handicrafts seller lose two years of chat history because nobody warned them.

If any of steps 4–7 make your eyes glaze over, that's your signal to use a BSP or bring in an IT consulting partner to handle onboarding. There's no shame in it. The API is genuinely fiddly.

When should an Indian SMB pick a BSP instead?

Go with a BSP if you tick most of these boxes:

• You have no developer and don't want to hire one.
• Your team needs a shared inbox where three or four agents handle customer chats.
• You run marketing campaigns and want drag-and-drop broadcast tools with opt-out management.
• You want a chatbot builder without writing code.
• You need it live this week, not next fortnight.

Most Indian retail, D2C, coaching, clinic, and services businesses fall here. The ₹2,000–₹5,000 monthly fee buys back dozens of hours. Just remember the recent policy tightening: Meta now restricts general-purpose AI chatbots on the platform. If your BSP is pushing a generic GPT bot, read our breakdown on why WhatsApp bans general AI chatbots and how to fix your bot before it breaks before you commit.

What to demand from any BSP before you sign

• Confirm the WABA will be created under your Business Manager, and you get admin access.
• Ask whether they mark up per-message rates or bill Meta's rates at cost.
• Get the messaging tier and daily limit in writing. New numbers start at 1,000 business-initiated conversations/day and scale up. Our guide on WhatsApp bulk messaging limits, tiers, and warm-up for 2026 explains how to grow this safely.
• Check DPDP compliance: where is chat data stored, and can they export and delete on request?
• Confirm support SLA. "WhatsApp us anytime" is not an SLA.

A real migration: how a Pune D2C brand cut its bill and kept control

A 12-person home fragrance brand in Pune came to me spending ₹14,500/month on an enterprise-tier BSP they'd been oversold. They sent maybe 6,000 messages a month, mostly order confirmations and shipping updates, plus one weekly promo blast. They were using less than 10% of what they paid for. Worse, their WABA sat under the BSP's Business Manager, so they couldn't leave without losing their verified number.

Here's what we did over two weeks:

1. Reclaimed the WABA. We requested a Business Manager ownership transfer. The BSP dragged their feet, so we escalated through Meta's partner request flow. Took nine days but it worked.
2. Moved to an entry-tier BSP at ₹2,500/month that offered exactly the team inbox and broadcast tools they used. No enterprise chatbot they'd never touched.
3. Wired their Shopify order events directly to utility templates, so shipping updates fire automatically. We reused an existing integration our custom software team had built.
4. Restructured messages by category. Order and shipping updates went to the cheaper utility category. Only the genuine weekly promo went out as marketing.

Result: their all-in monthly cost dropped from ₹14,500 to roughly ₹4,100, including Meta message charges. That's ₹1.25 lakh saved a year, and crucially they now own their number outright. The lesson isn't "BSPs are bad." It's "match the tier to your actual usage and never let anyone else hold your WABA."

What are the compliance obligations you can't ignore?

Regardless of route, three compliance realities apply to Indian SMBs.

Opt-in consent. Meta requires you to have explicit opt-in before messaging anyone. A checkbox on your website, a keyword reply, or a signed form all count. Buying a contact list and blasting it will get your number blocked fast, and it violates both Meta policy and the spirit of India's DPDP Act 2023.

DPDP Act 2023. This governs how you collect, store, and process personal data including phone numbers and chat content. You need a clear purpose for collection, the ability to honour deletion requests, and reasonable security. If you go direct, this sits entirely on you. A good BSP shares the load but never removes your accountability.

Template category discipline. Sending a promotional message dressed up as a utility template is a policy violation. Meta's systems catch mismatches, and repeated flags hurt your quality rating and can restrict your account.

Pro Tip: Keep a simple consent log with a timestamp and source for every contact you message. When Meta or a customer questions it, you produce the record in seconds. I've watched accounts survive a quality review purely because the owner could show clean opt-in data. This one habit is worth more than any fancy dashboard.

If you're also running payment collection over chat, the compliance surface widens. Our guide on WhatsApp payments for SMBs covers the RBI and settlement side.

Which route wins for support and reliability?

Here's the uncomfortable truth: Meta's direct support for Cloud API is thin. You get documentation, community forums, and a business support inbox that responds slowly. If your integration breaks at 9 PM before a Diwali sale, nobody at Meta is picking up. Your safety net is your own developer or technical partner.

A reputable BSP, by contrast, gives you a human. The good ones have India-based support who understand template rejections, tier limits, and quality ratings. That's worth real money when you're not technical. But the market is full of thinly staffed resellers whose "support" is one overworked person. Vet hard.

My rule of thumb: if messaging is mission-critical to your revenue and you have no in-house tech, pay for a BSP with a genuine SLA, or partner with someone like eDarpan who manages the WhatsApp Business API onboarding and keeps it running. If you have a capable dev team and mostly transactional needs, direct Cloud API plus your own monitoring is leaner and cheaper.

How does WhatsApp fit with your other messaging channels?

Don't treat WhatsApp as an island. Most SMBs I work with run it alongside SMS for OTPs and fallback, and increasingly voice for support overflow. WhatsApp delivery isn't guaranteed instant; SMS still matters for time-critical OTPs in low-connectivity areas. Pairing your WhatsApp flow with reliable bulk SMS services gives you a proper fallback.

For businesses fielding a lot of repetitive calls, an AI voicebot can catch overflow while WhatsApp handles the async conversations. And if you're thinking about layering intelligence into your WhatsApp itself, read our setup guide for Meta's Business AI on WhatsApp to stay within current policy.

Frequently asked questions

Is WhatsApp Cloud API free to use?

The Cloud API hosting is free from Meta. You still pay per-message or per-conversation charges based on category, and if you use a BSP you pay their platform fee on top. So "free" applies only to the software layer, not the messaging volume.

Can I use my personal WhatsApp number for the Business API?

No. A number moved to the API leaves the consumer WhatsApp and WhatsApp Business apps permanently, and chat history doesn't transfer. Always use a fresh, dedicated number for your API traffic to avoid losing anything.

How long does WhatsApp Business API approval take in India?

With a BSP, you can often go live in 1–3 days if your Meta Business verification is already done. Direct Cloud API setup including verification typically takes 1–2 weeks. Template approvals themselves are usually minutes to a few hours.

Do I own my WhatsApp number if I use a BSP?

Only if the WABA is created under your own Meta Business Manager. Insist on this in writing before signing. If the vendor holds it under their account, switching providers or leaving becomes very difficult.

What happens if I send messages without opt-in?

Your quality rating drops, users report you as spam, and Meta can restrict or block your number. It also risks non-compliance with India's DPDP Act 2023. Always collect explicit opt-in and keep a timestamped consent log.

Which is cheaper for a small business, direct API or BSP?

Direct Cloud API is cheaper on paper since there's no platform fee, but it needs technical skill to set up and maintain. For most non-technical SMBs, an entry-tier BSP at ₹2,000–₹5,000/month is cheaper overall once you count the developer time you'd otherwise spend.

Can I switch from a BSP to direct API later?

Yes, provided your WABA sits under your own Business Manager. You'd migrate the phone number and rebuild your integration or move to another provider. This is exactly why owning your WABA from day one matters so much.

So which route should you pick?

If you're a technical team or already have a development partner and your needs are mostly transactional notifications, go direct with Cloud API. You'll pay less and control more. If you're a busy owner who needs a working dashboard, a team inbox, and campaign tools without touching code, pick a reputable BSP with a real SLA and, above all, insist your WABA lives under your own Business Manager. Getting the WhatsApp Business API for SMBs right is less about the tool and more about ownership, compliance, and matching the tier to your actual message volume.

At eDarpan we handle both paths. We onboard businesses directly on Cloud API when that's the smart call, and we set up and manage BSP integrations when a dashboard makes more sense, always keeping the account in your name. If you want a straight answer for your specific situation, look at our WhatsApp Business API services, browse our full services overview, or just get in touch and tell us your message volume. We'll tell you honestly which door to walk through.

Image credit: Market by Mike Knell via flickr (BY-SA 2.0), sourced through Openverse.