WhatsApp CRM for Retail and D2C

A retail brand sends two fundamentally different kinds of WhatsApp message, and Meta prices them differently.

Utility messages relate to a transaction the customer has already made: order received, payment confirmed, packed, dispatched, out for delivery, delivered, return picked up. These are free inside an open customer service window and charged outside it.

Marketing messages promote something: a sale, a new drop, a festive offer, a cart the customer abandoned. These are always charged when sent, with no free window.

There are two other categories worth knowing. Authentication templates — login and verification codes — behave like utility: free inside an open window, charged outside it. Service messages are ordinary free-form replies; they are free, but can only be sent inside an open customer service window.

The rule that catches brands out is this: the category Meta applies to the template at the time of use determines the charge — not the category you intended. Write what you consider a dispatch update, attach "and here's 10% off your next order", and you have written a marketing message. You will be billed accordingly, and you cannot appeal it after the send.

That single sentence is the discipline this page is about. Keep transactional templates transactional.

Retail is unusual in that its highest-volume messaging is also its cheapest, provided you sequence it correctly.

The economics turn on the customer service window: 24 hours, opened or refreshed by the customer replying to you. Inside it, your utility templates are free and your agents can send ordinary free-form messages at no cost. Outside it, every utility template is charged.

That has a practical consequence for how order journeys are designed. A customer who replies to your order confirmation — even with a thumbs up, even with a question — opens a window in which the next few updates are free. Meta's own guidance for the window is to prompt the user to reply in order to activate it. So an order confirmation that ends with a genuine reason to respond ("reply CHANGE if the delivery address needs correcting") is not a copywriting flourish; it is a billing decision.

The sequence most Indian retailers actually need

• Order confirmed — immediately, with a reply prompt
• Dispatched, with tracking
• Out for delivery
• Delivered, with a reply prompt for issues
• Return or exchange status, if raised

Anything beyond that is marketing wearing a delivery van's uniform, and it will be priced as marketing.

Festive season is where retail WhatsApp spending concentrates, and where two mistakes compound.

The first is treating volume as available on demand. Your messaging limit is the number of unique recipients you can message outside a customer service window in a rolling 24 hours. New business portfolios start at 250. The next tier is 2,000, reached by completing Meta's scaling requirements and passing message-quality analysis, after which the limit is raised immediately. Above 2,000 it scales automatically, but only when message quality stays high across all your numbers and templates and you have used at least half your current limit in the last seven days.

A brand that sends nothing for ten months and then wants to reach 50,000 customers in Diwali week fails the usage condition and arrives at the season stuck. Build the tier through the quiet months.

The second is putting offers into the transactional stream because it looks free. It is not free, and the reclassification is decided by Meta.

One legitimate cost advantage is worth using: conversations opened from Click-to-WhatsApp ads are a free entry point, giving 72 hours in which all messages are free. For a D2C brand already spending on paid social, routing a festive creative into WhatsApp is the cheapest way to open a large number of conversations.

For current rates, see Meta's pricing documentation (checked 19 August 2026). We do not publish a rupee rate table, because Meta revises those rates and a stale table would mislead your budget.

The order journey ends. The customer stops replying. The window closes.

At that point, every remaining intention you have towards that customer — win them back, tell them their size is restocked, ask why they returned — is a marketing template, charged each time, sent to someone who has already gone quiet. Repeat that across a lapsed customer base and you are paying per message for exactly the audience whose reaction Meta is measuring.

This is the structural end of a WhatsApp-only retail stack. The tool has not broken. It has run out of channel.

WhatsApp tools automate inside WhatsApp. HelloGrowthCRM continues the sequence off it.

When a customer's window closes, the contact stays on a pipeline rather than in an inbox. The sequence carries on where there is no messaging window: an SMS, an email with the restock or the offer, a dialer call for a high-value buyer, and a dated task for a named person on wholesale or repeat accounts. The WhatsApp thread stays attached to the same record, so nobody restarts the conversation from zero.

Stated plainly about us: WhatsApp broadcasts are available as Campaigns on tier 2 and above, not on every plan. A free plan exists. Production runs on AWS Tokyo, so any claim you read of Indian data residency for us would be wrong.

Take last month's WhatsApp sends and sort them into two columns: transaction and promotion. If anything sits in both, that is the message quietly repricing your bill.

HelloGrowthCRM is ₹899 per user per month on annual billing; monthly is ₹1,099. Book a walkthrough and bring your order-update templates — the split is easiest to see on your own copy.