WhatsApp Template Approval & Categories

Most teams treat template submission as a pass/fail gate. Approved, ship it. That framing misses the expensive half of the process.

Meta's pricing documentation is explicit: businesses "accept the charges associated with the category applied to the template at time of use". You submit a template; Meta decides what kind of message it is. That decision, not your intention, sets the bill. A template you wrote as an order update that Meta categorises as marketing does not cost slightly more — it moves into a different charging model entirely.

Read the utility row again. A utility template is free only inside an open customer service window. That window lasts 24 hours and is opened or refreshed by the customer replying to you. So the same approved utility template can be free this morning and chargeable this evening, purely because the customer went quiet in between.

This is the single most useful thing to understand before you build a template library: the category sets the pricing rule, and the window decides whether that rule costs you anything today.

You control three things, and it is worth being clear about which is which.

The category you request. You nominate one at submission and Meta reviews it. If Meta's view differs from yours, Meta's view is the one that gets charged.

The wording. This is your main lever over categorisation. A template that states a transaction fact — a booking time, a payment status, an account event the customer already initiated — reads as utility. The moment the same template adds an offer, an inducement, or a nudge towards a purchase the customer did not ask for, it reads as promotional. Businesses routinely lose the utility rate by appending one line of upsell to an otherwise transactional message.

The variables. Templates use placeholders for the parts that change. Loose or over-broad variables make it harder for a reviewer to see what the message will actually say when sent, and they make the template easier to misuse later.

We are deliberately not printing a "top ten rejection reasons" list here. Those lists are usually copied between vendor blogs rather than read off Meta's documentation, and several are out of date.

Four facts from Meta's own documentation carry almost all the practical weight.

Outside the 24-hour customer service window, any business-initiated message is required to use a pre-approved template. That template may be text, media or interactive. There is no free-form escape hatch. If you have no approved template that fits a situation, you cannot message that customer at all until they message you.

Inside the window, you do not need a template. Free-form service messages are permitted and are free. Meta's own guidance is to prompt the user to reply in order to activate the customer service window.

Messages sent from a WhatsApp user to a business are never charged. Inbound costs nothing, ever.

Conversations opened from Click-to-WhatsApp ads are a free entry point, with 72 hours in which all messages are free.

Put together, these produce a template strategy rather than a template list:

• Build templates for the situations where you must reach a silent customer. Those are the ones you will pay for.
• Design your in-window messaging to invite a reply, because a reply refreshes the window and everything inside it is free.
• Do not build a large marketing template library and assume you will use it lightly. Marketing templates are charged on every send with no window relief.

And one exercise before submitting anything: for each template, write down the state the customer will be in when it fires.

The fourth row surprises people. Activity on your website does not open a WhatsApp customer service window. Only a WhatsApp reply does.

We are not printing per-country rupee rates. Meta revises them, they differ by country and category, and a stale table on our site would mislead you into a budget you cannot hold. See Meta's published pricing documentation for current rates (checked 19 August 2026).

Templates are how you knock on a closed door. They are approved, categorised, charged, and — importantly — they can be ignored.

A contact who has stopped replying is not a template problem. They are a channel problem. Each further send costs money, adds nothing if it goes unread, and puts your message quality standing at risk if it lands as unwanted. This is the honest boundary of WhatsApp-only tooling: it automates well for people currently in a conversation with you, and has nothing to offer the larger group who are not.

HelloGrowthCRM's position is straightforward: WhatsApp tools automate inside WhatsApp; we continue the sequence off it. When a thread goes quiet, the contact stays on a pipeline and the next step becomes an SMS, an email, a dialer call or a dated task on a named person's list — with the WhatsApp history attached to the same record so nobody starts cold.

Before you submit your next batch of templates, do the state exercise above: for each one, write down whether the window will be open when it fires. That single column tells you which templates are a cost centre and which are effectively free.

Then ask what happens to the contacts your templates cannot reach. If the answer is "we send another template", that is a budget with no ceiling. Book a walkthrough and bring your real template list — the interesting conversation is about the ones that keep firing at people who stopped replying. HelloGrowthCRM is ₹899 per user per month on annual billing, or ₹1,099 monthly.