The Festival Rush: What Your Guest WiFi Has to Survive, and What It Should Keep
Janmashtami to Diwali is the densest stretch of foot traffic most Indian venues see all year. It tests two different things at once: whether the network holds, and whether you keep anything from the crowd once it goes home.
From Janmashtami through Ganesh Chaturthi, Navratri, Durga Puja and on to Diwali, most Indian venues see the densest stretch of foot traffic in their year. A cafe near a temple, a hotel taking Mathura and Vrindavan traffic, a restaurant on Dahi Handi evening, a mall in the week before Diwali: for six or seven weeks, the room is fuller than it has been since last season, and almost everyone in it is new.
That rush tests two completely different things, and most owners only think about the first one. The network has to hold under a crowd it has never carried. And the business has to keep something from a room full of people it will otherwise never see again.
Test one: a crowd the network has never carried
The uncomfortable thing about festival load is that it doesn’t scale gently. A cafe that comfortably runs thirty devices on a normal evening isn’t asked to handle forty on the big night, it’s asked to handle a hundred and twenty, most of them arriving inside the same two hours, most of them on video calls to relatives or uploading photos.
Two failures show up at exactly that moment, and they look identical to a guest.
The first is that the connection is genuinely saturated: more devices than the line and the access points were sized for, so everything slows to a crawl at once. This is a planning problem more than an equipment problem, and it’s worth doing the arithmetic before the season rather than during it, both on how much bandwidth the room actually needs and on how many access points that floor really takes. A venue that has never measured its normal peak has no way to guess its festival peak.
The second is subtler and more common: nothing is saturated, but a handful of devices are eating the whole line, so the other ninety people get nothing. That is what per-session limits exist to prevent — not to be stingy with guests, but so that one person’s cloud backup doesn’t quietly become everyone else’s outage. The related trap is assuming an unlimited user count means unlimited capacity; it doesn’t, and the difference between those two things is usually discovered on the busiest night of the year.
And if the line itself drops during that window, the cost isn’t measured in minutes. It’s measured in the number of people who were in the room at the time, which on a festival night is the highest it will be all year — which is the whole argument for a backup connection that switches over on its own rather than a staff member noticing and calling the ISP.
Test two: everyone in the room is a stranger
Here is the part that gets missed. On an ordinary Tuesday, a good share of the room is regulars — people you already know, who will come back without being asked. On a festival night, most of the room has never been to your venue before and, statistically, will never come again. They came for the festival, not for you.
That is the actual opportunity, and it has a short shelf life. A hundred and twenty people walked in, used your WiFi, spent money, and walked back out as complete strangers. Nothing about them is recorded anywhere you can reach. Next month, when business is quiet, there is no way to tell any of them that you exist.
A branded login is what changes that arithmetic, because the connection already requires an action from the guest. When someone logs in with an OTP, you end up holding a phone number that has been verified in the only way that counts: a code went to it and came back correctly. Over one festival season, that turns a crowd into a customer record you own rather than rent — built out of normal foot traffic, with nobody at the counter asking anyone to join a list.
The important distinction, and it matters more in a rush than at any other time: verified is not the same as marketable. A number collected so someone could get online was collected for that purpose. Sending that number a promotion later is a new purpose that needs its own clear opt-in, offered at the login screen, separate from the connect button, refusable without losing the WiFi. India’s DPDP rules are specific about this, and a festival is precisely when a venue is tempted to be sloppy, because the numbers are flowing in faster than they ever have.
The login has to be fast on the one night it can’t afford to be slow
A login flow that works fine for eight guests an hour can fall apart at eighty. The usual culprit is SMS. Delivery gets slower under load, DND settings block a share of it outright, and a guest standing in a crowded room with a slow phone gives up in about twenty seconds. That is the single strongest practical argument for WhatsApp OTP over SMS on high-traffic nights: it lands in an app the guest already has open, and it doesn’t depend on operator queues on the busiest evening of the quarter.
It also helps to have a second path that doesn’t depend on any message arriving at all. For a booked event, a wedding block, a corporate Diwali party or a puja gathering, printed vouchers handed out at the door get a whole group online without anyone waiting for a code, and they still record who connected and for how long. That is the same machinery that makes bulk access for events workable rather than chaotic.
What you get to do afterwards
The follow-up is where festival footfall either pays off or evaporates, and the temptation is to do the wrong thing immediately: blast every number collected in September with a Diwali offer. That burns the list, and it can get a WhatsApp sender’s quality rating throttled fast — the platform’s rules and the law are pointed in the same direction here. The workable version is narrower: message only the people who opted in, send rarely, and make each message specific enough that the recipient is glad it arrived.
The good news is that festival timing does half the work. A guest who visited during Navratri is a genuinely sensible person to tell about your Diwali menu six weeks later, and one message like that, sent to people who agreed to hear from you, is worth more than a season of generic promotions.
What a busy season doesn’t fix
None of this rescues a network that was already marginal. A festival crowd doesn’t create new problems so much as expose the ones a quiet room was hiding: an access point in the wrong corner, a line that was always undersized, a login nobody has actually stood in a queue and tried. Every one of those is cheaper to find in the week before the season than in the middle of it.
If you are going into this stretch with an unbranded router page and no idea what your peak actually looks like, the useful order is: measure the normal peak, size for three or four times it, put a login in front of the network that verifies a number and asks a clean opt-in, and only then think about what you’ll send afterwards. Wyfy Guest runs that whole chain — the branded login, the OTP, the failover behind it, and the campaign at the other end — as one managed setup, which mainly means there is one place to look when the room is full and something needs checking.
