Twilio
Twilio is a reseller, not a network. Every WhatsApp message it sends is still Meta’s message on Meta’s rate card — Twilio adds its own fee on top and hands you one account, one bill and one API for WhatsApp, SMS and verification codes. Whether that is worth paying for depends entirely on whether you need more than WhatsApp.
Last reviewed: 30 August 2026 · Reviewed every two weeks
Three things. WhatsApp messages — invoice sent, payment received, a reminder on an overdue account. SMS as the fallback when WhatsApp is not configured or the recipient has no WhatsApp, which matters more than it sounds for site staff and drivers. And one-time passcodes for sign-in and for confirming a sensitive change, delivered over whichever of the two channels you prefer.
Whose account it is matters, so here is the architecture. Each customer gets their own Twilio subaccount under ours — its own credentials, its own sender, and its own message log, with no customer able to reach another’s. Twilio bills the parent account as a single balance, so the usage arrives on your Consaya invoice at what it cost, itemised by the subaccount that spent it, rather than as a second bill from a company you have never contracted with. You buy nothing from Twilio and you sign nothing with Twilio.
For WhatsApp, Twilio charges USD 0.005 per message on top of Meta’s per-message fee, with no monthly platform charge. On a thousand messages a month that is five dollars — for most firms the mark-up is not the deciding factor, and the deciding factor is whether you also need SMS.
SMS and verification codes are priced separately again, by destination country and by message segment, and Twilio changes those figures without telling anybody. We deliberately do not reprint them here: a stale SMS rate on our page that you budget against is worse than no rate at all. Take those two from Twilio’s own pricing page on the day you decide.
Twilio lets a platform open a subaccount per customer — up to a thousand of them — each with its own credentials, its own sender and its own logs. Nothing about your traffic is visible from any other customer’s subaccount, and no credential of theirs can reach yours. The alternative, one shared account with everybody’s messages in one log, is how a platform ends up unable to tell you what your own messaging actually cost.
It also decides what happens when you leave. A subaccount is suspended or closed on its own, and your numbers and history go with it — rather than your messages being a subset of rows in somebody else’s account that nobody can cleanly hand back.
Use Twilio if you want WhatsApp and SMS and passcodes from one place, or if you would rather not go through Meta’s business verification yourself. Go direct to Meta if WhatsApp is all you will ever send and volume is high enough that the per-message mark-up starts to be real money — the comparison table on the integrations hub sets the two side by side.
One thing neither route changes: WhatsApp is a permissioned channel. Meta decides which template you may send, the client can block you, and a message outside an open conversation window is billed as a new one. Anyone who tells you the channel is simply cheaper than email is not describing the same thing.
The USD 0.005 figure is Twilio’s published WhatsApp fee as at the review date above, and it is theirs to change. Consaya takes no share of it and sets none of it.