Festive sale on WhatsApp without getting blocked: a Diwali send plan for D2C brands

Arjun Mehta runs a dry-fruit and gift-hamper brand in Jaipur with a team of eleven. Diwali is his biggest fortnight by a distance. His Shopify store has about 38,000 customer records. About 8,400 of those people ticked a box agreeing to offers on WhatsApp. His WhatsApp account is verified and sits at a messaging limit of 2,000 people a day.

Last year he sent the Diwali offer to everyone on the Business app, from a phone, over two evenings. This year he’s on the WhatsApp Business Platform, and the rules are different. This is the plan we’d give him.

Diwali falls on Sunday 8 November 2026, per the central government’s holiday list for 2026, which also puts Dussehra on Tuesday 20 October and Govardhan Puja on Monday 9 November. The same list notes that some states observe the holiday a day earlier, on Naraka Chaturdashi, so check where your customers are.

What decides whether your Diwali sends arrive

Your messaging limit

This is how many different people you can message outside an open chat window in any rolling 24 hours. Since October 2025 it belongs to your business portfolio, and every number in the portfolio shares it. New portfolios start at 250; verification takes you to 2,000; after that Meta moves you up to 10,000, 100,000 and unlimited on its own.

The move up happens within 6 hours once two things are true: your messages are high quality, and you used at least half your current limit in the last 7 days. At 2,000, that means reaching at least 1,000 different people in a week.

The part people forget: order confirmations and shipping updates go to people outside a chat window too, so they count against the same limit. In Diwali week, Arjun’s sale message and his order updates compete for the same 2,000.

Our messaging limits guide covers the levels in detail.

The per-person marketing cap

WhatsApp limits how many marketing templates each person receives from all businesses combined. Meta publishes no number. The cap moves with how that person reads marketing messages and how busy their inbox is. When your message is held back, it fails with error 131049.

Meta doesn’t say anything about festivals. But a cap that depends on how full a person’s inbox is will bite harder in the fortnight when every brand they’ve ever bought from sends a Diwali offer. We’d plan for more 131049 failures from late October, and treat that as a reason to send earlier and to fewer, better-chosen people.

Two rules from Meta’s page matter here. Wait at least 24 hours before trying a capped person again. And since 30 April 2026, repeated retries inside 24 hours to people who are already capped can make further attempts to them unavailable for up to a day, enforced across your whole account. Switch off any automatic retry.

One exception works in your favour: marketing templates delivered inside an open 24-hour window, after the customer has messaged you, don’t count towards the cap.

Template pacing and quality

New templates can be paced. Meta sends the first messages, then holds the rest while it waits for early feedback. If the feedback is good the rest go out; if it’s bad they’re dropped and the template is paused. Meta’s stated goal is that even paced messages arrive within an hour in 99% of cases. Separately, since December 2025 Meta delivers large campaigns in batches.

A template with low read rates or many blocks and reports gets a lower quality rating and can be paused. Quality is also one of the two conditions for your limit moving up. A Diwali template that annoys people costs you the send and the next level.

Week of 5 October: set up

Build the list first. Only people who opted in to marketing on WhatsApp, with your brand named, should get a Diwali offer. That’s Meta’s opt-in rule. For Arjun it cuts 38,000 records to 8,400, and it’s the single biggest thing he can do for his block rate.

Then split those 8,400 into segments that behave differently:

Segment	Arjun’s count	Why it’s separate
Bought a Diwali hamper last year	2,100	Highest intent; send first
Bought in the last 12 months, not at Diwali	3,300	Interested, needs a reason
Opted in, never bought	3,000	Lowest intent; one message at most

Submit the templates now. Review takes up to 24 hours, and a rejection costs a day each time. Our guide to template rejections covers the format rules. Write the offer as a marketing template and keep it out of order updates, or Meta may bill your order updates as marketing for the whole season.

Put a quick-reply button on every marketing template that lets people say no, such as “Stop offers”.

Weeks of 12 and 19 October: warm up

Send a small, useful message to the first segment: an early look at this year’s hampers, or corporate-gifting order dates. 2,100 people across a few days takes Arjun past 1,000 in a week, so his limit should move to 10,000 before the main send.

This send also puts the new templates through pacing on a group that knows the brand. Watch the read rate. If it’s much lower than your usual sends, fix the message now rather than in Diwali week.

Week of 26 October: the main offer

Send the main Diwali offer, segment by segment, over two or three days rather than in one blast.

What it costs, before GST, at ₹0.8631 per delivered message:

• Send 1, all 8,400 opted-in people: about ₹7,250.
• Send 2, a follow-up to the 3,000 who read send 1 but didn’t buy: about ₹2,589.
• Send 3, a last-order-date message to 1,500 who tapped or replied: about ₹1,295.

That’s about ₹11,134 for the season. Sending one message to all 38,000 records would cost about ₹32,800, would break the opt-in rule for most of them, and would bring the blocks that pause templates.

When customers reply, your team answers inside the 24-hour window. Since 1 October 2026 those replies are free only for the first 1,000 per number per month, then ₹0.115 each. In a busy Diwali week a single number can pass 1,000 fast. Answer in one message, not four.

Week of 2 November: last orders, then stop

Send one message about your last order date for Diwali delivery, and only to people who engaged with an earlier send. Take the date from your courier’s actual cut-off, not a hopeful guess.

Don’t send “sale ends at midnight” at 10 pm. With batching and possible pacing, part of that send can land after the offer has closed.

On Diwali itself, send nothing promotional. Order updates, yes. A greeting from a brand, in the middle of the family evening, gets muted.

Handling opt-outs and blocks

WhatsApp’s policy requires you to respect every request to stop, whether it comes through WhatsApp or anywhere else. Someone who taps “Stop offers”, or writes “please stop” in Hindi at 11 pm, comes out of every marketing segment the same day. They keep getting their order updates.

Blocks are the signal that hurts you most, and you rarely see them directly. You see them afterwards, as falling read rates and a template quality rating that drops. If a send’s read rate falls well below your earlier sends, stop the remaining segments and rewrite.

If you’re running click-to-WhatsApp ads

A chat that starts from a click-to-WhatsApp ad, where you reply within the window, opens a free entry point window of up to 7 days. Every message in it, templates included, is free. And while the customer’s 24-hour chat window is open, your marketing templates don’t count towards the per-person cap. For a Diwali hamper enquiry that takes a few days of back and forth, that window covers the whole conversation.

The checklist for this week

• Check your messaging limit and whether your business is verified
• Filter the list to people who opted in to offers on WhatsApp
• Split it into at least two segments by how recently they bought
• Submit festive templates, each with a “Stop offers” button
• Turn off automatic retries for failed marketing sends
• Put your courier’s last Diwali dispatch date in the calendar
• Decide who removes opt-outs, and how fast

Do the list filter first. Everything else in this plan depends on it.