WhatsApp Message Category Pricing: Marketing, Utility, Auth, Service

Context: four price tags, one inbox

When someone searches “WhatsApp message category pricing,” they are rarely hunting for a PDF of rate cards.

They want a sharper answer: why did that campaign cost more than yesterday’s shipping update, what Meta means by marketing vs utility vs authentication vs service, and what changed when per-message pricing replaced the old conversation model.

This sits beside our 24-hour messaging window ops guide and the template quality rating post. Those pieces cover permission (may I send free-form?) and quality (will Meta keep the template green?). This one is the price tag on each send: category, market, and Meta’s published charging rules.

UnifiedSend is a WhatsApp Business messaging platform (campaigns, shared inbox, AI replies and agents, storefront, bookings, payments). The goal here is not to rebrand Meta’s rate card. It is to stop ops teams treating every outbound bubble as the same cost line.

Problem: teams still bill in their heads like it is one channel

Meta moved WhatsApp Business Platform charging to per-message pricing (PMP) on 1 July 2025. Delivered template messages are charged by category and by the recipient’s country calling code. That replaced conversation-based pricing, which is now deprecated documentation.

The four categories that matter for day-to-day ops are:

• Marketing. Promos, offers, cart reminders, product launches, win-backs. Template only. Usually the highest rate on a given market’s card. No volume tiers.
• Utility. User-triggered or critical updates: order confirmations, shipping, appointment reminders, account alerts. Template. Cheaper than marketing in most markets. Volume tiers exist.
• Authentication. OTPs and identity checks. Template. Often priced like utility, with volume tiers, and some markets also have authentication-international rates.
• Service. Non-template replies inside an open customer service window (human agent or third-party AI). For a long stretch these were unbilled. Meta’s published docs say service messages become chargeable per message from 1 October 2026, at the same market rates as utility and authentication, with a free monthly tier of 1,000 delivered service messages per business phone number. Unused free units do not roll over. Volume tiers do not apply to service.

That is Meta’s model, not a UnifiedSend invention. BSP blogs from Twilio, WATI, respond.io, Interakt, and others describe the same foundation because it is platform policy. Where teams still lose money (and trust) is treating category as a label you pick for convenience.

The ops pain looks like this:

• Marketing copy is pasted into a utility template, Meta recategorises or rejects it, and the campaign either stalls or lands on the expensive card you tried to dodge
• Finance forecasts from the old “one conversation” mental model, then the invoice shows one charge per delivered marketing template
• Support assumes every in-window reply is free forever, then service charging and in-window utility charging (also published for 1 October 2026) show up as a surprise line
• Auth OTPs and promo blasts share one vague “WhatsApp budget” with no split by category or market
• Agents send long free-form threads with no visibility into how close the number is to the 1,000 free service messages for the month
• Nobody has a payment method on the WhatsApp messaging account, so when service becomes charged Meta may stop delivering those replies after the free tier
• Click-to-WhatsApp ad leads enjoy a free entry point billing window when you reply in time, but the team still mislabels the follow-up promo as utility

Permission and price remain two clocks. An open 24-hour window lets you send free-form service messages. It does not turn a promo into a free paste. Marketing still needs an approved marketing template and documented opt-in. Utility is for events the user triggered (or critical alerts), not a sale dressed as shipping.

Insight: map every send to a category before you hit send

On UnifiedSend, the useful habit is a category map, not a hope that Meta will guess kindly.

1. Name the job of the message. Are you reaching out with an offer (marketing), confirming something the user already started (utility), verifying identity (authentication), or answering someone who wrote you (service)? If two jobs sit in one bubble, split them. Do not hide a promo inside a shipping template.

2. Respect who opens the conversation. Business-initiated contact outside the customer service window needs an approved template in the right category. Customer-initiated contact opens the window for service replies. Your template does not reopen free-form. Their reply does. Category pricing does not rewrite that permission clock. See the session vs templates guide for the window itself.

