WhatsApp Business API providers: Meta, Twilio or 360dialog?

In 60 seconds: With an internal development team able to maintain the integration, evaluate direct Meta Cloud API. If you already operate SMS or voice on Twilio, compare the cost of reusing that foundation. For a WhatsApp-only operation with substantial traffic, include 360dialog and its per-number subscription in your calculation. If your team needs a ready-made inbox, also compare respond.io, Wati and the inbox features of the specific plan. Your message mix, incident ownership and ability to regain control of the number determine the choice.

Verified on October 17, 2026. Every row links official sources consulted on this date. “Verify” flags an unconfirmed detail; a commercial claim is not a successful test in your account.

This guide is part of our comparisons for choosing tools and integrations.

Verdict by team profile

This is our operational assessment of the published conditions, rather than a universal provider ranking.

SME profile	Route I would evaluate first	Condition for choosing it
Internal development team	Direct Meta Cloud API	Someone owns credentials, incoming events, errors and maintenance.
Business already using Twilio for SMS or voice	Twilio	Reusing code, monitoring and support offsets its per-message fee.
High volume, WhatsApp only	360dialog versus direct Meta	Actual traffic justifies the per-number subscription and contracted support.
Team seeking a ready-made inbox	A solution with an inbox	Assignment, human takeover, permissions and CRM connectivity pass a test on the selected plan.

An API transports messages. Your agent still needs case state, rules governing actions and a person to handle exceptions. Define that architecture before comparing discounts.

Comparison: costs, access and exit

The verification date above applies to the whole table. Number control and exit checkpoints are conditions to request when contracting, rather than guarantees of immediate portability.

Fixed criterion	Direct Meta Cloud API	Twilio	360dialog	Official source for this row
Provider subscription	No intermediary; separate platform fee: verify.	Usage-based model; budget separately for the number and additional services.	Regular: EUR 49; Premium: EUR 99; Scale: EUR 500 per number per month, plus Meta.	Meta pricing, Twilio pricing, 360dialog plans
Markup on Meta	No intermediary BSP markup.	USD 0.005 per inbound or outbound message, plus Meta.	States that Meta rates are passed through without markup.	Twilio message fee, 360dialog no-markup model
Onboarding and verification	Requires a Meta business portfolio, WABA and business phone number.	Self Sign-up; Meta requirements still apply.	Hub onboarding; confirm requirements for your account.	Meta official collection, Twilio signup, 360dialog keys after onboarding
Templates	Validate category and approval with Meta.	Validate template states in the integration; migration may require renewed approval.	Management through API, Hub or WhatsApp Manager; Meta approval.	Meta categories, Twilio template migration, 360dialog templates
Support	Contractual SLA for this case: unconfirmed; verify.	Scope and SLA: verify the contracted support plan.	Regular advertises 24/7 human support; confirm contractual SLA.	Meta support, Twilio support, 360dialog support by plan
Number ownership and control	Require business access to the portfolio, WABA and number.	Can register your own number; also review its telecom contract.	Require business control and check partner permissions.	Meta required assets, Twilio registration, 360dialog partner access
Ease of switching provider	Verify destination requirements and plan the integration change.	Migration into Twilio is documented; confirm exit separately.	Migrations documented; confirm source and destination conditions.	Twilio migration requirements, 360dialog migrations
MCP status	Official server for this use case: unconfirmed; verify.	Documentation MCP in public beta; does not execute calls.	Premium advertises Messaging MCP; verify availability and scope.	Meta official API, Twilio MCP, 360dialog Premium
Authentication	Bearer token; user or system user.	API uses HTTP Basic with credentials; separate keys by service.	API key per number; check who can regenerate it.	Meta tokens, Twilio authentication, 360dialog keys
Permissions	whatsapp_business_messaging and whatsapp_business_management, depending on the operation.	Check key permissions and accessible assets.	Key management depends on payment setup and partner access.	Meta permissions, Twilio keys, 360dialog permissions
Where processing and data live	Cloud API hosted by Meta; your backend stores the state you design.	Adds Twilio processing; verify residency and retention.	Adds the 360dialog layer; verify residency and retention.	Meta hosting, Twilio API, 360dialog API
Integrations	Connect your backend and CRM through development.	Programmable Messaging; validate the adapter to your CRM.	Lists Zapier, Make and n8n integrations.	Meta integration, Twilio messaging, 360dialog integrations
Limits and LATAM support	Verify account limits, data region and support channel.	Verify effective limits, support language and coverage.	Verify plan capacity, support language and regional coverage.	Meta documentation, Twilio support, 360dialog plans

