WhatsApp BSP vs Tech Provider vs Solution Partner

What is a WhatsApp BSP, and does Meta still use the term?

BSP stands for Business Solution Provider. It is the phrase this market runs on, and it is not the phrase Meta uses. Meta's current partner documentation names three types — Solution Partners, Tech Providers and Tech Partners — and the words "BSP" and "Business Solution Provider" appear nowhere on that page (source).

Meta has published no notice retiring the word, and it survives everywhere else — vendor pages, agency posts, procurement checklists. But Meta's own documentation neither defines it nor grades it, so "BSP" tells a buyer only that a company has WhatsApp Business Platform access, which is true of every vendor on the shortlist.

Meta's three names tell you something far more useful: who Meta bills for your messages, and therefore who is in a position to set that price.

Checked against Meta's partner documentation on 22 August 2026.

• What is a WhatsApp BSP, and does Meta still use the term?
• What are Meta's WhatsApp partner types?
• What is a WhatsApp Solution Partner?
• What is a WhatsApp Tech Provider?
• Why can a Solution Partner resell Meta's message fees when a Tech Provider cannot?
• What does the difference do to your bill?
• Who owns your WhatsApp number under each model?
• Can a Tech Provider bill you for messages anyway?
• How can you tell which tier a vendor is?
• Which tier is WabaCRM?
• Which model should you prefer?

What are Meta's WhatsApp partner types?

Meta publishes its own comparison table. Here it is with the row labels quoted rather than paraphrased, because the wording of two of them is the entire subject of this page.

Read from Meta's partner documentation on 22 August 2026 (source).

Look at the first row and the last. Every tier can offer the full platform, and every tier reaches Meta's Direct Support. These are not capability grades, and a vendor implying otherwise is describing a table that does not say so.

The third column needs no section below, because Meta defines it in one line: Tech Partners are "Tech Providers who are, or are eligible to become, Meta Business Partners." Same billing position as a Tech Provider, plus the badge.

What is a WhatsApp Solution Partner?

Meta defines Solution Partners as "Meta Business Partners that provide a full range of WhatsApp Business Platform services to other businesses (clients), such as messaging services, billing, integration support, and customer support."

Two further sentences on the same page do the real work. Solution Partners have "credit lines which can be extended to clients who they bring on board, thus removing the need for those clients to enter their own payment method during the onboarding process." And they "can directly invoice their clients for the WhatsApp Business Platform services provided through their apps."

So Meta bills the partner and the partner bills you. That can mean one invoice instead of two, billing in your own currency, and payment terms rather than a card charge. For a company with a procurement process, those are real advantages and not marketing.

Meta closes the section by telling would-be partners the tier is a choice rather than a rung: "Note that becoming a Solution Partner is a lengthy process, so if you don't need a credit line and don't need to invoice your clients for API usage directly, consider becoming a Tech Provider instead." A credit line is the thing being chosen — not a level of approval.

What is a WhatsApp Tech Provider?

Meta describes Tech Providers as "similar to Solution Partners in that they also can offer a full range of WhatsApp Business Platform services to other businesses, either by providing these services on their own, or by partnering with a Solution Partner who already offers these services" — then names the difference plainly: "Unlike Solution Partners, however, Tech Providers do not have credit lines."

Meta then spells out what that means for you in two sentences, and those two sentences are the whole tier. Clients onboarded by a Tech Provider "must provide their own payment method after onboarding is complete. Meta will then bill these clients for API usage, and the Tech Provider will bill for other services."

So Meta bills you directly, against your own WhatsApp Business Account, at Meta's own published rate. The platform bills you for software and nothing else.

The cost is in the first of those two sentences and cannot be skipped. The payment method goes on your own Meta account, after onboarding and before your paid messages start, and any dispute about that bill is between you and Meta. No credit line also means no payment terms. A vendor selling its tier to you as "no credit card" is describing its own invoice, not the job.

Why can a Solution Partner resell Meta's message fees when a Tech Provider cannot?

Because reselling requires being billed first, and only one tier is.

A credit line puts the partner in the payment path: Meta invoices the partner for API usage, and the partner invoices you. Once there is an invoice in the middle, the number on it is a price the partner chooses. Meta's own row for this reads "Bills customers directly for API usage (vs. Meta billing customers for usage)" — Yes for Solution Partners, No for Tech Providers.

A Tech Provider has no invoice to mark up. Meta charges your card for your messages and the vendor never touches the transaction. There is no markup to remove because no fee passes through.

