WhatsApp Business API in Europe — a country-by-country guide
Where WhatsApp actually dominates in Europe, what it costs to send in each market, and the rules that differ by country before you launch a campaign.
September 24, 2026 · 4 min read
Europe is the strongest region in the world for business messaging on WhatsApp: very high adoption, concentrated in countries with real purchasing power. If you're deciding where to launch first, this is the practical map.
Where WhatsApp actually wins
Adoption is not evenly spread. Roughly, by share of smartphone users who use WhatsApp:
| Market | WhatsApp adoption | Notes |
|---|---|---|
| Spain | Very high (~90%+) | Effectively the default way people message, business included |
| Italy | Very high (~90%) | Strong for customer service and appointment reminders |
| Netherlands | Very high (~85%) | Business use is mainstream and expected |
| Portugal, Greece | Very high | Similar profile to Spain |
| Germany | High (~80%) | Huge market; buyers are the most privacy-sensitive in Europe |
| UK | High (~75%) | Competes with SMS and email, which are still entrenched |
| France | High | WhatsApp leads, though Messenger retains a share |
| Poland, Ireland, Switzerland, Austria | High | Reliable WhatsApp-first audiences |
| Nordics | Mixed | Finland is WhatsApp-first; Sweden and Denmark lean on SMS and Messenger |
Adoption figures are approximate and move year to year — treat them as rank order, not precision.
The contrast worth knowing: the United States sits near a quarter, because iMessage and SMS own the market there. A WhatsApp-first product is an easier sell in Madrid, Milan or Amsterdam than in Chicago.
What it costs to send
Meta bills per template message, priced by the recipient's country and the template category — marketing, utility or authentication. European rates are among the highest in the world; a marketing template to a German or UK number costs materially more than one to an Indian or Brazilian number.
Two things follow:
- Model your cost per market before you scale, not after. The same campaign can cost several times more in Western Europe than in Southern Europe or Latin America.
- Use the right category. A delivery update sent as a marketing template costs more and is more likely to be seen as promotional. Utility templates are cheaper and better received.
Meta publishes current rates, and they change — check them rather than trusting any vendor's table, including ours. On every platform, including this one, those charges go to your own WhatsApp Business account. See WhatsApp API pricing for how the billing model works.
The rules that differ
Consent is the constant. Every EU market requires prior opt-in for marketing messages, and Meta requires it independently. There is no European country where buying a list and blasting it is viable. Start with WhatsApp marketing and the GDPR.
Germany is the strictest in practice — not because the law differs, but because enforcement and competitor complaints (Abmahnung) are real and common. German buyers will ask for your DPA, your sub-processor list and your data location before they sign. Have all three ready; they're a qualifying question, not a formality.
Italy and Spain are the fastest to adopt and the least friction-heavy. If you want early traction, start here.
The UK is post-GDPR but effectively equivalent, with the UK GDPR and PECR. You'll want the International Data Transfer Addendum alongside the Standard Contractual Clauses — ours is already incorporated.
Language matters more than you'd expect. Templates are approved per language, and a Spanish customer who gets an English template reads it as spam. Create the template in each language you serve; approval is per language pair, so plan for it rather than translating at send time.
Time zones and send windows
Europe spans three time zones, and messaging etiquette is stricter than email. Sending at 21:00 local is a complaint; several countries have norms (and in some cases rules for telemarketing) about contacting consumers outside reasonable hours. Schedule by the recipient's market, not your own.
The 24-hour window, in practice
Once someone messages you, you have 24 hours to reply freely with anything; outside it, only an approved template. This matters more in Europe than elsewhere because service expectations are high — a reply at hour 25 costs you a template message and reads as an ad. Keep response times inside the window and most of your replies stay inside the window (Meta's free tier covers the first 1,000 service messages a month per business phone number; see the pricing guide). See the 24-hour window.
A launch order that works
- Pick one market, not the continent. Spain, Italy or the Netherlands for speed; Germany for size, if your compliance answers are ready.
- Get consent flowing before you build anything else — a website tick box and a click-to-WhatsApp entry point.
- Warm the number up. A new number starts at Meta's lowest tier and climbs with volume and quality; a sudden blast on day one is the fastest way to get restricted. We ramp new numbers automatically over their first days of bulk sending.
- Templates in the local language, submitted early, because approval takes time.
- Then scale into the next market, reusing the same flows with new translations.
How SendFromChat fits
Everything above is what the product is built around: templates with Meta's rules checked as you type, automatic new-number warm-up, STOP handling that applies across every campaign and sequence, a DPA with the SCCs already incorporated, and EU VAT handled by our merchant of record so you get a proper invoice. And because it runs as an MCP server, you can do all of it by asking Claude or ChatGPT — including "what did this campaign cost me in Germany last month".
Start free for 30 days — one number and 1,000 messages, no card.
Do this from your AI assistant
SendFromChat connects Claude, ChatGPT, Cursor or any MCP client to the WhatsApp Business API — templates, bulk sends, inbox, chatbots and sequences, just by asking. 30 days free, no card.
Start freeMore guides
Send WhatsApp messages from Zapier or Make with one HTTP request
Send WhatsApp template messages from a Zap or a Make scenario using a plain webhook or HTTP step, with a test key, idempotent re-runs, refusal handling and a webhook for delivery status and replies.
WhatsApp display name rejected? The rules, the fix, and the 14-day re-register
Why Meta rejects a WhatsApp Business display name, what each rejection reason in the webhook means, how to edit and resubmit it (10 edits in 30 days), and the 14-day window to re-register the number after approval. Includes a mock-tested Node script.
WhatsApp two-step verification PIN: what to do when register asks for it
What the 6-digit two-step verification PIN does on the WhatsApp Cloud API, when the register call needs your existing one, how to change a forgotten PIN, why you should not loop the call (10 tries in 72 hours), and Meta's PIN deprecation for eligible numbers.
Send a WhatsApp message when a Stripe payment fails (and when it succeeds)
Tell a customer on WhatsApp when their Stripe invoice payment fails, with a link to fix it, and send a receipt when it is paid. A signed-webhook Node server, two templates, no double sends on Stripe retries.