For a lot of Spanish SMBs, WhatsApp is not a channel. It is the front desk. Local service businesses run appointments and complaints there. Ecommerce shops answer “dónde está mi pedido” there. Small agencies babysit client inboxes there. Margins are already thin: ads, commissions, IVA, and a support person who also does everything else. The quiet assumption for the last stretch has been that replies inside the 24-hour window are free. That assumption ends on 1 October 2026.

This is not a surprise feature drop. Meta published the model earlier. What matters now is the deadline sitting about two weeks out (depending when you read this): add a payment method to the WhatsApp Business Account by 30 September, or Meta will stop delivering service messages once they become charged on 1 October. That is the operational cliff.

What changes on 1 October

Meta’s developer docs on non-template / service pricing spell it out:

  1. Service messages (non-template replies inside an open 24-hour customer service window, powered by a person or a third-party bot) become charged per delivered message. Rates match utility and authentication rates by market. There are no volume tiers for service messages.
  2. Utility templates sent inside that same 24-hour window also become charged again (they had been free in-window since 1 July 2025).
  3. Meta Business Agent messages are a separate category (token-based charging already live from 1 August). Do not confuse “our n8n/Make/Klaviyo bot” with Meta’s own agent product.
  4. New free tier: each business phone number gets 1,000 free delivered service messages per month. Unused units do not roll over. After the free tier, you pay. Meta is clear that without a payment method it can still deliver inside the free tier, then stop.

Non-template messages still only work inside the customer service window. You still cannot cold-outreach with free-form text. The 72-hour free entry point window from Click-to-WhatsApp ads stays free for message delivery (Meta Business Agent token usage is a separate story).

Primary source: Upcoming pricing updates for Meta Business Agent, service and utility messages. Rate cards and the October package also sit on Meta’s main WhatsApp pricing page.

Margin math (illustrative — check your WABA currency card)

Meta publishes separate rate cards per billing currency. A Spanish business billed in EUR should model against the EUR card, not by converting the USD card at today’s FX. Meta Ireland typically invoices Sold-To countries in EUR when the WABA is in EUR.

Order-of-magnitude for Spain, using published utility/authentication list rates that service will match (verify on Meta’s October CSVs before you budget):

  • On the USD card, Spain utility/auth has sat around ~$0.020 per message.
  • On the EUR card (July 2026 published list rates widely cited from Meta’s EUR CSV), Spain utility/auth has sat around €0.0166 per message, before 21% IVA.

Illustrative only (not a quote from Meta’s finance team):

Monthly delivered service replies (after the 1,000 free)Rough Meta fee @ €0.0166+ 21% IVA
2,000 billable~€33~€40
5,000 billable~€83~€100
15,000 billable~€249~€301

A boutique that gets 80 WhatsApp threads a day, with a bot that sends 3–4 auto-acks per thread, burns through the free 1,000 fast. n8n, Make, Klaviyo, ManyChat-style, or custom “service = free” bots will show up as a new P&L line, not as “platform fee surprise.” BSP markups, if any, sit on top.

If your WABA is still in USD while your books are in EUR, FX noise hits the same thin margin. Prefer modelling in the currency Meta actually invoices.

Who feels this in Spain

  • Local services (clinics, trades, hospitality) using WhatsApp as the only CRM.
  • Ecommerce with order-status bots that fire multiple free-form replies per ticket.
  • Agencies running client WABAs without a card on file “because support was free.”
  • Anyone who classified every automation as “service” to dodge template review, then scaled volume.

Checklist before 30 September

  1. Payment method on every WABA in Billing Hub. No card / credit line by 30 Sep is how delivery breaks when charging starts.
  2. Confirm Sold-To country and currency (EUR vs USD). Know which Meta entity invoices you.
  3. Volume audit: last 30 days of delivered non-template (category: service) and in-window utility templates. Pricing Analytics / webhooks already expose category. Subtract 1,000 per number to see billable exposure.
  4. Classify automations: what must stay free-form service, what should be a utility template (order update, appointment reminder), what is actually marketing and was mislabelled.
  5. Kill chatty bots: every “recibido, te respondemos pronto” ack is about to cost money after the free tier. Collapse multi-message flows.
  6. Meta Business Agent vs own bot: token pricing (~global $2 / 1M tokens; Meta’s own examples land around a few USD cents per agent reply) is a different P&L. Do not migrate blindly to “Meta’s agent” thinking it is free support.
  7. Category hygiene and volume limits: utility/auth still have volume tiers; service does not. Do not expect bulk discounts on free-form replies.
  8. Pass the cost into client retainers if you are an agency, in writing, before October invoices land.

GDPR / ePrivacy still apply to logging and outbound. They are not the story this week. The story is cash and continuity.

Name the hype

This is not “WhatsApp launches AI support.” It is a billing cliff Meta announced on a calendar: free service replies (since November 2024) and free in-window utility (since July 2025) flip to paid on 1 October 2026, with a 30 September payment-method hard stop. Spanish SMBs that built support economics on “WhatsApp is free” have a short window to put a card on file, count real volume, and decide which automations still earn their keep.