Twilio or ZapClaw for WhatsApp: which one keeps my number in the WhatsApp Business app, and what does each cost?

In short: both run on Meta's official WhatsApp Business Platform, but they treat a number that is already in the WhatsApp Business app differently. Twilio's own migration guide has you delete the WhatsApp account before the number moves to Twilio; ZapClaw connects it through Coexistence, and the number keeps working in the app. Twilio charges US$ 0.005 per message, sent or received, plus Meta's fees; ZapClaw charges per account, with 20,000 messages a month and unlimited numbers on the Business plan, and Meta bills its fees to you directly.

How each one connects a number

Twilio sends and receives WhatsApp messages through Meta's WhatsApp Business Platform and its own Programmable Messaging API. To register a number as a WhatsApp sender, its Self Sign-up guide asks for an upgraded (paid) Twilio account, administrator access to a Meta Business Portfolio and a number that is not already registered with WhatsApp. It can be a Twilio phone number or your own.

A number that already runs in the WhatsApp Business app has to leave it first. Twilio's migration guide starts by deleting the WhatsApp account, and warns that you will not be able to keep using WhatsApp or the WhatsApp Business app with that number. Twilio's documentation we checked does not mention Coexistence.

ZapClaw, a Meta Tech Provider, connects your number to Meta's official WhatsApp Cloud API through Embedded Signup with Coexistence, so the number keeps working in the WhatsApp Business app. Meta's documentation says the business can still send one-to-one messages from the app, with the chat history in sync. Messages reach your webhook and you send through a REST API. ZapClaw does WhatsApp only.

Side by side

Twilio's prices are in US dollars, as its pricing page shows them, and that page says they are current as of September 2026. ZapClaw's prices follow where you are: reais in Brazil, US dollars elsewhere. “Not covered here” marks a point this page did not check.

What you pay

Twilio's WhatsApp price list, as published on its pricing page:

• Twilio's fee: US$ 0.005 per message, inbound or outbound. Meta's fees come on top, and Twilio passes them through.
• Failed messages: a processing fee of US$ 0.001 per message that ends with the status Failed.
• Messaging Engagement Suite, optional (link shortening, click tracking, scheduling): US$ 0.015 per message, the first 1,000 each month free.
• Testing: a free trial with no card, and trial accounts include 100 WhatsApp messages. The Sandbox is for testing only: it uses a shared number, and a session expires three days after you join it.

ZapClaw's price list, the same whatever the number of numbers:

• Free: US$ 0, 500 messages a month, 1 number, no card.
• Business: US$ 29 a month, or US$ 276 paid once a year. 20,000 messages a month and unlimited numbers; extra messages from US$ 0.90 down to US$ 0.55 per 1,000.
• Agency: US$ 49 a month, or US$ 468 paid once a year. 3 clients and 60,000 messages a month, unlimited numbers; extra messages US$ 0.50 per 1,000, extra clients from US$ 10 each.

What counts. Both prices count received messages. Twilio's fee applies inbound or outbound; ZapClaw counts each message sent through the API, the dashboard or Chatwoot and each real message received, while delivery and read confirmations, messages typed on the phone, imported history, webhook redeliveries and sends Meta does not accept are not counted.

Low volume. Twilio's fee grows with each message, so a small volume can cost less there: 5,000 messages a month come to US$ 25 in Twilio fees, plus failed messages and Meta's fees. ZapClaw's free plan covers 500 messages a month on one number, and Business costs US$ 29.

20,000 messages a month. Twilio's fee comes to US$ 100, plus US$ 0.001 per failed message. ZapClaw Business includes them in its US$ 29, on as many numbers as you connect. On both, Meta's fees come on top.

50,000 messages a month. Twilio's fee comes to US$ 250, plus failed messages. On ZapClaw Business it is US$ 29 plus US$ 27 for the 30,000 extra messages, drawn from a prepaid balance. On both, Meta's fees come on top.

