Be Live on WhatsApp Before Diwali: The Real Timeline

Every year, the same story plays out across Tamil Nadu’s retail district.

A showroom owner decides, sometime in October, that this year he’s finally going to run Diwali properly on WhatsApp. He calls a vendor on October 15th. The vendor says setup takes a week. The owner assumes he’ll be live by October 22nd — two weeks before Diwali, plenty of time.

What he doesn’t know: Meta Business Verification alone takes two to three weeks if the first submission is clean, and longer if there’s a document issue. He submits the verification on October 16th. He gets a rejection notice on November 1st — a name mismatch between his GST and his Meta account. He resubmits on November 3rd. Diwali is November 4th.

He spends Diwali the same way he spent it last year: forwarding the sale image by hand from the counter phone, broadcasting to WhatsApp groups, watching the rival showroom three doors down — the one that started in September — sending a professional broadcast to their opted-in list of six thousand people.

This is not a horror story. It’s the standard story, and it happens because the timeline has specific steps that don’t compress, regardless of how much anyone rushes.

Want to be live for Diwali 2026? Send “Hi” to +91 96009 59581 on WhatsApp now. The window is open; it won’t be for long.

The actual steps and how long they take

These timelines are realistic, not optimistic. The “best case” scenario assumes a clean first submission on every step. Build your plan around the realistic scenario.

Step 1: Meta Business Verification

Before you can use WhatsApp Business API for broadcasts, Meta verifies that your business is a real, operating entity. You submit documents — your GST certificate is the most reliable for Indian businesses — and Meta’s systems review them.

Best case: 5-7 business days. Realistic case: 2-3 weeks. If rejected and resubmitted: 2-3 more weeks.

The most common rejection trigger is a name mismatch — the business name in your Meta Business Manager doesn’t match exactly the name on your GST. Check this before you submit. A document that’s hard to read, too dark, or photographed at an angle also delays the process.

Step 2: WhatsApp number setup and phone number verification

Once Meta Business Verification clears, your WhatsApp Business Account (WABA) is created and your number is connected. This step is relatively fast when the verification is in place — usually a day or two.

Step 3: Message template submission and approval

You cannot broadcast anything until you have at least one approved template. Templates go through Meta’s review process — automated first, then human review if flagged.

Best case: 24-48 hours. Realistic case: 3-7 days. If rejected and resubmitted: another 3-7 days.

Submit more than one template simultaneously. If the Diwali offer template gets rejected, you don’t want to be waiting for the next submission before you can send anything. Have your utility templates (order confirmations, reminder messages) submitted and approved separately from your marketing templates.

Step 4: Testing and warm-up

A brand-new WhatsApp number doesn’t behave the same as an established one. Meta’s systems are more cautious about new numbers sending large volumes. Sending your first broadcast to ten thousand people on Day 1 of a new account is how accounts get restricted on Day 2.

Warm-up involves sending to small batches first — a few hundred, then a few thousand, over days or weeks — to establish the number’s reputation with Meta’s systems. This isn’t a vendor invention; it’s how Meta’s quality-rating system works.

Realistic warm-up for a clean launch: 2-3 weeks before the number is stable enough to handle a full Diwali-scale broadcast without risk.

Step 5: List opt-in and preparation

The people you broadcast to need to have opted in. If the billing system has ten thousand numbers and none of them have been through an opt-in process, the first outreach needs to be the opt-in message — “Hi, this is [Shop Name], we’d like to send you updates. Reply YES to subscribe.” Running that, waiting for responses, and cleaning the list takes a week to two weeks before the first real campaign can go out.

The deadline math

Starting September 1st:

Weeks 1-3 (Sep 1-21): Verification submission and wait. If clean, clears by September 21st. Week 3-4 (Sep 22-30): Number setup, template submission. Templates approved by end of September. Weeks 4-6 (Oct 1-14): Warm-up sends, opt-in collection, list preparation. By mid-October, list is ready and number is healthy. Weeks 5-6 (Oct 15-31): First targeted campaigns — the weeks before Diwali when the purchase decision is being made. Diwali week (early November): Full broadcast to warm list, confirmed opt-ins, healthy account standing.

Starting October 15th: Verification clears early November at best. You have Diwali week with a cold list, an untested number, and no warm-up time. In practice, you are broadcasting to strangers from a new account — the setup that gets accounts restricted.

Starting October 25th: You will not be live for Diwali. This is not a maybe; it’s arithmetic.

The template rejection that kills Diwali

There’s a specific failure mode in the October-start scenario that deserves its own mention.

The shop that submitted verification on October 16th, cleared it on November 1st, and immediately submitted a Diwali marketing template on November 1st — that template is rejected on November 3rd because it contains the phrase “guaranteed lowest price” or because the linked URL is HTTP instead of HTTPS.

They resubmit November 3rd. The revised template is approved November 5th. Diwali was November 4th.

The shop that started in September submitted their Diwali template in late September as a precaution. It was rejected on a minor issue, fixed and resubmitted immediately, and approved by October 10th. Three weeks before Diwali, they had an approved template, a warm number, and a growing opt-in list. When the first of November came, they weren’t checking the approval status. They were looking at reply rates.

This is why the template step is inside the September timeline, not an afterthought. A rejected template in September gives you time. A rejected template on November 1st gives you nothing.

What the shop that started in September did differently

The rival showroom three doors down — the one running the proper Diwali broadcast — spent September on verification and setup. They spent October collecting opt-ins, warming the number with smaller broadcasts, and running the first engagement campaigns: “New Diwali collection preview — reply if you’d like to see photos.” By November 1st, their list had already replied to two messages from the same number. The Diwali broadcast went to people who were already in a conversation with the shop.

Their Diwali broadcast was not their first broadcast to that list. It was their fourth.

For the verification step specifically: Meta Business Verification for Indian Shops: Step by Step.

For the cost to budget against in each phase: What WhatsApp Business API Actually Costs in India.

For Coimbatore shops specifically — the full local season from Aadi through Diwali: WhatsApp Business API in Coimbatore: A Local Guide.

The short version

• Meta Business Verification: 2-3 weeks, longer if rejected.
• Template approval: 3-7 days per submission.
• Warm-up: 2-3 weeks for a new number to be stable at scale.
• Opt-in collection: 1-2 weeks.
• Total realistic timeline from “I’ll start now” to “ready for a full Diwali broadcast”: 8-10 weeks.
• Start by September 1st. Start by August if you want breathing room.
• Starting in October means not being properly live for Diwali. This is arithmetic, not pessimism.

Send “Hi” to +91 96009 59581 on WhatsApp today. Every week of delay in August is a week of warm-up time you don’t have in October.