7 tips before WhatsApp service replies stop being free
Right now, free-form replies inside the 24-hour customer service window are still free on the WhatsApp Business Platform. That changes on October 1, 2026: Meta will charge per delivered service message, and utility templates sent inside that window stop being free too. (Meta Business Agent gets its own token bill even sooner — August 1.)
If you already read our note on the July rate card, treat this as the next step: not more pricing theory — seven habits to install before the meter starts.
1. Count your outbound messages this week
You can’t budget what you don’t measure. Pull a week of inbox volume: how many replies per conversation? How many “ok”, “one sec”, and “following up”? Every short ping will cost something after October.
Tip: sample 20 closed chats and average the business-side message count. Multiply by monthly conversations. That’s your rough October baseline.
2. Answer once, completely
Partial replies (“let me check”) followed by three more bubbles feel friendly — and will get expensive. Train the team to batch the answer: status + next step + one clear question, in a single message when you can.
Saved replies help here. Build 8–10 “complete” blocks (shipping status, hours, payment options) instead of tiny fragments. See templates vs saved replies.
3. Kill duplicate “just checking” loops
Two agents saying the same thing, or a workflow + a human both nudging, doubles spend later. Use assignment so one owner speaks. Pause automations when a human takes the thread.
4. Prefer FAQ macros over improvisation
Unstructured typing creates long threads. Macros keep tone consistent and usually shorter. Review your top 10 intents monthly and rewrite the longest ones down.
5. Put AI on the boring 80% — with a hard handoff
AI that chatters for ten turns is a cost amplifier once service messages are billed (and Meta’s own agent bills per token from August). Use AI for FAQs and triage, then escalate cleanly — as in AI first response. Prefer your model key over mystery black boxes when you care about cost control.
6. Move transactional updates to the right tool
Order shipped, appointment confirmed, payment received: that’s utility template / calendar / email territory — not a long free-form essay. After October, in-window utility isn’t free either, so still keep those messages short and intentional. Booking flows: calendar + AI.
7. Set a first-response rule (and an after-hours auto)
Slow first replies don’t just hurt CSAT — they stretch conversations into more back-and-forth the next day. Pick a daytime FRT target, assign unowned chats fast, and send one clear after-hours acknowledgement so customers don’t re-ping every hour.
In Wroups
Shared inbox + assignment, saved replies, workflows, and AI agents with your credentials (BYOC) so you can practice lean replies before October — not scramble after the invoice lands.
WhatsApp pricing shifted again — what inbound teams should actually change
July 2026 rate updates hit some marketing and utility markets. Service replies inside the window stay free. Here’s how to keep costs predictable without pausing the inbox.
WhatsApp Coexistence — what it is and how it differs from “pure” API
How Meta lets you use the WhatsApp Business app and Cloud API on the same number — and what that means for your ops in Wroups.