Twilio WhatsApp Alternatives (2026): What Twilio Really Costs, and When a Flat-Fee Inbox Is Cheaper
Twilio is an excellent developer platform with a per-message price. Here is that price worked through at three US volumes, the alternatives in each category, and an honest list of who should not switch.
Short answer: Twilio has no monthly fee for WhatsApp but charges $0.005 per message, inbound or outbound, plus $0.001 per failed message, on top of Meta's own fees. For US traffic that matters more than it looks: Meta charges just $0.0034 per utility, authentication or service message to a US number, so Twilio's own fee is about 1.5 times Meta's (our arithmetic). At 10,000 messages a month that is $50 to Twilio before Meta; at 50,000 it is $250. The alternatives fall into three groups: other per-message APIs (Bird $0.005 outbound only, Gupshup $0.001), flat-fee team inboxes that add nothing per message (QuickWA from $5/month, 0% markup, no per-seat fees), and help-desk add-ons (Zendesk, HubSpot, Freshchat). If your engineers have built on Twilio's APIs or you need WhatsApp, SMS and voice from one vendor, staying may be the right call. We make QuickWA; every competitor price links to that company's own page, checked 26 October 2026.
How Twilio charges for WhatsApp
Twilio's WhatsApp pricing page, checked on 26 October 2026, sets out three parts:
- Twilio's fee: "$0.005, inbound or outbound" — every WhatsApp message in either direction.
- A failed-message fee: "$0.001 per message will be applied only to messages that terminate in a 'Failed' status."
- Meta's fee: the per-template charge, which "Twilio passes through to customers," varying by category.
There is no monthly platform fee. What you get is an API: Twilio describes "reliable, scalable, programmable APIs," positions itself as "a single vendor and API for WhatsApp, SMS, RCS, Voice, Email," and refers to integrations with its Flex product. What you do not get out of the box is a shared inbox where a team reads and answers chats — you build that, or connect another product.
That model is a strength for software teams. It is a cost for a business that just wants five people answering WhatsApp, because every customer message they receive is billed by Twilio too.
Why the per-message fee weighs more in the US
Two US facts change the math.
First, Meta's US rates are low. On Meta's North America USD rate card, effective 1 October 2026, utility, authentication and service messages cost $0.0034 each, and the first 1,000 service messages per business number each month are free. Customer messages are free from Meta. A platform fee of $0.005 per message — charged on inbound as well — is therefore larger than Meta's own charge on most US traffic.
Second, US WhatsApp traffic is now mostly service and utility. Meta's documentation states that "Starting April 1, 2025, Meta does not deliver marketing messages sent to WhatsApp users in the United States," with error 131049, across every Business Messaging API — Twilio's included. The $0.025 marketing rate no longer applies to US numbers. What remains is replies, order and appointment updates, one-time passcodes and conversations started from Click-to-WhatsApp ads — exactly the low-cost categories where a per-message platform fee stands out. (If you ran US promotional WhatsApp campaigns through any provider, they stopped being delivered on that date; our guide to marketing messages and US numbers explains what still works.)
The cost at 1,000, 10,000 and 50,000 messages
To compare fairly we need one traffic pattern. Ours, for a typical US service business: half the messages are inbound (customers writing to you); of the outbound half, 40% are utility templates (confirmations, reminders, shipping updates) and 60% are service replies inside the 24-hour window. No marketing to US numbers, because it is not delivered. All figures are monthly and our arithmetic.
| Monthly messages (in + out) | Inbound (free from Meta) | Utility templates | Service replies | Meta's charge |
|---|---|---|---|---|
| 1,000 | 500 | 200 × $0.0034 = $0.68 | 300 — inside the free 1,000 = $0 | $0.68 |
| 10,000 | 5,000 | 2,000 × $0.0034 = $6.80 | 3,000 − 1,000 free = 2,000 × $0.0034 = $6.80 | $13.60 |
| 50,000 | 25,000 | 10,000 × $0.0034 = $34.00 | 15,000 − 1,000 free = 14,000 × $0.0034 = $47.60 | $81.60 |
Meta's charge is the same whichever provider you use. Now add each per-message provider's own fee, as published on its pricing page:
| Provider and its fee | 1,000 messages | 10,000 messages | 50,000 messages |
|---|---|---|---|
| Twilio — $0.005 per message in or out | $5.00 fee · $5.68 with Meta | $50.00 fee · $63.60 with Meta | $250.00 fee · $331.60 with Meta |
| Bird — $0.0050 per outbound message (inbound free) | $2.50 · $3.18 | $25.00 · $38.60 | $125.00 · $206.60 |
| Gupshup — $0.001 per message, template and session, incoming included | $1.00 · $1.68 | $10.00 · $23.60 | $50.00 · $131.60 |
| Flat-fee inbox with 0% markup (e.g. QuickWA) | plan fee + $0.68 | plan fee + $13.60 | plan fee + $81.60 |
Twilio's failed-message fee is left out because it depends on your list quality. Three things stand out:
- At low volume, Twilio is cheap. At 1,000 messages a month its total is under $6. If you only send a few hundred passcodes, a per-message API is hard to beat.
- Twilio's line grows fastest because it charges inbound too. Every "thanks!" a customer sends costs half a cent. Bird charges outbound only, so the same traffic costs half as much in Bird fees.
- In this pattern, Twilio's own fee is the bigger part of the bill at every volume — about 3.7 times Meta's charge at 10,000 messages ($50 vs $13.60) and 3.1 times at 50,000 ($250 vs $81.60).
A flat-fee inbox adds no per-message platform charge. The honest caveat: plans have message limits, so a busier team may need a bigger plan. QuickWA shows every plan's limits after sign-up and starts from $5/month; we do not claim that the starting plan covers 50,000 messages. The point is structural — on a flat plan, a busy week does not create a bigger platform invoice.
The alternatives, by type
1. Flat-fee team inboxes
For businesses whose WhatsApp is people answering customers. Prices from each provider's own page on 26 October 2026:
| Provider | Starting price (as shown) | Seats | Meta's fees |
|---|---|---|---|
| QuickWA | from $5/month, monthly or yearly | No per-seat fees | Billed by Meta to you, 0% markup |
| ChatMaxima | Starter $19/month (or $99 billed yearly); 10,000-message monthly allowance, +$10 per extra 10,000 | 3; extra $6/month | Not stated on pricing page |
| Zoko | Starter $49.99/month plus usage fees | Agents free on Starter | Paid to Meta directly; Zoko lists a $0.015 per-conversation markup on Starter |
| SleekFlow | Essential US$49/month billed yearly | 3; extra US$15/seat | Per SleekFlow rate card; number hosting listed at US$15/month |
| respond.io | Starter $79/month billed yearly; $99 monthly | 5; extra $12/user | Not included in the subscription; you top up WhatsApp credit |
Zoko is the one to read closely if you are leaving Twilio to save on per-message fees: on Starter its published conversation markup ($0.015) is higher per unit than Twilio's message fee, though it applies per conversation rather than per message; on its Max plan there is no markup.
2. Other per-message APIs
For engineering teams that want to keep an API-first setup but pay less per message. Gupshup charges $0.001 per message with Meta "billed at actuals" and markup listed as "NA." Bird charges $0.0050 per outbound message with inbound free, and shows the totals per category on its page. 360dialog takes a different shape — €49 per number per month on Regular, "+Meta WhatsApp Messaging Fees," and "no markup on Meta fees" — so its cost does not grow with volume at all. Each is still an API: you build or buy the screen your team works in.
3. Help-desk and CRM add-ons
If your support team already lives in a help desk, adding WhatsApp there may beat any standalone tool. Zendesk Suite Team is $55 per agent per month paid yearly ($69 monthly), with "Additional fees apply" for WhatsApp. HubSpot puts WhatsApp on Service Hub Professional at $90 per seat per month annually ($100 monthly) plus a $1,500 onboarding fee. Freshchat includes WhatsApp from Growth at $19 per agent per month billed annually. For five agents that is $275, $450 and $95 a month respectively before Meta (our arithmetic).
The full US provider comparison covers fifteen platforms side by side.
Who should stay on Twilio
Switching has a cost, and for some teams Twilio is plainly the better tool:
- You have engineering time invested in Twilio's APIs. If your order system, login flow or contact center already calls Twilio, rewriting it to save $40 a month is rarely worth it.
- You need several channels from one vendor. Twilio offers WhatsApp, SMS, RCS, voice and email from one vendor and API. In the US, where promotions still go by SMS while WhatsApp marketing is paused, that matters.
- You verify users across channels. Twilio says it can handle "verifying users over WhatsApp, SMS, RCS, voice, email, push, and OTPs" — useful if a passcode must fall back to another channel.
- Your volume is low and machine-sent. A few hundred passcodes or receipts a month cost a few dollars on Twilio; a flat plan would not save much.
- You run a contact center on Twilio Flex, which Twilio's own page lists among its integrations.
Who usually saves by switching
- Teams that reply by hand. If WhatsApp at your business means people answering customers, you need an inbox anyway — and on Twilio every inbound message is billed.
- Businesses sending thousands of messages a month, where Twilio's fee reaches tens of dollars — $50 at 10,000 messages in our scenario, against $13.60 to Meta.
- Anyone who built a custom inbox on top of Twilio and now maintains it. A ready-made inbox with assignment, notes, chatbots, AI replies and Shopify updates replaces that code.
- Bilingual US businesses. QuickWA's AI replies in the customer's language, so English and Spanish chats run in one inbox.
How to switch without losing anything
- Export your history first. Your past chats live in your current provider's logs, not in WhatsApp. Download what you need before you leave.
- List your approved templates — name, category, language and text — so you can re-create any that do not carry over.
- Ask both providers, in writing, how your number moves. Meta's own migration documentation notes that its rules differ under its newer WhatsApp account model, so get a specific answer for your account rather than relying on a general guide.
- Decide on the number. Keep your current US number, or start fresh. In QuickWA you can also buy a USA number inside the app and read its incoming SMS — such as Meta's verification code — in an SMS inbox; one is included on eligible paid plans while subscribed. Meta still decides whether any number can register. See choosing a US number for WhatsApp Business.
- Point your systems at the new API. QuickWA has a developer API with signed webhooks, documented at quickwa.com/docs, plus Shopify, WooCommerce, HubSpot, Zoho, Zapier and Stripe integrations.
- Run both for a week on low-risk traffic, then cut over.
Consent records come with you only if you keep them. US law on WhatsApp under the TCPA is unsettled, so keep SMS-level opt-in evidence for every contact. This is not legal advice.
For the US-specific setup, see the QuickWA US page and our US pricing guide.
Sources
- Twilio, WhatsApp pricing ($0.005 per message inbound or outbound, $0.001 per failed message, Meta fees passed through): twilio.com (checked 26 Oct 2026)
- Twilio, WhatsApp product page (single vendor for WhatsApp, SMS, RCS, voice and email; verification; Flex integrations): twilio.com (checked 26 Oct 2026)
- Meta, WhatsApp Business Platform pricing and North America USD rate card (effective 1 Oct 2026): developers.facebook.com (checked 26 Oct 2026)
- Meta, marketing messages — US delivery restriction and error 131049: developers.facebook.com (checked 26 Oct 2026)
- Meta, migrating phone numbers among solution partners: developers.facebook.com (checked 26 Oct 2026)
- Pricing pages, all checked 26 Oct 2026: Bird, Gupshup, 360dialog, ChatMaxima, Zoko, SleekFlow, respond.io, Zendesk, HubSpot Service Hub, Freshchat
Frequently asked questions
How much does Twilio charge for WhatsApp messages? +
Twilio's pricing page lists $0.005 per WhatsApp message, inbound or outbound, plus $0.001 per message that ends in a failed status. Meta's own per-message fees are passed through on top. There is no monthly platform fee.
What is the cheapest alternative to Twilio for WhatsApp? +
It depends on how you use WhatsApp. Among per-message APIs, Gupshup lists $0.001 per message. Among flat-fee team inboxes, QuickWA starts from $5/month with no per-seat fees and 0% markup on Meta's fees, so it adds nothing per message. At very low, machine-sent volumes Twilio itself is inexpensive.
Is Twilio more expensive than Meta's own WhatsApp fees in the US? +
On most US traffic, yes. Meta charges $0.0034 per utility, authentication or service message to a US number and nothing for messages customers send, while Twilio charges $0.005 on every message in or out — about 1.5 times Meta's utility rate (our arithmetic).
Can I send WhatsApp marketing to US customers through Twilio or any alternative? +
No. Since 1 April 2025 Meta has not delivered marketing templates to WhatsApp users in the United States, across all its Business Messaging APIs; sends fail with error 131049. Utility, authentication and service messages, and Click-to-WhatsApp ad conversations, still work.
Should I leave Twilio if my developers built on it? +
Not necessarily. If your systems already call Twilio, or you need WhatsApp, SMS, voice and email from one vendor, staying is often sensible. Switching usually pays off for teams that answer chats by hand or send thousands of messages a month.
Can I keep my US number when moving away from Twilio? +
Often, but ask both providers in writing how your specific number and templates move, because Meta's migration rules differ by account model. Export your chat history before you leave, since it lives in your old provider's logs.