Email costs effectively nothing per recipient. WhatsApp is billed per message delivered — every template, and since 1 October 2026 plain service replies beyond a free tier of 1,000 per phone number per month. Everything else — how big a list you want, what you send, how often, and what counts as a good campaign — follows from that one difference. They are not competitors. They fail in opposite directions.
The mistake is treating WhatsApp as email with better numbers. Run it that way and you will pay for every impression of a campaign that email would have carried for free.
The economics run the other way
Since 1 July 2025 Meta charges per message rather than per conversation, and until 30 September 2026 its pricing documentation was blunt about the trigger: “You are only charged when a template message is delivered.” Marketing, utility and authentication templates each carry their own rate, and the rate depends on the market you are messaging — with volume tiers on top for utility and authentication. In Germany a marketing message costs €0.1131 on the rate card effective 1 October 2026, still current as of 1 November 2026.
Since 1 October 2026 the free space has shrunk further. Meta charges per message for service messages beyond a free tier of 1,000 delivered service messages per business phone number per month (no rollover, no volume tiers, at the market’s service rate, the same as utility — €0.0456 in Germany as of 1 November 2026), and for utility templates sent inside an open 24-hour window with no free tier at all. Without a payment method on file, service messages stop being delivered once the free tier is used. The exception is a user who arrives through a Click-to-WhatsApp ad on the Android or iOS app: if you answer within the 24-hour window, a free entry point window opens for up to 7 days in which marketing, utility, authentication and service messages are not charged (Meta Business Agent replies still are).
We covered the October change in more detail in what actually changes for your budget.
Put the two channels side by side and the planning logic inverts:
| Cost of one more recipient | negligible | a per-message charge |
| A campaign with a 2% response rate | fine | expensive |
| Bigger list | strictly better | strictly more expensive |
| The thing you optimise | volume and deliverability | relevance per message |
An email list is an asset that costs almost nothing to hold. A WhatsApp list is a liability if you message it the way you message an email list. That is not a warning about etiquette. It is arithmetic.
The consent rules are genuinely different
This is where most teams assume symmetry and get it wrong.
For email, Article 13(2) of the ePrivacy Directive carves out the so-called soft opt-in: if you obtained the address “in the context of the sale of a product or a service”, you may market your own similar products to that customer without separate prior consent, provided you gave clear notice at collection and offer a free, easy objection with every message. Member states implemented this differently, so the detail depends on where your recipients are — but for email the exemption exists. Whether it also reaches messengers is contested; we cover that in the opt-in article linked below.
WhatsApp has no equivalent on Meta’s side. The WhatsApp Business Messaging Policy states you may only contact people if “(a) they have given you their mobile phone number or username; and (b) you have received opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you”, and puts the burden on you: “You are solely responsible for determining the method of opt-in, that you have obtained opt-in in a manner that complies with laws.”
So a customer relationship that lawfully earns you an email does not earn you a WhatsApp message. Two separate permissions, collected separately, recorded separately. We wrote up what a defensible record looks like in WhatsApp opt-in under GDPR.
Who decides what you are allowed to say
In email, the wording is yours. Nobody approves your subject line before it goes out.
On WhatsApp, “you may only initiate conversations using an approved Message Template”, and Meta reserves the right “to review, approve, pause and reject any Message Template at any time”. Sending outside an open window means writing inside a format someone else signed off on, days earlier.
There is a second control layer that email has no analogue for. Per the same policy (last updated 23 September 2026), “users can block or report businesses” and Meta’s “systems may limit the amount of messages a business can send or calls a business can initiate, based on this user feedback”. Meta does not publish the formula, and it discontinued the old Flagged and Restricted number statuses on 7 October 2025, but the policy wording stands as of 1 November 2026. Recipient annoyance does not just cost you unsubscribes — it throttles the channel itself.
Email’s failure mode is the spam folder, guessed at by a filter you cannot see. WhatsApp has no spam folder, but delivery is not guaranteed either.
Meta’s per-user marketing limits cap how many marketing templates one person receives from all businesses combined, failing the excess with error 131049, and as of 1 November 2026 WhatsApp “does not currently deliver marketing template messages” to US phone numbers at all. On top of that, messaging limits start a new business portfolio at 250 unique recipients per rolling 24 hours outside open service windows, rising to 2,000, 10,000, 100,000 and unlimited only while Meta rates your message quality high.
Both failure modes are real. They are not the same problem, and the fixes have nothing in common.
About that 98% open rate
The figure everyone quotes for WhatsApp circulates without a traceable primary source, and Meta publishes no open-rate benchmark for the Business Platform. Treat any comparison built on it as marketing rather than measurement.
What you can measure is narrower and more useful. The Cloud API reports a delivery status per message — sent, delivered, read — because, as the Cloud API webhooks documentation puts it, “each outgoing message can have up to three separate webhooks (one for a status of sent, one for delivered, and one for read)”. Email has no dependable equivalent; the open rate is inferred from a tracking pixel that mail clients increasingly load or block on the recipient’s behalf — Apple Mail, for example, has hidden pixel loads behind Mail Privacy Protection since 2021.
Email’s freedom from pre-approval has limits of its own, too. Since February 2024 Google’s sender guidelines require anyone sending more than 5,000 messages a day to Gmail accounts to authenticate with SPF, DKIM and DMARC and to offer one-click unsubscribe, and every sender to keep the spam rate below 0.3 percent; since November 2025, Google’s FAQ says, non-compliant mail meets “temporary and permanent rejections”. Yahoo sets the same bar, and since 5 May 2025 Outlook.com sends mail from domains above 5,000 a day that fail SPF, DKIM or DMARC to junk, and may reject it. Nobody approves your wording, but the mailbox providers do throttle you.
That asymmetry is worth more than the folklore. On WhatsApp you know a message arrived. On email you are estimating.
What this means for you
Split the work by what a message is worth, not by which channel you like:
- Email — newsletters, long-form content, anything going to your whole list, anything where a 2% response rate is an acceptable outcome, and re-engagement of people who have gone quiet.
- WhatsApp — order and delivery updates, appointment and webinar reminders, abandoned checkout, replies to people who wrote first (free for the first 1,000 a month per number, then billed at the utility rate), and the small segments where one conversion pays for a thousand messages several times over.
- Both — the opt-in itself. Email is the cheapest place to ask for WhatsApp permission, because asking costs nothing and the ask can be repeated.
Two practical rules follow. Never migrate a list sideways: an email address does not carry consent for a phone number, and the numbers are usually missing anyway (the longer version here). And before you send a WhatsApp campaign, price it — recipients times the marketing rate for that market — and compare that number to what the same campaign would cost by email, which is roughly nothing.
Nybero keeps an append-only consent log per contact for exactly this reason, recording how and where each opt-in was given. If you are deciding where to start, start by pricing one campaign both ways. The answer is usually obvious once it has a number attached.
Updated 1 October 2026: WhatsApp service messages became chargeable on this date; pricing, the Business Messaging Policy wording of 23 September 2026 and the email sender requirements were updated against the sources linked above, all retrieved 1 October 2026.
Updated 1 November 2026: prices and the service-message free tier re-checked against Meta’s pricing page and rate card; the Click-to-WhatsApp exception is now stated with its conditions (24-hour reply, up to 7 days, mobile apps only, Meta Business Agent excluded); per-user marketing limits, the US delivery pause and messaging limits are now sourced, and the policy’s feedback-based limit is no longer equated with the discontinued quality-rating statuses; the email section adds Gmail’s enforcement since November 2025, Yahoo and Outlook.com’s requirements of 5 May 2025. Sources retrieved 1 November 2026.
