📋 Playbooks

Navratri and Garba events: ticketing and attendee support on WhatsApp

Updated 2026-09-19 · 4 min read · By the Convo360 team

In short

Event ticketing on WhatsApp for Navratri and Garba works by selling passes through a chat flow with a Razorpay payment link, adding buyers to an attendee group for daily reminders and entry updates, answering entry-rule and parking FAQs automatically, and letting attendees recover a lost digital pass without calling the organiser.

Key takeaways
  • Sell single-night and season passes directly in chat with a Razorpay payment link.
  • Add every buyer to an attendee group for daily reminders through the event run.
  • Automate entry-rule FAQs (dress code, timing, parking) so the team is not repeating them daily.
  • Let attendees retrieve a lost digital pass through the bot instead of a help desk queue.
  • Send a same-night feedback prompt after the final day to gauge interest in next year's event.

Why WhatsApp works well for multi-day festival events

Navratri and Garba events typically run for multiple consecutive nights, with attendees buying single-night or full-season passes, needing daily reminders, and asking repetitive questions about entry rules, timing and parking. WhatsApp's combination of payment links, group messaging and an FAQ bot covers the whole lifecycle from sale to entry to lost-pass recovery, without a separate app or portal.

Organisers running these events, whether a housing society, a cultural association or a commercial event company, typically manage this with a small volunteer team across nine nights. Automating pass sales, reminders and FAQs is what lets a small team handle a large attendee base without hiring temporary help just to answer the same handful of questions each evening.

Selling passes through chat

On Convo360's Flow Builder, the whole pass-selling sequence below is drag-and-drop, no code needed.

  1. Trigger the flow from a keyword like 'pass' or 'Navratri', or a Click-to-WhatsApp ad.
  2. Use a List Menu to show pass types: single night, three-night bundle, full nine-night season pass.
  3. Capture buyer name and preferred entry gate with Ask a Question.
  4. Send a Razorpay payment link for the selected pass.
  5. On confirmed payment, send a digital pass (QR or code) via Send Media, and add the buyer to the event's Add to Group for updates.

Many Navratri bookings are for a group of friends or a family rather than a single individual. Add a quantity step to the pass-selection menu so one buyer can purchase multiple passes in a single transaction, and generate a separate QR or pass code per person rather than one shared code, which avoids confusion and disputes at the entry gate when a group arrives together but needs to scan in individually.

Ask for each attendee's name alongside quantity where your entry process checks ID, so the digital pass can carry the correct name per person rather than one buyer's name applied to every pass in the group.

Daily reminders and entry updates

Once buyers are in the attendee group, a Wait / Delay sequence can send a same-day reminder each event evening with entry time, gate assignment and any last-minute changes (weather, timing shift). This keeps the whole audience informed without individually messaging hundreds of buyers each night.

Where multiple entry gates exist, capturing a preferred gate at the time of booking, and mentioning it consistently in reminders, spreads arrivals more evenly than leaving everyone to pick whichever gate they see first. If your venue has a capacity limit, tie ticket sales to a running count using a Condition block on total passes sold, so the flow automatically stops selling once a safe capacity is reached rather than relying on manual tracking during a busy sales period.

Automating entry-rule and logistics FAQs

Dress code, couple versus stag entry rules, parking availability and re-entry policy are asked repeatedly across a multi-night event. Build these into a guided (no-AI) bot menu or an AI Reply step scoped to your event rules document, so the volunteer desk is not fielding the same five questions on loop every evening.

Beyond Navratri and Garba, the identical structure, pass sales, an attendee group, an FAQ layer and lost-item recovery, works for other ticketed cultural gatherings through the year: a Ganesh Chaturthi pandal event with paid entry, a New Year's Eve function, or a local mela. Building this once as a reusable flow template means each new event only needs updated dates, pricing and FAQ content rather than a rebuild from scratch.

Handling a lost pass

  1. Add a 'Lost my pass' option to the main menu.
  2. Verify the buyer using their registered phone number, which is already tied to their purchase record.
  3. Resend the digital pass via Send Media automatically once verified.
  4. Flag repeated lost-pass requests from the same number for manual review to prevent misuse.

The chatbot handles sales, reminders and routine FAQs, but a multi-night event still needs volunteers at the gate for physical entry checks and handling genuine exceptions. Give volunteers a simple way to flag unusual situations, a disputed entry, a payment dispute, back into the same system, for example by messaging a dedicated staff WhatsApp number that routes into live-chat team inbox, so exceptions are logged in one place rather than handled verbally and forgotten.

Closing the loop after the event

On the final night or the morning after, send a short feedback prompt with Buttons for a quick rating, and capture interest for next year's early-bird pass list. This turns a one-time event contact list into a warm base for next season's campaign, without needing to rebuild it from scratch.

The attendee group built for daily reminders becomes a genuinely warm audience once the event closes, people who already paid and showed up, not cold leads. A short early-bird message sent a few months ahead of next year's event, offering a modest discount to last year's attendee group specifically, often converts noticeably better than a fresh promotional push to an unfamiliar audience the following season.

Keep this group tagged separately from your general contact list so the early-bird offer stays exclusive to genuine past attendees, and avoid over-messaging them outside the event season, a single well-timed early-bird nudge works better than repeated touches through the rest of the year.

Step by step

  1. Build the pass-selection menuOffer single-night, multi-night and season pass options via a List Menu.
  2. Capture buyer details and paymentCollect name and entry gate preference, then send a Razorpay payment link.
  3. Deliver the digital passSend the QR or pass code automatically on confirmed payment and add the buyer to the attendee group.
  4. Schedule daily remindersSet up a Wait / Delay sequence for same-day entry reminders through the event run.
  5. Add an entry-rules FAQBuild a menu or AI Reply step for dress code, timing and parking questions.
  6. Enable lost-pass recoveryLet attendees verify by phone number and receive their pass again automatically.
  7. Collect feedback and next year's interestSend a short rating prompt and early-bird interest capture after the final night.

Example conversation

I lost my QR code for tonight, can you resend it?
No problem, I've found your season pass under this number and resent the QR code. Gate 2 opens at 7 PM, see you there!

Sell your event passes on WhatsApp

Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.

Frequently asked questions

Can I sell both single-night and season passes through the same flow?

Yes, a List Menu with pass options, single night, multi-night bundle, full season, branching into their own payment link and confirmation steps handles multiple pass types within one flow, so buyers never need a separate link for each option.

How do I prevent one QR code being shared and reused by multiple people?

Pair the digital pass with your gate scanning process so a used QR is marked and flagged if presented again; the chatbot handles issuing and resending, not physical entry validation.

Can the attendee group be used for something other than reminders?

Yes, you can also share safety information, weather updates or last-minute schedule changes to the same group, keeping all event communication in one place instead of texting individual buyers, and the same group becomes a warm list for next year's early-bird offer.

Is a payment link safe enough for event ticket sales?

Razorpay payment links are a standard, secure way to collect payment; the bot never asks for card numbers or OTPs directly, keeping payment handling within Razorpay's own secure page.

Does this work for other festival events, not just Navratri?

Yes, the same pattern, pass sales, an attendee group, FAQ automation and lost-item recovery, applies to any multi-day ticketed event, from a Ganesh Chaturthi pandal with paid entry to a New Year's Eve function or a local mela.

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.