Meta's fees are the same on both. Meta charges per delivered message, by market and category, as its pricing page sets out. Since 1 October 2026 that includes service replies past the first 1,000 a month per number. Twilio passes those fees through; on ZapClaw, Meta bills you directly and ZapClaw never marks them up. For the same messages sent through the API, what differs is Twilio's fee per message against ZapClaw's plan. Under Coexistence, replies typed in the WhatsApp Business app stay free.

When Twilio is the better choice

• You want one vendor and one API for SMS, MMS and WhatsApp. Twilio's Programmable Messaging API sends all three, and its WhatsApp docs point to Conversations for two-way messaging across WhatsApp, SMS and chat, and to Verify for one-time passcodes over WhatsApp, SMS and other channels. ZapClaw does WhatsApp only.
• You are putting a new, dedicated number on WhatsApp. Twilio's Self Sign-up is built for a number that is not on WhatsApp yet, and it can be a Twilio phone number. ZapClaw only connects a number that runs in the WhatsApp Business app, and Meta may refuse one with little recent activity there (the requirements).
• Your volume is low. At a few thousand messages a month, Twilio's fee per message can cost less than ZapClaw's Business plan (see the worked examples above).
• Your team already builds on Twilio. Its WhatsApp docs cover the Programmable Messaging and Conversations APIs, a Content API for rich messages and Studio, Twilio's no-code and low-code builder, so WhatsApp fits the tools you already use.

ZapClaw also does not fit bulk broadcasting, more than 20 messages per second, groups, voice or video calls, or the Official Business Account blue checkmark. None of that is supported under Coexistence, and the limitation is Meta's. This page did not check how Twilio handles those points.

When ZapClaw is the better choice

• The number already runs in the WhatsApp Business app, and you want it to stay there. ZapClaw connects it through Coexistence, so your team keeps answering on the phone while your system uses the API. Twilio's migration guide has you delete the WhatsApp account first.
• You move a steady volume. ZapClaw charges per account, not per message: Business includes 20,000 messages a month, sent and received together, and the extra is priced in brackets that get cheaper as you grow.
• You connect several numbers, or your clients' numbers. The paid plans have unlimited numbers for one base price, and the Agency plan keeps each client's numbers, messages, contacts, templates, API keys and webhook URL apart, with no Meta app of your own and no App Review. Twilio's docs ask software vendors that onboard customers to join Meta's Tech Provider program, which takes business verification and App Review.
• Your system runs on a webhook. ZapClaw signs every delivery with HMAC-SHA256, tries it up to 3 times (right away, 30 seconds later, then 120 seconds after that) and keeps every event so you can replay it after an outage.
• You run Chatwoot self-hosted. Its native WhatsApp Cloud channel connects to ZapClaw with no Meta app of your own, and the number stays in the WhatsApp Business app. In Chatwoot's own guide, the row “Keep using the WhatsApp Business app on your phone” is marked no for the Twilio channel, and Quick setup with Meta on a self-hosted install needs the installation's own Meta app.
• You want to try before paying. The free plan has 500 messages a month on one number, asks for no card and has no end date.

Moving from Twilio to ZapClaw

Your customers keep writing to the same number. What changes:

• A number registered as a Twilio WhatsApp sender works on the API only, outside the WhatsApp Business app. ZapClaw connects through Coexistence, so the number goes back to the app first: ask Twilio to release it from the API (Meta calls this deregistering), register it in the WhatsApp Business app, version 2.24.17 or newer, and use it normally for a while, because Meta may refuse a number with little recent activity. The steps are in moving a number from another provider.
• A number you never moved to Twilio, because you only tried the Sandbox's shared number, connects to ZapClaw directly (all the requirements). When it connects, Meta unlinks every companion device from the account, and supported ones can be linked again.
• Your code. ZapClaw's webhook payload is not Twilio's, so your code reads different fields: see the webhook format. You send through ZapClaw's REST API with the X-API-Key header.
• Chatwoot. A self-hosted Chatwoot connects through its native WhatsApp Cloud channel instead of the Twilio channel: see how.

