Business Solution Provider (BSP) / Solution Partner
An approved intermediary on the WhatsApp Business Platform: a company that integrates Meta‘s API once and then resells or embeds WhatsApp messaging for downstream businesses, so those businesses don’t integrate Meta directly. The heavier of the two ways onto the platform (the lighter being a direct client SDK like wapi-go).
What the role provides
From whatsapp-solution-partner:
- Embedded (in-app) signup — a flow the partner hosts so a business customer can create and connect its own WABA in-context.
- Shared credit line — the partner establishes billing/credit with Meta and covers its customers’ messaging spend.
- Access & permissions — access tokens and the permission scopes the partner operates under.
Role split
Meta distinguishes partner types, including:
- Tech Provider — builds and operates the technical integration.
- Solution Partner — a Tech Provider with additional commercial/onboarding standing (embedded signup, credit line).
- Measurement Partner — focused on analytics/measurement.
Example
Wassenger — the WhatsApp API vendor behind the routed whatsapp-chatgpt-bot — plays exactly this BSP-class intermediary role: a business points its bot at Wassenger, and Wassenger handles the Meta-side platform mechanics.
The role is not WhatsApp-specific (added 2026-07-30)
Once the wiki held three channels, the intermediary turned out to be the constant. Every business-messaging platform interposes an approved partner between brand and API, and they differ mainly in how optional it is:
| Channel | The role | Optional? |
|---|---|---|
| whatsapp-business-platform | BSP / Solution Partner | Optional — a direct integration via a client SDK like wapi-go is supported |
| rcs-business-messaging | Messaging partner / developer, launching an agent rcs-brand-verification | Partner-mediated by construction; carriers may add their own approval |
| apple-messages-for-business | Messaging Service Provider (MSP) apple-messages-for-business-docs | Mandatory — qualifying for an account requires selecting an Apple-approved MSP |
Apple sits at the strict end: no direct path exists, so the MSP supplies the platform, the server-to-server integration and usually the agent console. WhatsApp sits at the permissive end, where the BSP is the convenient path rather than the only one.
This is why sender-verification takes the shape it does. If an intermediary is going to send on a brand’s behalf, the platform must bind that intermediary to the brand’s consent — which is exactly what RCS’s authorization email to a named brand representative does rcs-brand-verification.
Related
sender-verification · whatsapp-solution-partner · apple-messages-for-business · rcs-business-messaging · wapi-go · synthesis