What a WhatsApp BSP actually gives you, how 360dialog, Twilio, and Gupshup price it, and when Meta's Business API is worth the setup versus a no-API alternative.
Every WhatsApp Business API setup runs on the same infrastructure: Meta’s Cloud API. Meta retired the old on-premise version in October 2025, so there’s no separate “enterprise” tier left to choose. What differs between 360dialog, Twilio, Gupshup, and the rest isn’t the messaging pipe, it’s the onboarding, dashboard, and template management layered on top of it, and how each one prices that layer. Here’s what a BSP (Business Solution Provider) actually gives you, what the main ones charge, and when you need one at all.
Meta calls the companies in this space “Solution Partners” and “Tech Providers.” A Solution Partner can onboard your business, manage billing, and extend messaging credit. A Tech Provider plugs you into the Cloud API more directly. Both get shortened to “BSP” in practice, and both sit on top of the same API Meta runs, not a separate one.
You don’t strictly need one. A business with in-house engineering can register directly with Meta through Business Manager and Embedded Signup, skipping the middleman fee but taking on template submissions, webhooks, and compliance itself. Most small and mid-sized businesses use a BSP for exactly that reason: someone else handles the plumbing.
Whichever BSP you choose, Meta’s own per-message charge sits underneath it, and that charge changed recently. Through June 2025, Meta billed per 24-hour “conversation” (a Marketing, Utility, Authentication, or Service bucket covering unlimited messages inside the window). Since July 1, 2025, Meta bills per individual template message instead, at rates that vary by category and destination country. A further change lands October 1, 2026: free-form service replies and in-window utility templates, both free today, start counting against a monthly allowance of 1,000 free service messages per phone number before charges apply.
We’ve covered the layered cost breakdown in more detail in WhatsApp Business API Pricing Explained. The short version: whatever a BSP quotes you, Meta’s rate is a separate line item on top, and it’s worth checking current numbers on Meta’s own pricing documentation before budgeting, since they’ve moved twice in 15 months.
360dialog charges a flat monthly platform fee per phone number (plans start around €50 to €60/month) and advertises no markup on Meta’s own rate. It’s built for businesses that already have, or plan to build, their own interface, since it’s a thin API layer rather than a bundled chat inbox.
Twilio charges no monthly platform fee at all, adding a small per-message markup on top of Meta’s rate instead. It’s an infrastructure play in the same vein: SDKs and a developer console, not a built-in agent inbox, so you build or buy a front end.
Gupshup also skips the monthly fee on its self-serve tier, adding a small flat fee per message, with volume discounts that improve noticeably past 100,000 messages a month, particularly for businesses in India and Southeast Asia.
Beyond these three, Infobip and Vonage serve the enterprise end with quote-based pricing rather than published self-serve rates, and Bird (formerly MessageBird) has moved from a pure API product toward a fuller marketing and pipeline suite on top of the same channel. Worth separating from all of these: WATI and AiSensy aren’t BSPs. They’re chat-inbox and chatbot-builder products that run on top of a BSP’s API access underneath, which is why their pricing pages look nothing like the ones above.
Every message sent outside a customer-initiated window still needs a Meta-approved template, no matter which BSP submits it. A dashboard can make resubmitting a rejected template faster to act on, but none of them approve templates themselves, that review sits with Meta. Rejections over wording or formatting are common enough that budgeting a few extra days into any campaign launch is the safer assumption.
A BSP earns its cost when you need what the Business API actually provides: reaching out first (order updates, reminders, re-engagement) rather than only replying, running several agents on one number without passing a phone around, or automating replies with a bot at a scale one person can’t handle. If none of that applies and what you actually need is to reply faster and keep track of leads inside conversations customers already started, the API’s per-message billing and template queue are solving a problem you don’t have.
That’s the gap The Chat Quotient is built for. It runs as a Chrome extension directly inside WhatsApp Web, so there’s no Business API application, no BSP relationship, and no per-message billing behind it. AI-drafted replies, chat summaries, and a CRM pipeline sit on top of the conversations you’re already having, for teams that need the reply-and-organize side of WhatsApp without the outbound infrastructure a BSP is priced for.
Is a BSP the same as the WhatsApp Business API? No. The API is Meta’s Cloud API, the same one for everyone. A BSP is a company that gives you access to it, with onboarding, a dashboard, and support layered on top, for a fee on top of Meta’s own rate.
Which BSP is cheapest? It depends on volume. 360dialog’s flat monthly fee suits predictable, moderate usage. Twilio and Gupshup’s per-message pricing with no platform fee can work out cheaper at low volume and more expensive at high volume, so run the numbers against your own expected message count.
Does The Chat Quotient replace a BSP? No. It’s a separate category, a no-API tool for replying inside conversations customers start, not a way to send Business API template messages. If you need to message customers first at scale, you still need the API and a BSP or a direct Meta connection behind it.
A BSP doesn’t sell you a different WhatsApp API. It sells you the onboarding and tooling around the one Meta already runs, priced as a flat platform fee (360dialog) or a per-message markup (Twilio, Gupshup). Meta’s own rate sits underneath all of it and is the part that’s actually changed, most recently the move off conversation-based billing in mid-2025. Before signing with any of them, check whether you need the API’s outbound capabilities at all. A lot of WhatsApp CRM problems get solved by a tool like The Chat Quotient without a BSP contract anywhere in the picture.
Install The Chat Quotient and turn that chat into a tracked lead, a faster reply, and — eventually — a closed deal. Free to start, right inside the WhatsApp Web you already use.