Twilio dates its rates to September 2026. It also publishes USD 0.001 per message ending in Failed and charges separately for add-ons. Source: Twilio.

We do not assert that direct Meta has a zero platform fee: we could not confirm that point on developers.facebook.com during this review. Its commercial pricing page publishes the market-and-category model. Do not budget for free service messages either: that page and Twilio’s calculator show different conditions. Verify the effective rate for your account before approving a budget.

MCP also needs a tested integration. The Twilio MCP reviewed here searches documentation and schemas without authentication; it does not send messages. For 360dialog, request a demonstration of the MCP advertised in Premium and confirm the tools, authentication and permissions available to your account.

Channel authentication also does not demonstrate that an agent respects each CRM user’s permissions. Require a test with two profiles: each can access only its own records and authorized actions. Enforce that validation in the tools accessing the system of record.

If you need an inbox, compare the whole plan

respond.io lists Starter, Growth, Advanced and Enterprise. With annual billing, it displays USD 79, 159 and 279 per month respectively; Enterprise requires a quote. Starter includes inboxes; Growth adds automation and an API. WhatsApp charges require a separate check. Verified on October 17, 2026.

Wati lists Growth, Pro and Business, with additional message charges. The base subscription did not appear in the version consulted: not published in that view / verify currency, region and billing term. Check the plan’s API and webhook access before contracting it for an agent. Verified on October 17, 2026.

These are routes to evaluate for an operation where people handle conversations. Test an actual transfer: the agent stops responding, the person sees the authorized context and the conditions for resuming automation are clear. If the CRM holds the case, check that the inbox does not create a separate state that is difficult to reconcile.

Calculate cost using your actual volume

Export a representative period from your operation without personal data. Separate numbers, destination countries, categories, inbound and outbound messages, delivery states and windows that affect charging. Do not substitute “conversations” for billable message counts.

Meta cost = sum of billable messages × applicable rate
            by country, category, tier and charging condition

Total cost = Meta + provider subscription + usage fees
             + number + inbox and add-ons + taxes
             + infrastructure + maintenance + supervision

For Twilio, add USD 0.005 × (inbound + outbound messages subject to its fee) and applicable failed-message or add-on charges. For 360dialog, add the plan subscription for each number; confirm any partner conditions. For direct Meta, verify outstanding charges and include your own technical operation. Keep quotes in their original currency and record the exchange rate when comparing EUR and USD.

To decide, calculate the difference between one route’s fixed cost and another’s variable fee using the same traffic and service level. Include maintenance hours at your internal cost. A break-even point based only on messages can change once you include support, an inbox or additional numbers.

Criteria before signing

1. Operational owner. Identify who receives failed events, reviews deliveries and can stop sends. Get support scope and exclusions in writing.
2. Business control. Document who administers the portfolio, WABA, number, billing and credentials. Verify that the business can recover access without depending on a provider employee’s personal account.
3. Testable exit. Request migration requirements, costs and coordination in both directions. The number, history and automations are separate pieces; do not assume they move together.
4. Testing before production. Use fictional data, authorized test destinations and tools with no effects on customers. Review messages, duplicates, errors and human takeover before connecting the real CRM. Follow the protocol to test a WhatsApp AI agent before production.

If you separate audiences or owners, review one WhatsApp number per business line. To separate the channel from commercial memory, see the CRM as source of truth and WhatsApp as the channel.

When to choose none of them

If the process runs between employees and only needs approval inside their existing work system, a WhatsApp API may add another channel to maintain. If a request is better served by a form or email follow-up, validate that journey first. Start with what to automate first in a business and define where the result should be recorded.

If you need an external channel but WhatsApp is not a requirement, review WhatsApp, Telegram or web chat for your sales agent before contracting a provider.

It also makes sense to postpone connection when nobody handles exceptions, you cannot establish control of the number or you lack permission to access the required data. Resolving those conditions makes the provider comparison useful.

To review your case, tell us which process and systems you need to connect. We can start with your current workflow, available access and the test criteria you will use to accept the integration.