Twilio has published $0.005 per WhatsApp message as its own platform fee, charged inbound and outbound on top of Meta's per-message fee, which varies by country and category. It is one line of a two-line meter, not the price of a message; re-check both lines before you budget.
Is Twilio WhatsApp pricing really $0.005 per message?
Twilio has published $0.005 per WhatsApp message as its own platform fee, charged on messages you send and messages you receive, and billed on top of Meta's per-message fee. It is one line of a two-line meter, not the total price. Re-check both lines on Twilio's live pricing page before the figure goes into a budget.
A message on this route costs Meta's fee plus Twilio's platform fee. The platform term is flat and easy to find. The Meta term is a matrix of country and message category, so this route has no single per-message price. Every second-hand summary that quotes one number is quoting half a meter.
Three properties follow, and each one changes a budget:
- Additive. Twilio's fee sits on top of Meta's. Meta's line is the country- and category-specific one, so it is the term to check first, and the term that moves.
- Symmetric. As published, the platform fee applies to inbound too. A support line that answers more than it initiates pays it on every reply it receives.
- Unbounded. There is no ceiling. Cost is a straight line from volume, forever.
The meter itself is in motion, and Twilio says so in its own headline. Twilio's Help Center carries a notice headed, verbatim, “Notice: Changes to WhatsApp's Pricing (October 2026)”, at help.twilio.com/articles/53100462475931, surfaced on 24 October 2026, with a companion notice at articles/53100480177819 the same week. Twilio attributes the change to Meta and dates it to 1 October 2026. Read both notices, then read your own country and category rows on twilio.com/whatsapp/pricing. Treat any figure in a blog post, this one included, as unconfirmed until you do.
One operator detail a rate card cannot show: the line that breaks inbound-heavy budgets is direction. Teams model outbound, because outbound is what they initiate. Then replies arrive, and the platform fee applies to those as well. Budget per direction, not per month.
What does a WhatsApp message cost on each route?
Each route charges for something different, so no single per-message price holds across them. Twilio meters a platform fee on top of Meta's fee. As published, Meta bills templates per delivered message and lists service messages free inside the 24-hour customer service window. Flat-licence tools charge per device and nothing per message. Pricing model and account risk decide most purchases, and rarely appear side by side.
| Route | Pricing model | Who charges what | Ban / account risk | Where conversations live |
|---|---|---|---|---|
| Twilio | Metered, per message | Meta's fee passed through, plus Twilio's platform fee (published as $0.005) on inbound and outbound | Sanctioned connection, so there is no unofficial-client risk; Meta can still restrict an account for policy or quality reasons. Needs a business portfolio and a dedicated number. | Twilio's infrastructure and Meta's |
| Meta Cloud API, direct | Metered, per message | Meta's fee only, as published: templates billed per delivered message, service messages free inside the 24-hour window | Sanctioned; Meta can still restrict an account for policy or quality reasons. Needs portfolio, dedicated number, template approval. | Meta's |
| A BSP such as WATI, 360dialog or Interakt | Metered, plus a subscription | Meta's fee, the BSP's markup, often a monthly platform subscription | Sanctioned, with the same Meta approvals plus the vendor's own terms. | The vendor's cloud |
| Self-hosted open source, e.g. Evolution API or WAHA | Flat infrastructure cost, no per-message fee | You pay for the server and your own engineering time; nobody meters messages | Unofficial connection, so bans are possible. Anti-ban, GUI and storage are yours to build and maintain. | Your server, once you build storage |
| SocialMate | Flat licence: $0 Free, $10/month or $99/year Pro | SocialMate only. No per-message fee and no Meta fee, because it is not the Cloud API. | Unofficial connection on your own number, so bans are possible. A built-in anti-ban engine reduces the risk; it does not eliminate it. | Your own machine, in local storage |
Short verdicts, one trade-off each:
- Twilio — for teams that want a documented, sanctioned integration and one consolidated bill. Trade-off: the platform fee is symmetric and uncapped.
- Meta Cloud API direct — for teams with engineering time for onboarding and enough volume that removing a platform layer matters. Trade-off: you own Meta's compliance surface.
- A BSP — for teams that want an inbox, assignment and analytics bundled with the channel. Trade-off: Meta's fee plus markup plus a subscription.
- Self-hosted open source — for teams that will run Docker and build the rest. Trade-off: anti-ban, GUI and storage become your projects.
- SocialMate — for teams automating their own number with local data and a flat licence. Trade-off: the connection is unofficial, so bans remain possible.
Full side-by-sides live in the Cloud API comparison and the self-hosted comparison.
What counts as one billable message, and why is there no single price?
One billable message on Twilio's meter is one WhatsApp message in either direction. Meta counts differently, as published: template messages are billed per delivered message, while service messages inside the 24-hour customer service window are free. Price per message therefore depends on which kind you are sending, to which country, and when the customer last wrote to you.
Meta's WhatsApp Business Platform pricing documentation sets the rate card as a matrix of country and category — marketing, utility, authentication. There is no single price per message to look up, which is why the search that led you here returns a fragment of one page rather than a number you can carry away.
Three things change the billable count on top of direction:
- Category. A marketing template and an authentication template are different rows of the same matrix.
- The 24-hour window. Whether a reply is a free service message or a billed template depends on when the customer last messaged you.
- Direction. As published, Twilio's platform fee applies to received messages, while Meta's service messages are free inside the window.
Meta has changed this split before and is changing it again: Twilio's 24 October 2026 notice states that Meta's revised pricing takes effect on 1 October 2026. Confirm the current rule on Meta's pricing page before modelling. For the quality-rating and messaging-limit side of the same window, see WhatsApp messaging limits and quality rating in 2026.
Why does Twilio charge $0.005, and what does the fee cover?
A per-message platform fee is normally for the layer between your code and Meta: the Meta relationship, the compliance surface, SDKs, delivery plumbing and one consolidated bill. That is the usual justification for a platform fee, and on this route it is what you are paying for rather than building.
It is a service, not a markup on nothing. Building that layer is a project; paying a per-message rate is a rate. A team with no engineer and a compliance review to pass is buying something real.
Its second function is absorbing rate changes. Twilio's two October 2026 Help Center notices exist because the underlying structure is being repriced; a platform layer is what keeps your integration stable while that happens. Confirm what the fee covers on the live page rather than taking this paragraph's framing of it.
What the fee is not is a substitute for Meta's fee. Twilio presents Meta's rates as pass-through with its own per-message fee as a separate line, which is exactly why the two get conflated in second-hand summaries, including the summary that sent you here.
What does the $0.005 not include?
The $0.005 excludes Meta's per-message fee, the onboarding that lets you send at all, and any inbox. It buys transport between your code and WhatsApp. Everything a support or sales team needs around that transport — history, assignment, a safety layer for a number you own — is built or bought separately.
- Meta's per-message fee. Pass-through, country- and category-specific. It is not one number, so it cannot be added to $0.005 in advance.
- Inbound. As Twilio publishes it, the platform fee applies to messages you receive. Inbound-heavy budgets break here first.
- The right to send. Meta requires a business portfolio, a number dedicated to the API, template review, category rules and adherence to the 24-hour customer service window. None of that is on a rate card, and all of it costs time.
- An inbox. Twilio's WhatsApp product is transport; shared inbox, assignment and history are separate products or builds. See a Twilio alternative for WhatsApp without building your own inbox.
- Data locality. Your conversations live in Twilio's infrastructure and Meta's, not on hardware you control.
One honest counterpoint, in the other direction: the official route is sanctioned, so there is no unofficial-client risk to the number. Meta can still restrict an account for policy or quality reasons, so sanctioned is not unconditional, but it is a genuine advantage and self-hosted tools should say so plainly.
What does $0.005 per message cost at real volume?
At $0.005 a message, Twilio's platform fee alone runs $30 a month at 200 messages a day and $750 a month at 5,000 a day — $9,125 a year. Those figures are the platform fee only. Meta's per-message fee is charged on top of every row and varies by country and category.
| Messages / day | Platform fee / day | / month (30d) | / year |
|---|---|---|---|
| 200 | $1.00 | $30 | $365 |
| 1,000 | $5.00 | $150 | $1,825 |
| 5,000 | $25.00 | $750 | $9,125 |
| 10,000 | $50.00 | $1,500 | $18,250 |
Read those as a floor, not a total. These multiplications are arithmetic on the published platform fee only; they are not a quote, and they expire when the rate does. The Meta line sits on top of every row, which is why a page that quotes only the platform fee understates the bill.
Now the figure worth carrying around. At $0.005 a message, 19,800 messages a year costs the same as a full year of SocialMate Pro at $99. On the monthly plan, $120 a year matches 24,000 messages. $100 of platform fee buys 20,000 messages, before Meta's fee is counted.
SocialMate Free covers 200 messages a day at no cost. Pro is $99 a year or $10 a month with no per-message fee. See what each tier includes.
Is a flat licence cheaper, and when is it not?
A flat licence is not cheaper at every volume. The crossover is about 19,800 messages a year on the $99 annual plan and 24,000 on the $120 monthly plan — roughly 54 to 66 messages a day, assuming one device seat and excluding Meta's fee from the Twilio side. Count Meta's fee in and the true crossover arrives sooner. Below that line, pay the meter.
The honest inverse matters as much. At 50 messages a day, $0.005 is roughly $7.50 a month — less than SocialMate Pro Monthly at $10. If your WhatsApp use is a support desk answering inside the free customer service window, your Meta bill may already be small and a licence may not be your best purchase at all.
The shape to hold: a per-message fee is a floor; a flat licence is a ceiling.
The ceiling is real but it is not unlimited. Free sends up to 200 messages a day on one account. Pro starts at a safe 500 a day per account and, after 72 hours of session warming, High-Volume Mode scales to 5,000 a day per account. Higher volume is never risk-free at any tier; a gradual ramp plus monitoring is the safe default, which is why warming is not optional. One licence includes one device; add seats for more concurrent machines, and WhatsApp accounts are unlimited on Pro with no Meta approval involved.
If you want to test the crossover on your own volume, the 7-day Pro trial is opt-in: it is started from inside the app, needs only an email, and requires no card. Download the free app and run the numbers against your own traffic rather than a table.
When is the official Cloud API the right answer?
When you send template messages to opted-in audiences at scale, or your compliance team requires a sanctioned channel, the official route is the right answer. It costs more and asks more of you, and in exchange the connection itself is sanctioned. No self-hosted tool should pretend otherwise, this one included.
SocialMate is built for the other job: a batch of individual, personalised messages to people already waiting on you — they ordered, they booked, they asked. Consent is required. It is not a bulk-messaging, broadcast or campaign platform: identical text to many contacts is blocked by the duplicate-content guard, and a batch means many individual messages, each paced by the anti-ban pipeline.
Two statements, plainly. Automation of a personal number can violate WhatsApp's terms, and bans are possible on every route, including this one. SocialMate reduces that risk; it does not eliminate it. The engine randomises delays and jitter, offers Safe, Balanced and Fast pacing profiles, applies per-number rate limits, warms new numbers, shows a real typing indicator and read receipts before replying, throttles adaptively as risk climbs, scores risk live including cold-outreach detection, and auto-resumes accounts that were cooled. On a desktop install it connects from your own residential IP — the network WhatsApp already associates with your number, which removes a risk factor rather than removing risk.
SocialMate is independent. It is not affiliated with, endorsed by, or partnered with WhatsApp or Meta.
If your question is whether a general-purpose assistant is permitted on the channel at all, read what the 2026 chatbot rules allow before you pick a route.
How do you keep your own stack and drop the per-message fee?
You run SocialMate on your own machine and call its local HTTP API at 127.0.0.1 with an x-api-key, or drive it from the native n8n node or the MCP server. Plain text send and the read endpoints run on Free. Pro adds media, groups, polls, locations, contact cards, scheduled messages, the smart queue and the named tunnel; 9 of the 35 webhook events are free.
Three ways in:
- HTTP API and webhooks. Your backend sends and receives events back. This is the path for Make, Zapier, Shopify, WooCommerce and anything else with an HTTP client. A stable inbound URL needs the Pro named tunnel.
- n8n. A first-class native community node, n8n-nodes-socialmate, with a scope-aware credential, an action node and a trigger node. Every operation is exposed as an n8n AI-Agent tool. Its Get AI Context operation returns a whole conversation, role-mapped and token-windowed, so memory survives restarts.
- MCP. A native Model Context Protocol server exposes 44 WhatsApp tools to Claude Desktop, Cursor, Claude Code and any MCP client. The local API server is off by default; switching it on is step one, and forgetting it is the usual reason tools do not appear.
Be precise about what these are: the WhatsApp hands and the memory your own LLM controls. AI replies, summaries and triage generated by SocialMate are coming soon and do not ship today. Every tool call still passes the same anti-ban, key-scope and tier gates, so an agent cannot bypass a limit.
Docs at /docs; the n8n hub at /docs/n8n.
| Route | Pricing model | Who charges what | Ban / account risk | Where conversations live |
|---|---|---|---|---|
| Twilio | Metered, per message | Meta's per-message fee passed through, plus Twilio's platform fee (published as $0.005) on inbound and outbound | Sanctioned connection, so there is no unofficial-client risk; Meta can still restrict an account for policy or quality reasons. Requires a business portfolio and a number dedicated to the API. | Twilio's infrastructure and Meta's |
| Meta Cloud API, direct | Metered, per message | Meta's per-message fee only, as published: templates billed per delivered message, service messages free inside the 24-hour window | Sanctioned connection; Meta can still restrict an account for policy or quality reasons. Requires business portfolio, dedicated number, template approval and the 24-hour window. | Meta's |
| A BSP such as WATI, 360dialog or Interakt | Metered, plus a subscription | Meta's fee, the BSP's markup, and often a monthly platform subscription | Sanctioned. Same Meta approvals as the Cloud API, plus the vendor's own terms. | The vendor's cloud |
| Self-hosted open source, e.g. Evolution API or WAHA | Flat infrastructure cost, no per-message fee | You pay for the server and your own engineering time; nobody charges per message | Unofficial connection, so bans are possible. Anti-ban, GUI and storage are yours to build and maintain. | Your server, once you build storage |
| SocialMate | Flat licence: $0 Free, $10/month or $99/year Pro | SocialMate only. No per-message fee and no Meta fee, because it is not the Cloud API. | Unofficial connection on your own number, so bans are possible. A built-in anti-ban engine reduces the risk; it does not eliminate it. | Your own machine, in local storage |
How to verify Twilio's current WhatsApp message price before you model it
- Read the two lines separately Open twilio.com/whatsapp/pricing. Treat Meta's pass-through rate for your country and category as one line and Twilio's own platform fee as another. Never add a headline platform fee to a budget on its own.
- Find your country and category rows on Meta's rate card Open Meta's WhatsApp Business Platform pricing documentation for the template categories you actually send — marketing, utility, authentication — and note whether your replies fall inside the free 24-hour customer service window.
- Read the notices, then date-stamp your numbers Read both October 2026 WhatsApp pricing notices in Twilio's Help Center, note the effective date, and write the date you checked beside every figure in your model. Rates move; undated numbers become wrong quietly.
Frequently asked questions
Is Twilio's $0.005 per message the whole cost of a WhatsApp message?
No. As published, it is Twilio's platform fee, billed on top of Meta's per-message fee. Meta's fee varies by country and message category and is the term to check first. Model them as two separate lines, and confirm both on Twilio's live pricing page before either figure goes into a budget.
Does Twilio charge for inbound WhatsApp messages?
As published, yes. Twilio's per-message platform fee applies to both directions, so replies you receive carry it as well as messages you send. For an inbound-heavy support line this is usually the line item that surprises the budget, and it is the first thing to check on the live page.
What counts as one billable message on these meters?
On Twilio's meter, one WhatsApp message in either direction. On Meta's meter, as published, template messages are billed per delivered message while service messages inside the 24-hour customer service window are free. Twilio's October 2026 pricing notice says Meta's revised structure takes effect on 1 October 2026, so confirm the current rule on Meta's pricing page.
How much does it cost to send 5,000 WhatsApp messages a day on Twilio?
Twilio's platform fee alone is $25 a day, $750 a month and $9,125 a year at $0.005 per message. Meta's per-message fee is additional and varies by country and category, so the real total is higher. SocialMate Pro is $99 a year with no per-message fee, starting at a safe 500 messages a day per account and reaching up to 5,000 a day after 72 hours of warming. Bans remain possible at any volume on any route.
At what volume is a flat licence cheaper than $0.005 per message?
About 19,800 messages a year on the $99 annual plan, or 24,000 on the $120 monthly plan — roughly 54 to 66 messages a day, assuming one device and excluding Meta's fee from the Twilio side. Include Meta's fee and the crossover comes sooner. Below it, the meter is cheaper.
Is there a WhatsApp API with no per-message fee?
Yes, self-hosted routes. SocialMate and open-source projects such as Evolution API and WAHA charge nothing per message because the work runs on your machine or server. All use an unofficial connection, so bans are possible. The official Cloud API is the sanctioned route, though Meta can still restrict an account for policy or quality reasons.
Do I need Meta business verification on a self-hosted route?
Not on SocialMate's route. It links your existing WhatsApp number by QR code and does not use the Cloud API, so there is no business portfolio, no number dedicated to the API and no template review. The trade-off is an unofficial connection and the account risk that carries.
Is there a free way to test whether a flat licence beats the meter?
Yes. SocialMate's 7-day Pro trial is opt-in: you start it inside the app from Onboarding, Settings, or the in-app Pricing page, it asks only for an email, and no card is required. Compare your real daily message count against the 19,800-a-year crossover before you decide.
How do I check Twilio's current WhatsApp price myself?
Open twilio.com/whatsapp/pricing and read two lines separately: Meta's pass-through rates for your country and category, and Twilio's own platform fee. Then read the WhatsApp pricing notices in Twilio's Help Center, the first surfaced 24 October 2026. Any second-hand figure, this page included, needs that check.
Keep reading
Guides
Evolution API License 2026: What Apache 2.0 Grants, and What It Does Not
Evolution API is Apache 2.0: free to use, modify and resell. Here is what that license grants, what it withholds, and the license…
Guides
Message Mates: What the Phrase Means, and Where Consent Draws the Line
"Message mates" means texting friends, not a WhatsApp feature. What the phrase covers, and why consent separates personal chat fr…
Guides