What is a WhatsApp BSP (Business Solution Provider)?

Updated 2026-09-19 · 4 min read · By the Convo360 team

The core definition

A Business Solution Provider, or BSP, is a company that Meta has formally authorised to give other businesses access to the WhatsApp Business API. Historically, this was the only route to API access: a business couldn't connect directly to Meta and had to go through an approved BSP for onboarding, message routing and billing.

A BSP sits between the business and Meta's infrastructure: technically, it is the entity whose servers actually talk to Meta's WhatsApp platform, while the business (and often a chatbot platform on top) uses the BSP's connection to send and receive messages.

Why BSPs existed in the first place

In WhatsApp's earlier API era, the technical setup was involved enough (self-hosted servers, manual approval steps, direct integration work) that Meta relied on a network of specialised partners to handle onboarding, template submission and billing relationships on businesses' behalf. This model still exists and works well for large enterprises that want a dedicated account relationship, a support layer and sometimes custom volume pricing.

For a mid-size or smaller Indian business, though, going through a traditional BSP often meant a slower onboarding process, minimum commitments, and a support relationship built for large accounts rather than a business that just wants a working WhatsApp chatbot.

The mechanics of a BSP relationship generally involve three things: technical connectivity to Meta's servers, template submission and review handling, and a billing arrangement for per-message charges. A business signing with a BSP was, in effect, outsourcing all three at once, which made sense when there was no self-serve alternative but adds a layer of dependency that isn't always necessary today.

Direct Cloud API access changed the picture

Meta's Cloud API and embedded signup now let a business connect its number to a software platform directly, without a separate BSP contract in the traditional sense. See Meta's own explanation at developers.facebook.com. This is faster to set up and gives the business a more direct relationship with its own WhatsApp Business Account, though platforms still handle the technical connection under the hood, and in effect, many chatbot platforms today act as a lightweight BSP-like connector without the older enterprise sales process attached.

Credit lines, billing, and BSP vs direct-connect compared

Some BSP relationships include a shared credit line for message billing, where the BSP fronts costs and bills the business, useful for larger enterprises managing high message volumes without a direct Meta billing relationship. Smaller and mid-size businesses more commonly pay Meta's per-message charges directly through their own billing setup connected during embedded signup — which also means no separate BSP invoice to reconcile every month, just Meta's own charges alongside your platform subscription.

Common misunderstandings

The biggest misunderstanding is assuming 'BSP' is a stamp of trustworthiness that any vendor can claim. It's a specific Meta authorisation, not a marketing phrase — a platform connecting via embedded signup without being a formal BSP itself is not automatically less reliable, since the underlying Cloud API connection is the same either way.

A second misunderstanding is assuming a BSP or platform automatically owns your WhatsApp number once you sign up through them. It shouldn't — a correctly configured WABA is created under your own Meta Business Manager regardless of which BSP or platform helped connect it, and it's worth checking this explicitly during onboarding rather than assuming it.

A third, and one that catches out cost-conscious Indian SMEs specifically, is assuming that a BSP's credit-line billing is always cheaper because it looks like one consolidated invoice. In practice, a credit line often bundles in a margin on top of Meta's own per-message charges, whereas paying Meta directly through embedded signup means you see and pay the exact underlying rate, with no hidden spread.

How Convo360 relates to this model

Convo360 shares a Meta App used for WhatsApp connections and gives businesses direct embedded signup to connect their own WhatsApp number and WABA, which the business owns and controls — it doesn't move between platforms if you switch tools later. This is the same BYOK principle applied to WhatsApp itself: your account, your billing relationship with Meta, no markup added on top. See /docs/whatsapp/.

What actually matters when choosing

Whether a provider is a formal BSP or connects via direct Cloud API access matters less than three practical questions: do you own your WABA outright, can you move it if you switch platforms, and does the connecting company add a markup on top of Meta's own per-message charges. Those answers tell you more about a provider than the BSP label alone, and are worth asking directly before signing up with any platform.

It also helps to ask how template submissions are handled — whether you submit and track approval status yourself inside the platform, or whether it goes through a separate BSP support ticket. The former is generally faster for the day-to-day work of launching new notification templates as your business needs change.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.