3. Read Meta’s published dates, not hallway lore. As of Meta’s pricing docs updated late September 2026:

• Per-message charging for marketing, utility, and authentication templates is already live
• From 1 October 2026, service messages are charged per delivery after the 1,000 free monthly tier per business phone number
• From 1 October 2026, utility templates sent inside an open customer service window are charged again (they had a free-in-window stretch after July 2025)
• Reaction messages stay outside the service charge path in Meta’s published notes
• Eligible governments and non-profits keep different service treatment under Meta’s published policy
• Rate cards can move on Meta’s quarterly calendar (1 Jan, 1 Apr, 1 Jul, 1 Oct) with advance notice rules

Always check Meta’s live pricing and billing pages before you lock a budget. Third-party blogs lag. UnifiedSend will not invent free categories Meta has withdrawn.

4. Wire the inbox and campaigns around category hygiene. Practical shape inside UnifiedSend:

1. Separate campaign and support paths. Broadcasts and win-backs are marketing template work with opt-in. Ticket replies are service (or utility templates when you need structured updates).
2. Keep template libraries labelled. Marketing, utility, and authentication packs should be named and approved for the jobs they actually do. Quality rating still matters; a cheap utility template that gets rejected or downgraded is not cheap.
3. Surface cost-relevant signals where agents work. Window open/closed is permission. Category and “are we still inside the free service tier this month?” is finance. Agents should not reverse-engineer either from failed API errors alone.
4. Teach bots the expensive mistake. A bot that retries failed free-form sends, or fires marketing-shaped copy on a utility path, burns both trust and budget. Fail closed into the right template, or hand off to a human with context.
5. Treat CTWA and Page CTA entry as speed plus honesty. A timely first reply can open Meta’s free entry point billing window for qualifying message types. That does not license a miscategorised promo later. Qualify, assign, and hand off in the same workspace.
6. Put a payment method on the messaging account. Meta has warned that without one, service delivery can stop once charging applies and the free tier is used. Ops continuity is a billing checkbox, not only a product feature.

Be precise about what this does and does not claim.

What the ops path is aiming for

• Clear marketing vs utility vs auth vs service decisions before send
• Fewer “why is this invoice huge?” surprises after category mistakes
• Template packs that match real jobs, not wishful labels
• Soft handoff between AI or bot first reply and human agents with context kept
• Honest talk about Meta rate cards versus product wiring

What still sits on Meta’s side

• Template approval, recategorisation, and quality rating
• Rate cards, volume tiers, free tiers, and quarterly updates
• Free entry point rules for ad and CTA entry points
• Policy on opt-in, opt-out, and what counts as marketing
• Whether a given government or non-profit cohort keeps free service treatment

Product wiring and Meta clearance remain two timers. UnifiedSend can help you pick the right path, route the thread, and send the right message type. It cannot invent a free marketing send, and it cannot promise Meta will keep today’s price labels forever.

Outcome: cleaner budgets, fewer category fights, calmer WhatsApp ops

When teams treat message category as an ops object, the week feels different.

Marketing stops sneaking offers into utility templates. Support stops assuming every in-window reply is free forever. Finance can forecast marketing, utility, auth, and service as separate lines instead of one fuzzy “WhatsApp” bucket. Bots fall back into the right template instead of burning retries. Leaders read Meta’s 1 October 2026 service and in-window utility updates as planning inputs, not as a fire drill after the invoice lands.

That is the competitor gap worth owning. Plenty of BSP pages reprint rate cards. Fewer product posts show how category hygiene, inbox visibility, template packs, CTWA speed, and campaign honesty sit in one WhatsApp workspace. UnifiedSend is built for that ops layer: campaigns, shared inbox, AI replies and agents, storefront, bookings, and payments under the same Meta clocks.

If you want category-aware WhatsApp ops beside the people who answer the chat, try UnifiedSend and run messaging like infrastructure, not like a hopeful inbox.