WhatsApp Business Solution Provider (BSP): what this partner does and how to choose one
Messaging has become an established contact channel in France. According to the Digital Barometer produced by Crédoc for Arcep, Arcom, CGE, and ANCT, 86% of the population uses instant messaging services, and 64% use them daily.
Messaging has become an established contact channel in France. According to the Digital Barometer produced by Crédoc for Arcep, Arcom, CGE, and ANCT, 86% of the population uses instant messaging services, and 64% use them daily.
Businesses are following the trend. But as soon as an entire team needs to respond, campaigns need to be sent to a contact base, or conversations need to feed into a CRM; the free WhatsApp Business app reaches its limits. You then need to move to the WhatsApp Business Platform, in other words, the API. And the most common way to access it is through an intermediary approved by Meta: a Business Solution Provider, or BSP.
This guide explains what a BSP really is, what it does and does not do, how much it costs beyond the advertised rates, what the alternatives are, and how to choose one without becoming locked into a solution that is difficult to leave.
What is a WhatsApp Business Solution Provider (BSP)?
In short: a BSP (Business Solution Provider) is a third-party company authorized by Meta to connect your business to the API for WhatsApp Business. It handles the technical integration, API hosting or relay, message template approval, and billing, most often through its own dashboard.
Meta's official definition
Meta does not provide a direct interface for businesses to operate its API. The BSP therefore sits between the two: it provisions the account, connects the number, routes messages, and provides support.
In its developer documentation, Meta uses the generic term "solution providers" for companies that deploy value-added solutions on behalf of business customers. These partners must meet the platform's technical requirements and policies before they can onboard customers.
The other names you will come across
"WhatsApp Partner," "WhatsApp Business Service Provider," "WhatsApp Business solution provider": these expressions refer to the same thing. Meta's official name remains WhatsApp Business Solution Provider. Useful to know when comparing offers written by different providers.
WhatsApp Business app or API: when a BSP becomes necessary
The limits of the free app
The WhatsApp Business app is perfectly suited to a freelancer or very small team handling a moderate volume of conversations manually. It offers greeting messages, quick replies, labels, and broadcasts to small lists. As long as one person can keep track of all exchanges and detailed reporting is not an issue, it is enough.
Five signs that mean you need to move to the API
The switch becomes necessary as soon as one of these needs appears:
- Several agents need to handle conversations without stepping on each other's toes, with assignment rules and managerial visibility;
- Outbound campaigns need to be sent to an opt-in base, that is, contacts who have expressly agreed to receive your messages—using templates approved by Meta;
- Conversations need to feed into a CRM or an existing support tool;
- Reporting by agent, campaign, or response time becomes a management criterion;
- Monthly volume exceeds what can be handled manually.
Staying on the app beyond this point increases response times and hides performance problems because there is no proper measurement.
Why Meta requires businesses to go through a WhatsApp BSP
A business model built after the acquisition
When Meta acquired WhatsApp, the company committed not to run ads in the app. It therefore needed another revenue model: the WhatsApp Business API, billed to businesses.
There was still a scale problem. Supporting hundreds of thousands of companies through technical integration, verification, and day-to-day support would have required a huge workforce. Delegating this role to a network of approved partners was faster and less expensive.
What the BSP handles for you
In practical terms, going through a BSP means you do not have to handle:
- Setting up and maintaining a webhook server, the component that receives incoming messages sent by Meta in real time;
- Submitting, tracking, and correcting message templates with Meta;
- Monitoring compliance rules that change regularly;
- Monitoring the account quality rating, the indicator Meta uses to measure recipient satisfaction, and the associated messaging limits;
- Developing a conversation interface for your teams, since the raw API does not provide one.
Few companies have the internal resources to handle these projects sustainably. That is exactly where BSPs come in.
How a WhatsApp BSP works in practice
From WABA creation to number activation
The integration process always follows the same steps, which the BSP handles to varying degrees:
- Business verification with Meta, supported by legal documents;
- Creation of the WhatsApp Business Account (WABA) and connection to Meta Business Manager, the space where Meta groups your advertising and business assets;
- Phone number activation, either by porting an existing number (mobile, landline, or special number) or by assigning a new number;
- Approval of the display name, controlled by Meta;
- Submission of the first message templates and implementation of consent collection.
Two questions to ask during the sales process: which steps does the provider actually carry out for you, and which depend on Meta alone? Business verification, display name approval, and template approval are handled by Meta, not the provider, so they can still block your launch after you sign.
The software layer added on top of the API
This is where offers really differ. Beyond API access, most BSPs provide a product that your teams use every day:
- Shared inbox: several agents handle conversations without collisions, with automatic assignment and a managerial view of workload;
- Workflow automation: routing by intent, priority, or team, with follow-ups triggered automatically;
- Campaign broadcasting: sending promotional or transactional messages to opt-in audiences;
- Template management: submission, approval tracking, and correction without leaving the platform;
- Rich messages: images, buttons, selection lists;
- AI agents and chatbots: contact qualification, answers to recurring questions, handoff to a human with full context;
- Integrations: CRM, e-commerce, support tool, marketing automation;
- Analytics: response times, resolution rates, campaign performance.
A simple way to compare providers is to link each capability to the business result it needs to deliver. If your priority is recovering abandoned carts, e-commerce triggers and order synchronization matter, not the depth of the chatbot builder.
What a BSP does not do for you
Here is the limitation sales pages rarely mention: the BSP provides the transport, not the result. It makes the API accessible and gives you tools. It does not design your conversational strategy, your content, your scenarios, or your opt-in base.
Without a defined journey, content, and qualification rules, an excellent provider will only reproduce your current results faster and at a greater scale. Choosing a provider is an infrastructure decision, not a marketing strategy decision.
WhatsApp BSP, Cloud API, or connected account: three access routes
Before comparing providers, make sure a BSP is actually the right route. There are three options, and they do not address the same need.
Meta's Cloud API directly
You connect directly to Meta's endpoints, with no intermediary and no per-message markup. In return, you build everything else: inbox, automation, routing, integrations, reporting, and hosting for your application layer.
This route suits teams with developers and a clear reason to control their technical stack. It is also the least expensive option on paper, provided you properly value development and maintenance time.
Going through a BSP
You get API access, integration support, and, depending on the provider, a complete platform. This is the most common route and the fastest for sales or support teams that want to deliver results without building infrastructure.
The connected account API, a separate route
This third option is absent from most comparisons, even though it solves a different problem. Rather than creating a new business identity, it authenticates an already active WhatsApp number on behalf of its owner, generally through pairing or by scanning a code.
The typical use case is a software, CRM, or ATS (applicant tracking system) vendor whose end users each want to connect their own WhatsApp account. No Meta Business verification, no template approval, near-instant setup. In return, you operate outside the official WhatsApp Business Platform framework: no service guarantee and no recourse if Meta restricts access. This deserves serious consideration before committing.
The question that separates these three routes can be summed up in one sentence: one number messaging many people, or many people each using their own number? The first two options address the first case; the third addresses the second. Choosing the wrong route is costly to correct because the integration has to be rebuilt from scratch.
Note: Meta's On-Premises API, long used for hosting on your own servers, has been discontinued. Check the exact timeline in Meta's documentation if you are still running an older integration.
How much does a WhatsApp BSP cost?
Your bill always has two layers: what Meta charges, which is the same regardless of provider, and what the provider adds on top. Comparing BSPs therefore means comparing the second layer.
Fees charged by Meta
According to Meta's official pricing page, billing has been per message since July 1, 2025, replacing the previous conversation-based model. The rate depends on the message category and the recipient's country.
There are three template categories: marketing, utility, and authentication. Service messages are added to these, meaning free-form replies sent within the 24-hour window opened by a customer message.
Pay attention to the current timeline. Meta announced pricing changes taking effect on August 1 and October 1, 2026, notably affecting service messages and utility templates sent within the 24-hour window. If you are building a budget, check the pricing in force at the time of launch rather than relying on a comparison article, however recent.
A direct consequence for provider selection: the broader the scope of billable messages becomes, the more heavily any per-message markup weighs.
Fees added by the BSP
Six cost items to examine, line by line:
- Setup fees: one-time charges; check what they actually cover (training, migration, template creation);
- Platform subscription: inbox, automation, analytics;
- Hosting fees: sometimes charged per WhatsApp Business account or connected number;
- Per-seat or monthly active contact pricing: the first model grows with team size, the second with database size;
- Per-message markup: added to Meta's rates, and the easiest cost to underestimate;
- AI and automation options: included by some providers, billed separately by others.
How to spot hidden costs
A markup that looks negligible per unit changes scale with volume. A few thousandths of a dollar per message add up to several hundred dollars for every hundred thousand messages sent.
Two habits protect your margin:
- Ask for a complete pricing schedule in writing, explicitly including the wording "no per-message markup" if the provider makes that claim;
- Model your monthly cost at your current volume, then at three times that volume. The cheapest offer today is not necessarily the one that will stay cheapest as you scale.
Finally, check the pricing model against your growth path: an attractive entry-level plan becomes expensive if your seats, options, or database grows faster than your conversation volume.
The limitations and lock-in risk of a WhatsApp BSP
Restricted access to new features
Some providers run their own version of the API rather than staying as close as possible to Meta's. One possible consequence is a delay of several months before you can use a new feature or even long-term unavailability. Ask how the provider rolls out platform changes and within what timeframe.
Required platform or CRM
Many BSPs integrate the API into their own messaging platform, sometimes bundled with an in-house CRM. This creates two risks: paying for features that duplicate your existing tools and being unable to connect to the CRM your teams already use.
A provider should not restrict your freedom to integrate. Check for native connectors to your current stack, not just the existence of a generic API.
What transfers (and what does not) during a migration
This is the point most often discovered too late. Changing BSP is possible, but under certain conditions, and not everything moves with you.
What generally transfers:
- The phone number, if both providers support porting;
- The WhatsApp Business account, provided it is linked to your own Meta Business Manager;
- The display name and business profile.
What generally does not transfer:
- Conversation history, which stays on the old platform;
- Approved templates, which must be resubmitted and approved again;
- Automation workflows, which must be rebuilt;
- Contact lists, depending on the former provider's export policy.
Also plan for a short interruption in sending and receiving. The true cost of switching is therefore not technical but commercial: campaigns paused, leads unanswered, and support slowed while everything is rebuilt.
Four questions to ask before signing and to have confirmed in writing:
- Will my WhatsApp Business account belong to my Meta Business Manager or yours?
- Can I export my contacts and conversation history?
- What is the process and timeline if I decide to change providers?
- Are there exit fees or a minimum commitment period?
Seven criteria for choosing your WhatsApp BSP
Technical and contractual criteria
BSP, Solution Partner, Tech Provider: Who will bill you for what?
Meta's official documentation distinguishes three partner statuses, and this administrative detail determines who sends you the bill:
- Solution Partner: the most comprehensive status. These partners have a credit line they can extend to their customers, which means customers do not need to enter their own payment method during onboarding. They can also bill customers directly for API usage.
- Tech Provider: It can offer all platform services, but without a credit line or direct billing for API usage.
- Tech Partner: an intermediate status, available by upgrading from Tech Provider status.
In practical terms, with a Solution Partner, Meta usage may appear on the provider's invoice, and you only see one total amount. With a tech provider, you enter your own payment method with Meta and can see line by line what the platform costs you. This is a question to ask from the first sales conversation.
Data residency, a decisive criterion in Europe
This point is often absent from English-language comparisons, even though it shapes the decision for a French company subject to the GDPR.
Providers whose headquarters and data centers are located in the European Union offer the clearest story on this front. Several market players are European as well: German, Croatian, Dutch, or French, depending on the provider.
That said, headquarters alone are not enough. Always request the data processing agreement (DPA, the contract required by the GDPR between you and your provider), the list of subprocessors, and the actual location of processing for your use case. A European provider may still rely on infrastructure hosted elsewhere.
Channel coverage beyond WhatsApp
A WhatsApp-only platform is enough as long as all your business conversations begin and end on that channel. It becomes a constraint as soon as contacts also arrive through Instagram, email, or SMS: you then need a second contract, a second inbox, separate routing rules, and reports that do not line up.
Before signing, ask whether your agents need to work from one shared workspace and whether your managers need a consolidated view of response times and conversion across all channels.
Overview of the types of WhatsApp BSPs on the market
Rather than a named ranking that will become outdated within a few months, here are the four provider categories and the profile each one suits.
How to verify that a provider is officially approved
Meta's partner directory is the only up-to-date reference. If a provider presents itself as an official BSP but does not appear there, ask which approved partner it actually uses. Some companies do offer a managed-services layer on top of a third-party BSP, which is perfectly legitimate as long as it is clearly disclosed.
Compliance and Meta rules: what your WhatsApp BSP should help you manage
Opt-in, templates, and the 24-hour window
WhatsApp applies strict rules, and failing to follow them can block your campaigns or suspend your account. Five points define the framework:
- Consent: recipients must have explicitly agreed to receive your messages. Valid consent states the company name, the type of messages expected, and how to opt out;
- Template approval: any business-initiated message must use a template approved by Meta;
- The 24-hour service window: free-form replies are only possible within 24 hours of a customer message. After that, only a template can be used to resume contact;
- The quality rating: Meta evaluates your account based on user feedback, including blocks and reports. A lower rating reduces your messaging limits;
- Messaging limits: a new account starts with limited reach, which increases if quality remains good and usage is consistent. So do not assume you can reach your target volume from day one.
Three questions to ask your future provider: How do you help me collect compliant consent? Do you flag risky content before a template is submitted? Can I track my quality rating and limits from your dashboard?
GDPR and messaging prospecting
The French framework does not disappear because the channel changes. In B2B, the CNIL accepts prospecting based on the company's legitimate interest, provided the subject of the outreach relates to the profession of the person being contacted. In B2C, prior consent remains the rule.
In both cases, the person must be informed of how their data is used and be able to object easily at any time. So check that your provider propagates an opt-out across all your scenarios, not just the campaign concerned.
WhatsApp under the Digital Markets Act
One final point of context, useful for planning ahead. Since September 6, 2023, Meta Platforms has been designated a gatekeeper under the European Digital Markets Act, notably for WhatsApp and Messenger, classified as number-independent interpersonal communications services.
Article 7 of the regulation therefore requires, on request and free of charge, interoperability of basic functionalities with other messaging services. The first two third-party services interoperable with WhatsApp were launched in November 2025, as stated on the European Commission's dedicated portal. The Body of European Regulators for Electronic Communications (BEREC) has issued several opinions on the reference offer published by Meta.
This does not change how BSPs operate today. But it is a signal: the channel is evolving under regulatory pressure, and access rules could change again.
How to proceed in practice
A six-step method that can be applied in a few weeks:
- Clarify your prerequisites: access to Meta Business Manager, verification documents, the number to use, priority use case, estimated monthly volume, required integrations, and, above all, a clearly identified internal owner.
- Build a shortlist of three to five providers, checking that they appear in Meta's directory.
- Calculate the total cost: Meta rates, subscription, hosting, seats or active contacts, and any markups at your current volume and at three times that volume.
- Validate reversibility and support: porting conditions, ownership of the WhatsApp Business account, support hours, and escalation channel in the event of an incident.
- Run a one-week proof of concept: connect a test account, send a template, check routing, automate one, hand off to a human agent, and report.
- Define your success criteria before deployment: target response time, routing accuracy, and reporting visibility.
Step 5 is the one most often skipped and the most revealing. A sales demo shows a product that works; a proof of concept shows how it behaves with your data, your templates, and your teams.
