You choose a WhatsApp Business Solution Provider (BSP) by starting from your own workflow, not their feature list: decide what WhatsApp needs to connect to, who on your team will use it, and how much automation you want, then compare providers on pricing model, API access, inbox quality, automation tools, integrations, support, data handling and how easily you can leave. The right WhatsApp BSP for a ten-person clinic and for a retailer sending campaigns to 50,000 customers are rarely the same company.
A BSP is a company approved by Meta to provide access to the WhatsApp Business Platform, usually bundled with software on top. This post explains what they actually provide, the questions that separate them, a scoring checklist, and the red flags to watch for. We don't rank providers. Features and prices change too often, and the right one depends on your setup.
What does a WhatsApp BSP actually do?
Meta runs the WhatsApp Business Platform; it doesn't sell you an inbox or a chatbot builder. BSPs fill that gap. Depending on the provider, they offer some mix of:
- Onboarding: help with business verification, connecting a phone number, display name approval and template submission.
- API access: the ability for your systems to send and receive messages, usually through the BSP's own API or webhooks layered on Meta's.
- Team inbox: a shared place for staff to answer chats, with assignment, notes and labels.
- Automation: chatbot or flow builders, auto-replies, and increasingly AI assistants.
- Campaigns: tools to send template messages to opted-in segments and track results.
- Integrations: connectors to CRMs, e-commerce platforms, helpdesks and payment providers.
- Support: help when templates are rejected, numbers get flagged or something breaks.
You can also go direct to Meta's cloud API without a BSP and build the software layer yourself or with a partner. That makes sense when you need custom logic anyway. Our explainer on the WhatsApp Business API vs. the app covers the basics.
What should you decide before you look at providers?
Answer these five questions first. They narrow the field faster than any demo.
- What's the main job? Customer support, sales conversations, bookings, order updates, marketing campaigns, or an AI assistant. Most providers are stronger at one or two.
- Who uses it? How many agents, in how many locations, in which languages.
- What must it connect to? Your CRM, e-commerce platform, booking system, ERP or accounting software. List them by name.
- How much automation, and who builds it? A few auto-replies your team configures, or an AI assistant with custom tools built by a developer.
- What volume? Rough inbound chats per day and outbound templates per month. This drives cost more than anything else.
How do BSP pricing models differ?
Prices change and vary by country, so we won't quote any. Check each provider's current pricing and Meta's current rates for your market. What you can compare is the shape:
| Cost element | What to ask |
|---|---|
| Meta's messaging fees | Are they passed through at cost, or with a markup? Is the markup a percentage or a fixed amount per message? |
| Platform subscription | Monthly or annual? What's included, and what's an add-on? |
| Per-seat fees | Is pricing per agent? What counts as a seat? |
| Automation and AI | Are chatbot sessions or AI replies charged separately? Can you use your own LLM key? |
| Setup and onboarding | One-time fees? What do they include? |
| Minimum commitments | Prepaid credits, annual contracts, minimum message volumes? |
For illustration only: a provider with a low subscription but a markup on every message can end up costing more for a high-volume sender than one with a higher subscription and pass-through pricing. Model your own volumes across at least two providers before deciding.
Which features actually matter?
Most demos show the same screens. These are the questions that tell providers apart.
API and webhook access. Can your own systems (or an automation tool like n8n or Make) send and receive messages through them? Is the API documented and stable? If you'll ever want custom automation or an AI assistant, this is essential.
Inbox quality. Assignment rules, sticky ownership for returning customers, internal notes, service-level timers, search, and a usable mobile app for staff in the field.
Automation and AI. Can the flow builder handle your real booking or support flow? If an AI assistant is offered, can it be grounded in your own documents, can you control what it says, and does it hand off cleanly to a person? Our guide to WhatsApp AI agents explains what good looks like.
Integrations. Native connectors for your CRM and store, and how deep they go. Does the CRM sync log conversations, create leads, and update fields, or just push a contact? See how to connect WhatsApp to your CRM.
Campaign tools. Segmentation, opt-in and opt-out tracking, frequency caps, and per-campaign reporting on blocks and replies.
Template management. Submitting, tracking and editing templates, with clear reasons when Meta rejects one.
Reporting. Response times, resolution, agent workload, campaign results, and exports you can analyze yourself.
What about data location, security and ownership?
These are easy to skip in a demo and painful to fix later.
- Who owns the WhatsApp Business account and number? It should be registered to your business in your own Meta business account, with the BSP given access, not owned by the BSP.
- Can you migrate the number to another provider or to the direct API if you leave? Ask how, and how long it takes.
- Where is chat data stored, and in which country? This matters for privacy obligations under laws like GDPR or India's DPDP Act, which depend on your jurisdiction, so check current rules or ask counsel.
- How long are messages retained, and can you set retention yourself?
- Is chat data used to train AI models? Get the answer in writing.
- Access controls: roles, single sign-on, audit logs of who viewed or exported conversations.
- Data export: can you get your full conversation history and contacts out in a usable format?
What does support look like in practice?
When a template is rejected the day before a launch, or the number's quality rating drops, you need a person who understands WhatsApp policy, not a ticket that closes in a week. Ask:
- What support hours and channels are included in your plan?
- Is there help with template approvals and policy questions?
- Is onboarding support included, and does it cover verification?
- Do they have references from businesses of your size and industry? Speak to one.
What are the red flags?
- They offer "unlimited" messaging to anyone, or suggest you don't need opt-in. Legitimate providers must follow Meta's policies.
- They're not actually on the official platform. Some tools sell "WhatsApp automation" that drives the regular app or WhatsApp Web. That breaks WhatsApp's terms and risks a permanent ban on your number. Confirm the provider is an approved partner using the official API.
- They want to own your number or your Meta business account.
- No clear exit path for your number and data.
- Vague pricing that only becomes clear after you've committed.
- Long lock-in contracts before you've tested with real traffic.
How do you run a fair comparison?
- Shortlist two or three providers that fit your main job, integrations and region.
- Score them on a simple sheet: pricing at your volumes, API access, inbox, automation, integrations, support, data and exit terms.
- Run a trial with real conversations, not just a demo. Connect a test number, send a few templates, route chats to two agents, and test the CRM sync.
- Check the fine print: contract length, markup, data terms and number migration.
- Decide what you'll build yourself. If your AI or integration needs are custom, pick the provider with the best API and inbox and build the rest. Our guide to build vs. buy for AI agents helps with that call.
Frequently Asked Questions
Do I need a BSP, or can I go directly to Meta?
You can use Meta's cloud API directly, but you then need to build or buy the inbox, automation and integrations. A BSP makes sense if you want those ready-made. Going direct suits businesses with developers or a partner building custom workflows.
Are BSPs more expensive than using the API directly?
Usually somewhat, because you pay for their software and sometimes a markup on Meta's fees. That can still be cheaper than building an inbox and integrations yourself. Compare total cost at your real volumes.
Can I switch BSPs later?
Generally yes, if the WhatsApp Business account and number are registered to your business. Ask each provider how number migration works and how to export your data before you sign.
Does the BSP affect my chances of getting banned?
The BSP doesn't control your behavior, but a good one helps you follow policy with opt-in tracking, frequency caps and template guidance. Your quality rating depends mainly on who you message and what you send. See our guide to automating WhatsApp without getting banned.
Can a BSP provide an AI chatbot?
Many offer flow builders and some offer AI assistants. Check whether the AI can use your own knowledge, whether you control its rules and handoff, and whether you can connect your own AI system through their API if theirs isn't enough.
Want an unbiased second opinion on your WhatsApp setup?
We don't resell any provider. If you're comparing BSPs or wondering whether to go direct, tell us what WhatsApp needs to do for your business and we'll help you weigh the options against your systems. See our AI automation service for the build side.