This is why "what is your per-message rate?" is the diagnostic question. A vendor that answers with a number of its own is billing you for messages, which means a credit line — its own, or a Solution Partner's that it has been allowed to share. Both cases are covered below.

What does the difference do to your bill?

One dated fact underpins the right-hand column. Meta's pricing documentation states that "effective July 1, 2025, Meta charges on a per-message basis", replacing the older conversation-based model (source). The widely repeated "1,000 free conversations a month" allowance went with it, so a vendor still quoting that in 2026 is reading a rate card Meta retired over a year ago. What Meta genuinely does not charge for is narrower and more specific, and is set out in what Meta charges for and what it does not.

Checked against Meta's pricing documentation on 22 August 2026.

Who owns your WhatsApp number under each model?

You do, under both, in the flows Meta documents. This is the point most comparison pages get wrong, usually in a Tech Provider's favour.

Meta's Embedded Signup documentation states that "business customers onboarded via Embedded Signup own all of their WhatsApp assets" and "have full access to WhatsApp Manager" — adding, pointedly, "Note that you cannot restrict this access in any way" (source). The partner-initiated route, which Meta documents for Solution Partners only, ends the same way: where a partner creates the account for a client, "the WABA will be created and its ownership will be assigned to the client" (source).

One asymmetry is worth knowing, and Meta states it on that same page: "Clients cannot add their own payment method to a WABA created via the partner-initiated WABA creation process." You own the account; the credit line stays the partner's. If leaving matters to you, ask which flow you were onboarded through.

Can a Tech Provider bill you for messages anyway?

Sometimes, and legitimately. Meta documents multi-partner solutions, which "allow Solution Partners and Tech Providers to jointly manage client WhatsApp assets in order to provide WhatsApp messaging services to their clients." Under one, "clients onboarded via Embedded Signup configured with a solution ID share the credit line of the Solution Partner associated with the solution" (source).

So a Tech Provider can put you on a Solution Partner's credit line. If a vendor calls itself a Tech Provider and still quotes a message rate, this is the likeliest explanation and there is nothing wrong with it. What settles your bill is whose credit line you are on, not what the vendor calls itself.

How can you tell which tier a vendor is?

Three checks, in order of how quickly they settle it.

Ask who Meta bills for your messages. A Tech Provider's answer is "Meta bills you." A Solution Partner's is "we do." There is no third answer, and a vendor that will not answer plainly has told you something.

Ask for their per-message rate. If they quote one, compare it against the rate card Meta publishes by country and category (source). The difference is the margin, and a visible margin is not a scandal — an invisible one is.

Look in WhatsApp Manager. You have full access and Meta forbids a partner from restricting it. If your own payment method and message charges are sitting there, Meta is billing you.

Which tier is WabaCRM?

Tech Provider, verified by Meta on 30 July 2026. What follows from that is not our policy, it is what the tier means — and we would rather state it here than have you find it out at your first broadcast.

Meta bills you directly for messages at its published rate, and we neither resell nor mark those fees up; there is no invoice in the middle to mark up. Our own bill is software only — ₹96 per 1,000 contacts a month with unlimited team members, free for the first 1,000 contacts with no expiry. And you attach a card to your own Meta account before your first paid message, because this tier carries no credit line to put you on.

We also do not claim a Meta partnership: Meta's table has a row reading "Is a Meta Business Partner" and Tech Providers are a documented No on it. Who operates this platform is on the about page, and the platform itself in the WhatsApp Business API, explained end to end.

Which model should you prefer?

There is no universal answer, and a vendor offering you one is arguing its own tier.

Prefer a Solution Partner when procurement is the constraint — a single invoice, payment terms, local-currency billing, or a finance team that will not put a card on a Meta account. A credit line is a real solution to a real problem. The trade is that your message rate becomes something you negotiate rather than something you look up.

Prefer a Tech Provider when the message bill is the constraint — you want Meta's published rate, verifiable by you, and the only variable your platform controls to be the software fee. The trade is the card, two invoices and no credit.

Either way, the tier settles exactly one thing: who bills you for messages. It does not settle capability, it does not settle who owns your number, and it says nothing about whether the software is any good.

Coexistence is the clearest illustration. Meta's onboarding documentation requires only that a partner "must already be a Solution Partner or Tech Provider" (source) — both tiers qualify, so the tier answers nothing. The question that does is whether the vendor has run a coexistence connection through to completion. Compare platforms on that, and on what the vendors most people evaluate publish about their pricing.

Every Meta quotation on this page was read from Meta's developer documentation on 22 August 2026. Meta changes that documentation without notice; the linked pages are authoritative and this one is not.