Twilio's WhatsApp pricing page is easy to misread because the number that matters most is not the one in large type. It is $0.005. That is what Twilio adds to every WhatsApp message that touches its API, and the detail that catches almost everyone by surprise: it applies to messages you receive as well as messages you send.
That is a genuinely unusual choice. Most BSPs charge on send. Twilio charges on both directions, which means every customer reply, every "stop" and every read receipt event that flows through the API is quietly billed.
What the fee actually adds up to
Twilio is a Meta Business Solution Provider, so the bill has two layers regardless of what you do: Meta's own per-message rate, which is identical no matter which BSP you route through, and Twilio's $0.005 on top, in each direction.
Take a mid-size operation sending 5,000 marketing templates a month to Brazil, where Meta's marketing rate is $0.0625, plus 3,000 inbound replies from customers.
| Line item Calculation Cost | ||
| 5,000 marketing templates, Meta fee | 5,000 × $0.0625 | $312.50 |
| 5,000 marketing templates, Twilio fee | 5,000 × $0.005 | $25.00 |
| 3,000 inbound replies, Twilio fee | 3,000 × $0.005 | $15.00 |
| Twilio's share of this bill | $40.00 |
Forty dollars sounds tolerable next to Meta's $312.50. It stops looking tolerable at scale. At 100,000 messages a month, Twilio's markup alone clears $500, before Meta's fees are even added, purely from the flat per-message tax compounding across both directions.
There is more sitting underneath the headline rate. Twilio has charged $0.001 per failed message since September 2024, which matters if your list has any stale numbers in it. Scheduling messages requires the separate Engagement Suite add-on at $0.015 per message. And Twilio's own general fee schedule includes support minimums and compliance surcharges that apply across its product line, worth checking against your account tier specifically rather than assuming the headline rate is the whole bill.
None of this is hidden exactly. It is published. It is also easy to model from the small number on the pricing page and miss entirely until the invoice arrives.
What you are actually paying for
To be fair to Twilio: the $0.005 buys something. Mature, extensively documented SDKs across a dozen languages. One contract and one dashboard if you already run SMS or voice through Twilio, which is a real convenience for teams doing exactly that. A large support organisation and predictable enterprise contracting. If your team is already deep in the Twilio ecosystem, the markup is partly a coordination tax you are choosing to pay, and that can be a reasonable trade.
If you are on Twilio purely for WhatsApp and nothing else in your stack touches it, you are paying for infrastructure you are not using.
The alternatives, by category
A lower-markup BSP, if you need to stay official. This is the fix for the fee specifically, without touching your compliance position. 360dialog charges a flat €49 to €249 monthly platform fee with no per-message markup on top of Meta's rate at all, which crosses over as cheaper than Twilio somewhere around 10,000 messages a month and pulls further ahead above it. Gupshup runs $10 to $80 a month with a markup as low as $0.001, particularly competitive in Indian and Southeast Asian markets where Meta's own rates are also lowest. Neither of these is a different category from Twilio; both are Meta BSPs, so you keep the verified badge, templates, click-to-WhatsApp ads and audit trail. You are only changing who resells you the same underlying access. Our pricing breakdown has the full country-by-country rate card if you want to model this properly.
A session-based API, if templates and the 24-hour window were never really what you needed. This is a bigger decision than switching BSPs, because it means leaving Meta's official platform entirely. No per-message fee in either direction, no markup, no templates, flat pricing regardless of volume: $5 to $35 a month for one to ten numbers on WaHttp, similarly at WasenderAPI, higher at Whapi.Cloud if you specifically need Groups or Channels support. The trade is real: automating a standard WhatsApp account this way breaches Meta's terms of service, and you give up the verified badge, catalogs and ad integration permanently. Our comparison of the two categories covers where each one wins, and it is worth reading properly before assuming price is the only variable that matters.
Self-hosting, if your volume is large enough that even a flat fee stings. Running Baileys or WAHA yourself removes every layer of BSP or platform fee, in exchange for owning the server, the reconnection logic and the protocol maintenance. The self-hosting guide has the honest cost accounting, infrastructure plus engineering time against what you would pay a vendor.
The parts of the complaint that are not about price
Some of the frustration behind this search term is not really about $0.005. It is worth separating out, because the fixes differ.
Twilio's sandbox environment for testing expires every three days and has to be rejoined each time, which is a genuine annoyance during development that has nothing to do with the eventual production bill. Broadcast and campaign tooling is not built in, so if you want a contact list, tagging and a send-and-track workflow, you are building it yourself on top of the raw API or paying for a separate layer. Template management went through a forced migration in April 2025 that cost some teams real engineering time with no cost benefit attached. None of this is unique to Twilio among BSPs, but it is worth knowing that switching providers to save on the per-message fee will also, incidentally, hand you a different set of these frictions rather than removing the category entirely.
Picking correctly
The variable that decides this is not your total spend, it is what proportion of your spend is Twilio's markup specifically versus Meta's own fees, which no provider changes. Pull your last invoice and separate the two lines before doing anything else. If Twilio's $0.005 is a small fraction of a bill dominated by Meta's marketing rates, changing BSP saves you little and a lower-markup reseller is a quick win. If your traffic is heavy on cheap utility templates or high-volume two-way conversation where the per-message fee compounds fastest, the markup is a bigger share of the bill and worth acting on directly.
Separately, ask whether you need the official platform's constraints at all. If your WhatsApp use is internal alerts, staff notifications or conversational support rather than regulated or ad-driven marketing, you may be paying Twilio's tax, and Meta's fees, for compliance machinery your traffic never touches. That is the deeper question behind most Twilio complaints, and it is worth answering honestly rather than just chasing a lower per-message number.
Common Questions asked by Users
How much does Twilio charge for WhatsApp? $0.005 per message, applied to both inbound and outbound messages, on top of Meta's own per-message rate, which is identical across every BSP. There is also a $0.001 fee per failed message and a separate charge for the Engagement Suite scheduling add-on.
Why does Twilio charge for messages I receive? Twilio bills API usage in both directions rather than only on send. Most competing BSPs charge only on outbound messages, so this is a meaningful difference to check when comparing providers, not just their headline rate.
What is the cheapest Twilio alternative for WhatsApp? For staying on the official platform, 360dialog has no markup on Meta's fees at all, just a flat monthly platform charge, and typically undercuts Twilio above roughly 10,000 messages a month. For leaving the official platform, flat-rate session-based APIs run $5 to $35 a month regardless of volume.
Does switching BSPs change my compliance position? No. Twilio, 360dialog and Gupshup are all Meta-authorised resellers of the same Cloud API, so switching between them changes only who you pay and their markup, not your standing with Meta.
Is a session-based API a real alternative to Twilio's WhatsApp product? For conversational, internal or transactional messaging, yes, and the cost difference is substantial. For anything requiring the verified badge, click-to-WhatsApp ads or regulated audit documentation, no unofficial provider is a substitute at any price.
Will I lose my WhatsApp number if I leave Twilio? No. Meta supports moving a number between WABAs without changing what customers see, if you are moving to another official BSP. If you are moving to a session-based provider instead, the number links there via QR code and is unaffected either way.