Summarise this article with:
On this page
- What a WhatsApp Business Solution Provider actually is
- How to evaluate any WhatsApp Business API provider: the 10-point checklist
- Provider categories you'll encounter
- Build your own comparison scorecard
- Which provider suits which team
- What switching actually costs
- Five questions to ask on a sales call
- What most teams get wrong when choosing a provider
- Get started with InfiQ
Almost every buyer's guide on this topic is written by a provider. Ours included. So instead of a ranking, this post gives you the ten questions we watch teams fail to ask, and an honest account of what it costs to change your mind eighteen months later.
All of these platforms sell access to the same thing. Meta operates the WhatsApp Business Platform; everyone else — InfiQ included — is a Solution Provider on top of it. Message delivery, template review, quality rating and messaging limits are Meta's, identically. What differs is the software around the API, the commercial structure, and who picks up the phone when a number goes yellow on a Saturday night.
Which makes the decision narrower than it looks. Two platforms with matching feature lists can differ by lakhs a year on a 200,000-message-a-month account, purely on markup.
InfiQ is one of the platforms you'll come across while evaluating this market. Pricing and features across all providers change often — verify current details on each provider's own site before deciding.
Key points
- A WhatsApp Business Solution Provider is a Meta-approved partner that provisions your WhatsApp Business Account and resells API access alongside its own software.
- Your WhatsApp bill has two layers: Meta's per-message rate, identical whichever provider you use, and your provider's platform fee plus markup.
- Meta moved to per-message pricing on 1 July 2025 and resumes charging for service messages and in-window utility messages from 1 October 2026.
- Messaging limits and quality ratings sit at Meta portfolio level and follow your number, so switching platform does not reset a damaged rating or a 250-message tier.
- The most useful sales-call question is the per-category markup in paise, in writing, before any discount.
What a WhatsApp Business Solution Provider actually is
A WhatsApp Business Solution Provider (BSP) is a company Meta has approved to provision WhatsApp Business Accounts, submit templates and send messages through the WhatsApp Business Platform on behalf of other businesses. Meta's documentation uses "Solution Provider" and "Tech Provider" for slightly different roles, but the meaning holds: they own the relationship with Meta that lets your number send at scale.
Hence the two-layer bill teams misunderstand until the second invoice. Meta charges per message by category and market, on rate cards published in INR among other currencies, and those rates do not move with your provider. InfiQ's pricing guide separates the layers; the cost page works the arithmetic.
| Layer | Who charges it | Varies by provider? | What to ask for |
|---|---|---|---|
| Per-message rate | Meta | No — Meta's rate card applies | The current INR rate card for your categories |
| Volume tier benefit | Meta | No — portfolio-wide, resets monthly | Whether the tier saving reaches your invoice |
| Platform / seat fee | Provider | Yes, substantially | Annual cost at projected headcount |
| Per-message markup | Provider | Yes, often undisclosed | The markup in paise, per category, in writing |
| Support | Provider | Yes, enormously | Named response times, in the contract |
Two details matter before you talk to anyone. Meta may only change pricing on 1 January, 1 April, 1 July or 1 October, with one month's notice for a rate-card update and six for a model change, so no provider can honestly call a rate rise a surprise. And utility and authentication rates get cheaper at higher monthly volumes across your portfolio — ask whether that saving is passed through.
How to evaluate any WhatsApp Business API provider: the 10-point checklist
This is the section to steal. It is written to be useful whichever platform you pick, including one we do not sell.
-
Solution Provider status, verified directly. Confirm the vendor is an approved Meta partner, not a reseller of a reseller. Ask which entity appears as Solution Provider on your WhatsApp Business Account, then check it in Meta Business Manager after onboarding.
-
Per-message markup transparency. Ask for the markup in paise across marketing, utility, authentication and service, in writing. "Meta rates plus platform fee" is not an answer, and nor is a per-conversation price — conversation pricing was deprecated after Meta's per-message pricing change on 1 July 2025.
-
Template submission and approval support. New accounts stall on templates. Ask who writes your first thirty, the turnaround on a rejection, and whether a human checks your copy for category risk. Meta reviews templates and appeals within 24 hours, so a provider taking four days is the bottleneck. See WhatsApp template categories.
-
Quality rating monitoring. Ask to see the screen. Meta exposes quality as GREEN, YELLOW, RED and UNKNOWN, and template statuses from Active–Quality pending through Paused and Disabled. Alerting on those beats discovering a problem when a broadcast fails; the quality rating guide covers what to watch.
-
Messaging limit and throughput handling. Meta sets limits at portfolio level on a ladder of 250 → 2,000 → 10,000 → 100,000 → unlimited, with throughput scaling to 1,000 messages per second for eligible numbers at Medium or higher quality. Ask how the platform paces a broadcast against your tier, and what it does on error 131049.
-
WhatsApp Flows support, and how deep. Flows are multi-screen forms inside the chat, on Android 6.0+ and iOS 12+, with WhatsApp Web support rolling out from December 2025. Ask whether the platform supports endpoint Flows calling your own HTTPS server or only static screens, and which Flow JSON version it publishes against.
-
Coexistence and onboarding path. If you run the WhatsApp Business app today, ask exactly what happens to that number and those chats, and whether it can be reverted. Small teams need this answered most and get it hand-waved most. Get it in writing.
-
API rate limits and webhooks. Ask for the platform's own rate limits, not Meta's, because that is where integrations break. Ask whether webhooks deliver raw Meta payloads or a proprietary transformation — the transformation is the lock-in. Compare against InfiQ's webhooks guide.
-
Migration help, in and out. Ask what they do to bring you in, then what they do to let you leave. The second answer matters more. InfiQ's Cloud API versus on-premises migration post covers what technically transfers.
-
Data handling, residency and support SLA. Ask where message content sits, the retention period, who can read your inbox, and how deletion works. India's DPDP regime makes consent and notice your obligation, not your provider's — take your own legal advice on current requirements, then get the SLA in writing with named response times per severity.
Provider categories you'll encounter
Rather than a per-vendor rundown that goes stale the moment a pricing page changes, here are the shapes providers tend to take in this market. Knowing which shape you're evaluating tells you which of the ten checklist questions to lean on hardest.
- Broadcast and campaign platforms emphasise high-volume sending with self-serve onboarding. Ask how throughput scales past your current volume, and what the markup looks like above 100,000 messages a month.
- Commerce and catalogue platforms build around product catalogues and order-lifecycle messaging for D2C sellers. Ask whether the catalogue integration is native or a bolt-on, and how it behaves at peak-season order volume.
- Team-inbox-led platforms put a shared inbox and agent workflow first. Ask whether pricing is seat-driven or volume-driven — the two scale very differently as headcount and message volume grow at different rates.
- Sales-enablement platforms focus on no-code chatbots for inside-sales and lead qualification. Ask for the developer-grade API surface if you expect to outgrow the no-code builder.
- Field and distributor-sales platforms optimise for mobile catalogue sharing by a distributed sales team. Ask about marketing automation depth if that is also on your roadmap.
- Lifecycle and retention platforms build around triggered journeys and automation sequences for consumer brands. Ask about enterprise governance controls — audit trails, role-based access — if you operate at scale.
- AI-led support platforms position around automated resolution for high inbound volume. Ask what that resolution actually costs at your ticket volume against a human-staffed inbox, and how it behaves once Meta resumes charging for service messages.
- Enterprise multi-channel CPaaS bundles WhatsApp with SMS, RCS and other channels on one procurement contract. Ask whether that consolidation is worth losing WhatsApp-specific depth.
- Developer-first CPaaS sells API primitives rather than an application — you build the inbox, template lifecycle and quality monitoring yourself. Ask whether you actually have the engineering capacity that model assumes.
- Agency and embedded-infrastructure platforms run bring-your-own-frontend, aimed at agencies reselling or teams embedding WhatsApp in their own product. Ask whether you have the interface already, or are also signing up to build one.
- Application-layer platforms — InfiQ among them — ship a shared team inbox, broadcast campaigns, a template library, a chatbot builder and analytics on top of the API, so you are not building the interface yourself. Ask what's included at your plan tier versus billed as an add-on.
None of this tells you which category wins; it tells you which questions to lean on once you know which shape you're looking at. Run every shortlisted provider through the ten-point checklist above regardless of category.
Build your own comparison scorecard
Feature lists and pricing pages change often enough that publishing a snapshot here would be stale before you read it. Build the comparison yourself instead, on this scaffolding, using each provider's own current numbers:
| Criterion | What to ask every provider for |
|---|---|
| Commercial model | Fixed platform fee, per-message markup, or both — in writing |
| Markup | The figure in paise, per category, not a percentage or "varies by plan" |
| Flow builder | Whether it calls your own HTTPS endpoint or ships static screens only |
| Exit path | What they export, in what format, and how long it takes |
| Support model | Named response times per severity, not "24/7 support" as a phrase |
Fill in a column per shortlisted provider yourself. A vendor's sales call or current pricing page is the only reliable source for any of this — treat the table as a question list, not a scoreboard.
Which provider suits which team
Segment first, shortlist second. Bad choices come from five-person teams buying enterprise platforms, and 200-agent operations buying campaign tools.
| Team shape | What actually constrains you | What to prioritise |
|---|---|---|
| Solo seller, 1–3 people | Fixed cost and setup time | Self-serve onboarding, a trial, template help |
| D2C brand, 10–50 people | Per-message economics at volume | Published markup, Flows depth, e-commerce integrations |
| BFSI, healthcare, regulated | Data handling and auditability | Residency answers, retention controls, inbox access logs |
| Dev-led product team | API surface and platform rate limits | Raw webhook payloads, documented limits, no lock-in |
| Agency reselling | Multi-account management and margin | Sub-accounts, white-label, transparent wholesale markup |
One factor is badly under-priced right now. Service messages have been free since 1 November 2024, and utility templates inside an open 24-hour Customer Service Window free since the July 2025 change. Meta resumes charging for both on 1 October 2026. A bot holding long threads inside that window costs nothing today and a real number in Q4, so ask every vendor how their automation behaves after 1 October — testing a denser, Flow-led design during a 7-day free trial beats modelling it.
What switching actually costs
Nobody quotes you this, so here is the honest version. Changing provider is not changing your WhatsApp presence — the number and the reputation are yours.
What you keep. Phone number and display name, quality rating, approved templates, your WABA, Official Business Account status, and your messaging limit tier. Meta's migration documentation confirms these persist across a hosting migration; switching BSP is lighter still.
What you rebuild. Chatbot and automation logic, because every builder is proprietary. Flow definitions, unless you exported the JSON. Saved replies, tags and agent rules. Conversation history beyond whatever export you are granted. Dashboards built on the old schema. And webhook integrations, if the old provider transformed Meta's payloads into its own shape — the real switching cost for engineering-heavy accounts.
How long. Four to six weeks for a mid-sized account: one to two weeks of parallel setup and template re-registration, a week of dual-running on a small traffic share, cutover, then two weeks of stabilisation. Compress it and you meet your edge cases in production.
The arithmetic, worked
Take a hypothetical D2C home-goods brand in Bengaluru sending 200,000 messages a month. The figures are illustrative and attributed to no vendor; substitute your own quotes.
Provider A quotes ₹6,000 a month plus 3 paise per message. Provider B quotes ₹15,000 plus 9 paise. Meta's rates are identical for both, so they cancel out.
- Provider A: ₹6,000 + (200,000 × ₹0.03) = ₹12,000 a month, ₹1,44,000 a year.
- Provider B: ₹15,000 + (200,000 × ₹0.09) = ₹33,000 a month, ₹3,96,000 a year.
The gap is ₹2,52,000 a year on identical delivery, and 71% of it comes from markup rather than the headline fee — which is why markup gets discussed last. At 500,000 messages the fee difference stays at ₹9,000 while the markup difference grows to ₹30,000 a month. Markup scales with you; platform fees do not. Against a gap that size a six-week migration is cheap; against ₹20,000 a year it is not.
Five questions to ask on a sales call
These are the ones that produce silence. Note who answers cleanly, then put the answers in the contract.
- "What is your markup in paise, per category, before any discount?" Marketing, utility, authentication and service, itemised. If you get a per-conversation figure, note that Meta deprecated conversation pricing after 1 July 2025 and ask again.
- "Whose Meta business portfolio will my WABA sit in, and can you show me after go-live?" You want the WABA in a portfolio you control, with the provider attached as Solution Provider. Ask what happens if you cancel.
- "If I leave in 18 months, what exactly do you export and how long does it take?" Ask for the export format, whether Flow JSON is retrievable, and the notice period. A vendor never asked this improvises; listen for it.
- "My number goes RED at 9pm IST on a Saturday during a festive campaign. Walk me through the next 30 minutes." You are testing for a human, a runbook and an alert rather than a ticket queue.
- "What share of my messages would bill as marketing versus utility, and where do I see that split?" Without category-level reporting, auto-recategorisation from utility to marketing — running since 1 July 2024, with no advance notice for repeat offenders since 16 April 2025 — reaches your invoice before anyone notices.
What most teams get wrong when choosing a provider
They compare features instead of failure modes. Every platform has broadcasts, an inbox and a bot builder. None of that predicts what happens when a template is rejected at 11pm before a sale, or 40,000 sends throttle mid-campaign. Ask about the bad days.
They treat the green tick as a provider capability. No provider can guarantee an Official Business Account badge. Meta requires 30 days on the platform, business verification, two-step verification, an approved display name, and evidence the brand is notable and frequently searched — judged largely on coverage in sizable-audience news publications, where paid placements do not count. InfiQ's green tick verification guide covers the rest.
They believe switching resets a damaged reputation. It does not. Limits and quality ratings attach to your portfolio and number, so a business on the 250 tier with a YELLOW rating arrives on the 250 tier with a YELLOW rating. Fix the sending behaviour first, per the messaging limits and tiers guide.
They assume the platform handles consent. No platform can manufacture a lawful basis for messaging someone. Opt-in capture, purpose limitation and a working opt-out are yours to design, as the opt-in and DPDP guide covers. Consult your own counsel, not a vendor's compliance page.
Get started with InfiQ
If you have run the ten points and InfiQ is on your shortlist, settle it on your own numbers rather than in a demo: submit real templates, run a broadcast against your tier, replace one question sequence with a Flow. If you picked someone else, the checklist still did its job.
Ready to compare WhatsApp Business API providers on your own volumes instead of a features page? Start your 7-day free trial — InfiQ gets you live on the official WhatsApp Business API in about 2 hours, with a shared team inbox and InfiQ Flows. Or book a walkthrough to get the ten questions answered on your own use case first.