Questions

Does Twilio use Meta's official WhatsApp API?

Yes. Twilio's WhatsApp docs describe sending and receiving messages through Meta's WhatsApp Business Platform with Twilio's APIs, and its Self Sign-up registers each number as a sender in a WhatsApp Business Account. ZapClaw runs on the same platform, through Meta's Cloud API. The difference between the two is not official against unofficial: it is whether the number can stay in the WhatsApp Business app, and how each one charges.

Can I keep my WhatsApp Business app number on Twilio?

Not according to Twilio's own docs. Its migration guide says that to bring a number from WhatsApp or the WhatsApp Business app you first delete the WhatsApp account, and warns that you “won't be able to continue using WhatsApp or WhatsApp Business App” with it; its Self Sign-up guide gives the same instruction. Twilio's documentation we checked does not mention Coexistence (checked on 14 October 2026). On ZapClaw the number connects through Coexistence and keeps working in the app, with WhatsApp Business 2.24.17 or newer.

How do the prices compare for 20,000 messages a month?

On one number, counting sent and received messages: Twilio's fee is 20,000 × US$ 0.005, which is US$ 100, plus US$ 0.001 per failed message. ZapClaw Business costs US$ 29 a month with those 20,000 messages included, on any number of numbers. At 50,000 messages, Twilio's fee is US$ 250, plus failed messages, and ZapClaw Business is US$ 29 plus US$ 27 of extra messages. Meta's fees are the same on both for the same messages: Twilio passes them through, and on ZapClaw Meta bills you directly.

Do I need my own Meta app?

No, on either. Twilio's Self Sign-up asks for an upgraded Twilio account and administrator access to a Meta Business Portfolio, with Meta's business verification before production if the portfolio is new. Software vendors that onboard their own customers on Twilio must join Meta's Tech Provider program. ZapClaw is a Tech Provider, which Meta requires of whoever connects a number through Coexistence: you connect in Meta's Embedded Signup window, with no Meta app of your own and no App Review.

Can a number on the official API still be banned?

Yes. Meta can restrict or disable an account that breaks WhatsApp's policies, on Twilio, on ZapClaw or with any other provider. ZapClaw forwards those notices from Meta to your webhook as account events.

Sources

Checked on 14 October 2026. Prices, versions and features change, so check each source before you decide.

• Twilio, WhatsApp pricing (fee per message, failed messages, free trial, Messaging Engagement Suite): twilio.com/en-us/whatsapp/pricing
• Twilio docs, registering WhatsApp senders with Self Sign-up: twilio.com/docs/whatsapp/self-sign-up
• Twilio docs, migrating phone numbers and WhatsApp senders: twilio.com/docs/whatsapp/migrate-numbers-and-senders
• Twilio docs, the Sandbox for WhatsApp: twilio.com/docs/whatsapp/sandbox
• Twilio docs, the WhatsApp overview, and the documentation index we searched for Coexistence: twilio.com/docs/whatsapp and twilio.com/docs/llms.txt
• Twilio docs, the Tech Provider program for software vendors: twilio.com/docs/whatsapp/isv/tech-provider-program
• Chatwoot, how to set up a WhatsApp channel: chatwoot.com/hc/user-guide/articles/1677832735-how-to-setup-a-whats_app-channel
• Meta, onboarding WhatsApp Business app users (Coexistence and linked devices): developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/onboarding-business-app-users
• Meta, WhatsApp pricing and rate cards: developers.facebook.com/documentation/business-messaging/whatsapp/pricing
• Meta, getting started as a Tech Provider: developers.facebook.com/documentation/business-messaging/whatsapp/solution-providers/get-started-for-tech-providers
• ZapClaw: pricing, webhooks, signature, moving a number from another provider and llms.txt

Also compare ZapClaw and Evolution API or ZapClaw and Z-API, or read how the official WhatsApp API compares with unofficial libraries.