7 min · Aug 3
How Meta separates expected messages (utility/auth) from unsolicited ones (marketing), what each category means for limits, cost and approval, and concrete examples of outreach you can legitimately reframe as utility.
Before you write your first WhatsApp template, there's a decision that will shape how much reach, how much cost, and how much approval friction you'll carry for the entire life of your operation: which category each message falls into. It's not a config detail. It's a strategy decision, and it's worth making deliberately before the problem shows up in production.
Meta doesn't classify your messages by what you're trying to achieve, but by what the user expects to receive. Its whole template policy revolves around one distinction: is this message something the person requested, initiated, or agreed to (expected), or is it something your business decided to send on its own (unsolicited)? That line separates the categories, and each category has very different consequences.
The category isn't a cosmetic label. It changes three things that hit your results directly:
Simple mental rule: if you remove the commercial part and the message no longer makes sense, it's marketing. If the message is still useful to the user without the promo, you can probably phrase it as legitimate utility.
Plenty of messages people label as marketing by default actually map to a real interaction and can be phrased as legitimate utility. Examples:
Being honest about this saves you recategorizations and blocks. If the message meets any of these, it's marketing and should be treated as such (approval, spaced cadence, expect the cap):
Don't try to disguise marketing as utility. Meta detects it, recategorizes the template, and in the worst case penalizes your number's quality. The winning strategy isn't gaming the classification — it's designing your flow so each message falls into the honest category it belongs to.
A healthy outreach operation doesn't choose between marketing and utility: it sequences them. Marketing makes the cold first touch (accepting its cap and its cost). The moment the contact replies, the 24-hour session window opens, where you converse with free-form messages — no template, no cap. And every transactional thing that comes out of that relationship (confirmations, reminders, notices) lives as utility. Designing the flow with this sequence is what gives you sustainable reach instead of an account that shuts off every time you raise volume.
Blind Agents is built around this distinction: it picks the right template per step, spaces marketing ones so they don't collide with the cap, and prioritizes keeping the conversation alive inside the session window, where no category limits you anymore. The business decision, executed by the engine.
Before you launch your outreach, do the exercise: list every message in your sequence and honestly classify it as expected or unsolicited. Reframe as utility everything that legitimately is, accept marketing for what it is, and design the flow to move into the conversation window as soon as possible. That deliberate classification, done before the problem, is the difference between scaling and forever putting out fires.
También te puede interesar
8 min
Why your WhatsApp messages aren't landing: the EC_FREQUENCY_CAPPING guide
What WhatsApp frequency capping (EC_FREQUENCY_CAPPING) is, why Meta enforces it, the difference between MARKETING, UTILITY and AUTHENTICATION templates, and a best-practices checklist so your outreach sequences stop silently failing.
6 min
How to Automate WhatsApp With an API (Event → Template)
Learn how to automate WhatsApp with an API: one event (a POST) creates the contact and fires an approved template. Real use cases plus a step-by-step guide.
6 min
Migrate From Personal WhatsApp to the WhatsApp Business API Without Losing Your Team or Context
How to migrate from personal WhatsApp to the WhatsApp Business API without losing your team or context: why, what to prepare, the steps, and how a shared inbox with an agent takes over.