Plan around the actual Mumbai Navratri dates.
Mumbai's 2026 Shardiya Navratri begins on Sunday, October 11, with Navratri continuing through Monday, October 19. Dussehra is Tuesday, October 20.
This guide works for very different businesses: a garba organiser in Borivali, a builder's office in Andheri inviting prospects to a festive property event, or an Indian grocery in New Jersey running a Navratri customer evening. The common problem is the same: you have a list of people to contact, but not enough time to call each person properly.
Use your event's own programme as the source of truth.
Festival dates and local observances can vary by region or community. The dates above are the 2026 Mumbai calendar dates; the date, venue, timing and ticket information in your calls must match your published event details.
Before the event: build the calling list.
Start with a clean audience list. The objective is not to call everybody with the same message. It is to give each group a reason to take the next step.
Split the database by intent.
Create separate lists for past attendees, new leads, registered guests, VIPs, sponsors and people who started registration but did not finish.
Call past attendees with a specific reason to return.
Mention the actual offer: early-bird pricing, a new venue, a performer, a family pass or a particular garba night.
Follow up unfinished registrations the same day.
Ask whether the person had a question about tickets, timing or payment. Resolve the blocker instead of starting another generic sales pitch.
Segment Mumbai audiences by location.
A person in Borivali may care about parking and western-suburb access. Someone in Ghatkopar may need different travel information.
During the campaign: make every call useful.
One call should move the customer somewhere.
The useful outcome can be a registration, a callback, an answer to a question, a written follow-up or a human transfer. Avoid calls where the only measurable outcome is “information shared.”
Use one clear offer.
State the event name, date, location and one reason to attend within the first 15 seconds.
Let the customer choose.
Ask whether they want a single-day pass or an all-nine-days pass, rather than delivering a long monologue.
AI calling can do this
Troika Tech supports 9+ Indian languages. Design the conversation around the languages your audience actually uses and allow a human handoff for questions outside the approved information.
- Invitation calls
- Registration qualification
- Ticket FAQs
- Venue and parking information
- Callback capture
- Human transfer for exceptions
Use the final week for confirmations, not generic blasts.
The closer the event gets, the more specific the call should become. Someone who booked October 15 does not need a generic “Navratri starts tomorrow” message.
Confirm
Call 48–72 hours before the customer's booked date.
Answer
Give entry time, parking, venue and ticket information.
Fill
Contact warm leads when genuine ticket capacity remains.
Follow up
Ask no-shows and attendees for the next useful action.
Confirm booked attendees 48–72 hours before attendance.
Confirm the date, entry time and important rules. Flag uncertain responses for follow-up.
Run a separate reminder for each booked night.
If the customer booked October 15, the call should clearly refer to October 15.
Call the waitlist when tickets open.
Keep the preferred date, number of passes and preferred language against each person.
Use the final 24 hours to fill genuine gaps.
Contact people who previously showed interest in the specific night where tickets remain.
Do not let the event database expire on October 20.
09 — Call no-shows.
Ask whether they want information about another Navratri night, a future event or next year's early registration. Do not pretend they attended.
10 — Ask one feedback question.
“How would you rate the event from 1 to 5?” is easier to answer than a long survey. Ask one optional improvement question.
11 — Tag every call outcome.
Use fixed outcomes: Interested, Registered, Callback, Wrong Number, Not Interested, No Answer and Human Follow-up.
Measure registrations, not just calls.
A calling campaign can generate thousands of conversations and still fail to sell tickets. Your dashboard should connect calls to outcomes.
Connection rate
Track total calls, answered calls and meaningful conversations.
Conversion
Track interested callers, registrations and revenue attributed to the campaign.
Cost
Compare campaign spend with registrations and meaningful conversations, not activity alone.
Example planning calculation
If your campaign is budgeted around ₹10–₹12 per minute and 1,000 calls average 45 seconds, that is 750 minutes of talk time, or roughly ₹7,500–₹9,000 before any other applicable charges. Actual spend depends on real call duration and your provider's pricing.
| Metric | What to record | Why it matters |
|---|---|---|
| Total calls | Every attempted call | Shows campaign reach. |
| Connected calls | Answered conversations | Shows actual contact. |
| Interested | Positive intent | Shows lead quality. |
| Registrations | Confirmed bookings | Shows the outcome that matters. |
| Callbacks | Requested follow-ups | Prevents warm leads from being lost. |
| Cost per registration | Campaign spend ÷ registrations | Lets you compare channels. |
AI calling vs human telecalling vs WhatsApp and SMS.
These channels do different jobs. For a festival campaign, a sensible workflow can use voice for attention and conversation, followed by a written message containing the exact details.
| Need | AI calling | Human telecalling | WhatsApp / SMS |
|---|---|---|---|
| First-touch invitation | Strong | Strong | Useful |
| Two-way conversation | Yes | Yes | Limited |
| High-volume repetitive calls | Strong | Team-dependent | Not applicable |
| Complex negotiation | Transfer | Strong | Possible |
| Detailed written information | Follow-up | Follow-up | Strong |
| Registration reminders | Strong | Strong | Strong |
The Mumbai Navratri calling planner.
Screenshot this section. Work down the rows and assign one owner to each action. The exact campaign start date should depend on your event date and sales cycle.
| Stage | When | Concrete action | Desired outcome |
|---|---|---|---|
| 01. Prepare | Before launch | Clean duplicates and divide past attendees, new leads, registered guests and VIPs. | A usable calling list. |
| 02. Script | Before first call | Write the invitation and answers for price, venue, parking, timing and tickets. | Consistent answers. |
| 03. First outreach | 2–3 weeks before your event | Call past attendees and warm leads with the actual offer. | Interest and callbacks. |
| 04. Lead follow-up | Within 24 hours of a new enquiry | Call people who submitted an enquiry or abandoned registration. | Registration or a clear reason for not registering. |
| 05. Registration push | 7–10 days before the relevant night | Call interested but unregistered people. | Paid or confirmed registrations. |
| 06. Confirmation | 48–72 hours before attendance | Confirm date, ticket quantity, venue and key entry information. | Fewer avoidable attendance problems. |
| 07. Final fill | 24 hours before a specific night | Contact warm leads or waitlisted people if genuine capacity remains. | Fill available tickets. |
| 08. Event day | Booked event date | Use only essential reminder calls and avoid unnecessary promotional calls. | Smoother arrival. |
| 09. Feedback | 24–48 hours after attendance | Ask for a simple rating and one improvement point. | Actionable feedback. |
| 10. Retention | After October 20 | Tag attendees and interested non-buyers for future events. | A clean audience for the next campaign. |
2026 date check
Shardiya Navratri begins October 11, 2026. October 19 is listed for Durga Ashtami/Maha Navami, and October 20 is Dussehra. Your event may follow a different programme, so verify your organiser's final schedule.
What others do.
IIT Delhi Alumni Day
Dograh documented an alumni invitation campaign where voice AI was used primarily for RSVP, with WhatsApp and email carrying detailed information afterward.
Lesson: use the call to get a decision, then use a written channel for the details.
Mumbai business and MICE hotel
Kallix describes an AI voice agent handling corporate booking and event enquiries in Hindi and English, including after-hours enquiries and follow-ups.
Lesson: build the agent around real event questions and booking actions.
Large Asian hospitality operation
Iconflux describes an AI voice agent handling 2,500–3,000 enquiries per day for accommodation and tour packages around major events.
Lesson: automate repetitive first-touch qualification when enquiry volume overwhelms the sales team.
Copy-paste this 30-second call.
Replace the brackets with verified information. Do not let the caller invent venue, price, ticket or event details.
Agent: “Hello [Name], this is calling from [Business]. We are inviting you to our Navratri celebration on [Date]. This year's [Offer] is available for a limited number of registrations. Would you like me to share the details?”
Customer: “Yes, tell me.”
Agent: “[Business] is hosting the event at [Venue] on [Date], with entry from [Time]. [Offer] includes [brief benefit]. Would you like to register for it?”
Customer: “No, not interested.”
Agent: “No problem, [Name]. Thank you for your time. I won't take any more of your time. Have a good day.”
Customer: “Maybe. Call me later.”
Agent: “Certainly. What time would be convenient for a callback?”
Where AI calling fits
Troika Tech can run the repeatable first-touch conversation, capture the response and trigger the next step according to your campaign rules. Keep sponsorships, bulk bookings, complaints and unusual requests on a human-transfer path.
Ready-to-run checklist.
- Your 2026 event dates, venue, entry time, ticket price and offer are final.
- Your database is divided into past attendees, new leads, registered guests and follow-ups.
- Your script answers price, parking, venue, timing, tickets and basic event questions.
- Every call has a defined outcome: registration, callback, not interested or human follow-up.
- Your campaign has a human-transfer rule for sponsorships, bulk bookings and exceptions.
- Your commercial-calling process has been checked against applicable TRAI requirements and customer consent rules.
Frequently asked questions.
Yes. An AI calling agent can make invitation and follow-up calls, answer predefined event questions, qualify interest and pass suitable callers to a person. For a Mumbai event, the useful part is the ability to run the same structured conversation across a large list without asking your sales team to make every first call manually.
Shardiya Navratri begins on October 11, 2026. In the Mumbai calendar, October 19 is listed for Durga Ashtami/Maha Navami and October 20 is Dussehra. Garba and dandiya event schedules can run according to the organiser's programme, so publish and call using the exact dates of your event.
You give the agent your approved event information, audience list and call objectives. It calls the relevant people, holds a conversation, records the outcome and can trigger the next action, such as a callback, written follow-up or human transfer.
Troika Tech supports 9+ Indian languages. The exact language mix and conversational behaviour should be tested with your target audience before the campaign goes live, especially where people switch between languages during a call.
AI calling in the Indian market can be budgeted around ₹10–₹12 per minute, with per-second billing making actual spend dependent on call duration. For example, 1,000 completed calls averaging 45 seconds would represent 750 minutes of talk time, or roughly ₹7,500–₹9,000 at that planning range, before any other applicable charges. Verify your actual provider quote before setting the campaign budget.
It depends on the job. AI is useful for repetitive first-touch calls, reminders, qualification and follow-ups at scale; people are still better suited to negotiations, sponsorships, complaints and unusual requests. A practical campaign uses AI for the repeatable layer and humans for exceptions.
You should not treat an AI voice campaign as exempt from telecom commercial-communication rules. TRAI states that commercial communications are subject to requirements around registered senders, templates and customer consent, and defines unsolicited commercial communication to include unwanted voice calls. Check the current TCCCPR requirements and your telecom provider's process before launching a promotional campaign.
Turn one event date into a working call plan.
Start with one audience, one event date and one clear offer. If you want Troika Tech to run the repeatable calling layer, its fully managed AI calling can be set up for a campaign and is described as going live in 3–7 days. Use your final event information, consent records and approved script as the source of truth.
Review the plannerFestival dates should be verified against the organiser's final programme. Telecom commercial-communication requirements should be checked against current TRAI guidance before launch.