// INSIGHTS
WhatsApp Reminder Journeys That Cut Event No-Shows
5 min read
No-show rate is the quietest way an event loses money. Catering is ordered, badges are printed, sponsors are promised a room, and 30 percent of registrations do not arrive. WhatsApp is the highest-read channel in India for this problem. But a reminder is only worth building if you can measure whether it changed attendance. Because ZebIQ runs both the messaging flows and the check-in system, each reminder can be scored against actual entry scans.
Why WhatsApp, and where SMS and email still belong
In India, WhatsApp is where transactional messages get read. Email works for the confirmation and the invoice. SMS works as a fallback and for OTP. But the day-before reminder, the venue map, the parking note and the reschedule alert belong on WhatsApp, delivered through the Business API with approved templates rather than a broadcast list on somebody phone.
Each channel carries its own compliance shape. WhatsApp Business API requires template approval and an opt-in trail. SMS in India requires DLT registration of the sender ID and the template under TRAI rules, and unregistered templates will simply not deliver. Email needs authenticated domains and a genuine unsubscribe path. We run email on Mailgun with Brevo as failover, which protects continuity during a deadline push. It does not protect inbox placement. Nobody can guarantee that, and any vendor who does is selling you something they do not control.
The practical design rule is one job per message. A reminder that also asks for a survey response, promotes a sponsor and shares a hotel discount code gets ignored. Reminders that say the date, the time, the gate and the QR code get acted on.
Typical no-show behaviour we plan around
How the journey is built
Language chosen at registration
The delegate picks Hindi, English or a regional language on the form. The whole journey then runs in that language, including the QR pass and the on-site fallback message.
Templates written for translation, not translated after
Hindi, Marathi, Tamil, Telugu, Gujarati and Arabic variants are drafted as separate approved templates. Machine translation of an English template usually fails WhatsApp review or reads badly.
Two-way handling
Replies are parsed for intent. Cannot attend triggers a release of the seat. Sending a colleague triggers a substitution flow. Silence after two reminders triggers the voice bot.
Scan-linked measurement
Every message is joined to the delegate ID. Post-event we report entry rate segmented by which messages were delivered, read and acted on.
The six-message sequence
Immediately on registration
Confirmation with the delegate name, event date and the QR pass. This message sets the WhatsApp thread that every later message rides on.
T minus 7 days
Agenda highlights and a single confirm or cancel button. Cancellations here are valuable. They free seats and correct the catering count while it can still be changed.
T minus 1 day
Venue, gate number, reporting time, parking and the QR pass again. In the delegate chosen language, with a map link that opens in the native maps app.
Event morning and T plus 2 hours
A short morning nudge, then a follow-up to registrants who have not scanned in. That second message is where a measurable share of the recovery happens.
What usually goes wrong
Template approval is the most common schedule risk. WhatsApp template review takes time, and promotional-sounding language gets rejected. If templates are submitted four days before the event, some of them will not be live in time. We submit at least two weeks out and keep an SMS fallback that is already DLT-registered.
The second problem is over-messaging. Nine reminders do not beat six. They produce blocks and opt-outs, and a blocked number cannot be recovered before the event. The third is data hygiene. Numbers entered without a country code, landlines typed into a mobile field and duplicate registrations from the same person all degrade delivery. We validate at the form rather than at send time. Finally, be clear about what reminders cannot do. If the event is in the wrong city for your audience, on a poor date, or the agenda has weakened since registration, no reminder journey fixes that. Messaging recovers attention. It does not manufacture intent.
Common questions
Do we need explicit opt-in for WhatsApp?
Yes. Opt-in is captured on the registration form with clear language about what will be sent and how to stop. That record is stored against the delegate ID with a timestamp. It is required by WhatsApp policy and it is the sensible position under the DPDP Act.
Which regional languages can you actually run?
Hindi, Marathi, Gujarati, Tamil, Telugu, Kannada, Bengali and Punjabi are the ones we deploy most often, plus English and Arabic for UAE editions. Each is a separately drafted and separately approved template set. We use human review on every language before submission because a badly worded reminder in a delegate mother tongue does more damage than an English one.
How do you prove the reminders worked?
We compare entry-scan rates across registrants who received and read the sequence against those who did not, holding registration source constant. It is a comparison, not a controlled trial, and we label it that way. On repeat editions the year-on-year no-show comparison is usually the more convincing number.
Cut your no-show rate before the next edition
Send us last year no-show number and we will design the reminder journey against it.
