Choose a WhatsApp Business Solution Provider by account ownership, operational fit, charging structure and a documented exit route. Compare what the provider supplies with what your business must still build or operate. Access to an API is not automatically a shared inbox, reliable handover process or portable archive of customer conversations.
360dialog’s onboarding and migration documentation and Twilio’s WhatsApp API overview illustrate different responsibilities to investigate. Their documents are evidence about those products, not a universal partner ranking or a claim that Spout holds an official provider status. Before signing, confirm the current agreement and account-specific requirements. 360dialog onboarding, Twilio WhatsApp overview.
What are you buying from a provider?
Separate platform access, messaging transport, the staff interface and any automation. A provider may supply some layers while another application supplies the inbox or chatbot. Record the owner of each layer so a customer reply cannot fall between systems.
A developer-oriented API can be suitable where the business has an application team, but that does not prove an operator-friendly inbox is included. Conversely, an inbox demonstration does not establish ownership of the business portfolio, number or underlying templates. Ask to see both the operating interface and the account assets.
Compare required functions using actual customer journeys: an incoming enquiry, a follow-up template, a failed delivery and a transfer to a staff member. Keep proposed custom development separate from features already available in the selected plan and configuration.
How do the routes compare?
| Route | Primary documentation used here | Responsibility to clarify |
|---|---|---|
| 360dialog | Embedded signup and number migration | Business ownership, partner billing route and migration path |
| Twilio | WhatsApp API and status callbacks | Application integration, message-event handling and operator interface |
| Direct platform route | A procurement alternative requiring its own current documentation | Who builds, supports and operates the missing layers |
This is a bounded comparison. It does not infer that all routes include the same inbox, migration guarantees or country availability. The direct route is identified as an option to investigate, not a fully evaluated product recommendation.
For each candidate, request the current description of included features and exclusions. Require a demonstration of the chosen workflow with the intended staff roles. A provider should not receive credit for a function that belongs to a separate product nobody has agreed to supply.
Who should own and complete onboarding?
360dialog says embedded signup uses Facebook Login and must be started and completed by the business portfolio owner or administrator. Its documentation states that third-party providers may not navigate that flow on the business’s behalf. Treat that as an ownership requirement rather than an inconvenience to work around.
The same guide lists a valid business number and business portfolio information, including legal name, address, website and contact number. It requires a live, publicly accessible HTTPS website that clearly describes the business. These requirements should be checked before planning a production messaging workflow.
Where a partner-paid account applies, the documented channel-addition route differs from the direct route. Ask who receives the provider bill and which party can add or remove numbers. Do not assume the person who receives an invoice also controls every Meta asset. 360dialog signup responsibilities.
What should charging comparisons include?
Ask each candidate to separate platform message charges from provider charges, inbox seats, automation, storage and support where applicable. Obtain a current private quotation against the intended recipient markets and message categories. This article deliberately supplies no monetary figures.
Do not compare one provider’s transport-only charge with another provider’s complete application package as if they were equivalent. Equally, an apparently simple bundled plan needs a clear explanation of which usage events it includes and which are charged elsewhere.
Keep the quotation’s assumptions with the comparison. Record whether it counts submitted messages, delivered messages, inbound traffic or other events. If official pages or sales answers conflict, leave that point unresolved until the provider identifies the applicable current terms. A spreadsheet cannot repair an uncertain charging definition.
What can be lost when moving providers?
360dialog’s migration page contains a broad introductory description but its asset table marks message/chat history and catalogues as not migrated in the listed migration column. Do not promise full conversation-history portability from the introductory wording alone.
The documentation distinguishes migration scenarios and warns that conditions vary. It also identifies restrictions involving test numbers, display names and template duplication. Duplicated templates can be rechecked and rejected. A number moving successfully does not prove that every surrounding asset and operating workflow moved with it.
Request the exact migration path for the account involved. Preserve required history through the supported export route before making changes, and establish how staff will access older conversations. Do not delete the existing app or disconnect a production number merely because a general guide mentions a possible migration step. 360dialog migration scope.
An original provider exit inventory
Complete this inventory while choosing a provider, rather than waiting until the relationship ends:
Business assets: portfolio, WhatsApp account, number, display name and authorised administrators.
Application assets: inbox configuration, routing, automation rules and integration endpoints.
Content assets: templates, languages, approval states and ownership of reusable copy.
Customer records: supported export formats, conversation history, consent records and retention constraints.
Commerce assets: catalogue ownership and product identifiers, where used.
Billing boundary: outstanding usage, provider services and final reconciliation process.
Migration evidence: exact supported path, prerequisites, exclusions and fallback if a step fails.
Acceptance result: incoming message, outbound template, delivery event and staff handover demonstrated after the move.
This inventory is an editorial procurement tool, not a guarantee that every asset is portable. Use it to expose exclusions before committing to a provider.
Twilio’s documentation describes status callbacks containing message identity, status and error information. Where delivery evidence matters, ask how the proposed application retains and displays those events to staff. Transport evidence and customer-response ownership should both be covered.
Discuss your requirements through Spout’s WhatsApp Business service or start an enquiry with the comparison and exit inventory.
Ask who can export the consent record and how its meaning is preserved. A contact list without the original permission context may not support the intended follow-up workflow after migration. Treat that as an exit requirement rather than assuming a number transfer carries every surrounding customer record.
By Spout Team. Prepared with AI-assisted drafting using the linked primary documentation.