24×7 support with a three-person team

A traveller's connecting flight gets cancelled at 10 pm and the only number they have is yours. Your driver in Manali can't reach a client who wandered off from the group. A client messages at 1 am asking what time the safari pickup is. None of these are emergencies, but every one of them lands on the same three phones: yours, your partner's, and whoever's covering ops that week.

That's the real question behind "24×7 support" for a small agency: not whether you can staff a call centre (you can't), but which of these messages actually needs a human awake at that hour, and which can wait till 9 am without anyone feeling ignored. Get that distinction wrong and you either burn out answering wallpaper questions at 2 am, or you sleep through something that genuinely needed you.

This post lays out a system for that distinction: a severity matrix, a per-departure WhatsApp group with a pinned emergency card, written response times from your ground handlers, and a duty-phone rotation that spreads the load across three people instead of parking it all on the owner.

The severity matrix: what earns a call and what waits

Most on-trip messages aren't emergencies. They just feel urgent to the person sending them at 11 pm. The fix is to decide, before departure, what tier each situation falls into and who's expected to respond in what window.

Tier	Examples	Response window	Who handles it
Tier 1: Emergency	Accident, hospitalisation, missing person, vehicle breakdown on a dangerous stretch	Callback within 15 minutes, any hour	Duty-phone holder, escalate to owner if unresolved in 30 min
Tier 2: Urgent	Flight/train delay that changes tomorrow's plan, hotel overbooking, lost baggage	Reply within 2 hours, 7 am–11 pm	Duty-phone holder
Tier 3: Routine	"Flight kab hai", weather, restaurant asks, general itinerary questions	Reply by 9 am if received after 9 pm	Whoever's rota'd that day

Print this matrix and stick it above the desk, or pin it in your internal ops group. The point isn't precision. It's that everyone, including the client-facing team member answering at midnight, knows in ten seconds whether to wake someone up or reply in the morning.

Careful: Don't let clients see the matrix language ("Tier 3, reply by 9 am"). It reads as bureaucratic and cold. Internally you triage by tier; externally, every message still gets a warm, prompt-feeling reply. The client should never sense they were sorted into a queue.

Build the per-departure WhatsApp group before you sell the seat

Every departure, whether it's two people on a Kerala honeymoon or twenty on a Ladakh fixed departure, gets its own WhatsApp group, created the day the booking is confirmed, not the day before departure. This does two things: it becomes the single channel where a duty-phone holder can see the full trip context instead of hunting through personal chats, and it lets you set expectations early instead of explaining rules mid-crisis.

Set the group rules on day one, pinned as the first message:

1. This group is for trip logistics and emergencies only. General questions go to the office number.
2. Tag @admin (or whoever's on duty) for anything urgent; don't assume someone's watching every message.
3. No forwards, no group games, no unrelated links. Keep it usable when someone actually needs to find the SOS card fast.
4. The group stays open until 48 hours after the trip ends, for lost-item and feedback follow-up, then it's archived.

A clean group with clear rules is also what makes the pre-trip documents checklist actually land: clients read pinned messages in a group they trust isn't going to spam them.

The emergency contact card every traveller should have pinned

Alongside the group rules, pin a single-image-free, plain-text card with every number a traveller might need mid-trip. Keep it to one message so it's easy to screenshot and forward to a family member back home.

A working card includes:

• Duty-phone number (the one number that's always live, see below), labelled "call this for anything urgent, any hour"
• Local driver/guide's direct number for that specific leg
• Nearest hospital or a 24-hour clinic near the first two nights' stay
• Travel insurance helpline and policy number, if you've sold one
• For outbound trips: nearest Indian embassy or consulate contact
• Office landline, for anything genuinely non-urgent

This card costs you nothing to prepare once and reuse per destination. It's a template, not a per-trip research task. The value is that a traveller under stress doesn't need to scroll back through a week of itinerary messages to find a number; it's pinned, it's the first thing they see when they open the group.

Get it in writing: SLAs with your ground handlers and DMCs

Your own duty-phone can only move as fast as the ground handler or DMC actually supplying the vehicle, guide, or hotel room. If a driver goes silent at midnight in a hill town, you can't fix that from your bed in the plains. You need your local partner to have already committed to a response time.

Before the season starts, get a written SLA (even a WhatsApp message confirming it counts) from every ground handler and DMC you rely on:

• Maximum response time for a breakdown or no-show report (aim for under 30 minutes)
• A named backup driver/vehicle contact, not just "we'll arrange something"
• Who their own after-hours contact is, and their number
• What they cover versus what falls back on you (fuel, food, accommodation during a delay)

This is boring to chase down in July when everyone's busy with the season, but it's the difference between "the handler will sort it" and actually knowing who picks up the phone at 1 am. It also feeds directly into your operations SOPs from booking to departure: the SLA numbers belong in that document, not scattered across old chat threads.

The rotating duty-phone: three people, one number

A three-person team can't each carry the "anyone might call me" burden simultaneously. That's how everyone ends up sleeping with the phone on loud, all season. Instead, run one shared duty-phone (a second SIM or a forwarded number works) and rotate who carries it.

Example: Say your three-person team splits duty by week: you carry the phone Monday to Wednesday, your partner Thursday to Saturday, and whoever's least booked that Sunday. Across a typical month with 8 departures running, each person is "on" for roughly a third of the emergencies but is fully off the other two-thirds, including nights. That's the entire point: round-the-clock coverage for the business, not round-the-clock exposure for any one person.

Whoever holds the duty phone that week gets first-line responsibility for every Tier 1 and Tier 2 message across every active departure group, and escalates to the owner only when they can't resolve it themselves. Write the rotation on a shared calendar, not memory: "whose week is it" should never require a debate at 11 pm.

Why this can cost you close to nothing

The instinct is that round-the-clock support means round-the-clock cost: staff time, a support line, maybe a call centre. On WhatsApp specifically, it's cheaper than most operators assume, because of how the platform prices conversations.

Since 1 July 2025, WhatsApp Business API billing works on a per-template basis, but replies inside an open 24-hour service window, meaning the traveller messaged first and you're replying within a day, are free, and utility templates sent inside that window are free too, according to Meta's own pricing documentation. Support conversations are, by definition, reactive: the client messages, you reply. That's the free case.

Example: Say you run 8 departures a month, averaging 30 WhatsApp exchanges per departure: check-ins, one SOS, itinerary reminders. If nearly all of those replies fall inside the window the traveller opened (which they do, since support is reactive by nature), you're paying ₹0 in messaging cost. Only your team's time. If you instead pushed a chunk of those out as unsolicited utility templates, after-July-2025 rates run about ₹0.115 per message, so 240 messages would cost roughly ₹28 for the month. Send the same volume as marketing templates and you're at ₹0.78–0.88 each, seven times the utility rate: ₹190–210 for identical volume. The lesson: keep support reactive and inside the window, not broadcast, and it stays nearly free.

It also helps that WhatsApp read rates are fast: vendors cite up to 95% of messages read within three minutes, though independently measured opt-in read rates run closer to 68% on average, per industry data. Either way, a pinned message in a live group reaches a traveller faster than an email they won't open until they're back on Wi-Fi.

What the Himachal floods taught about phones and networks

None of this works when the network itself goes down. During the September 2025 Himachal floods, more than 2,500 vehicles were stranded with tourists waiting it out in hotels while mobile networks were down for hours at a stretch. A WhatsApp group is useless if there's no signal to send to.

For any hill or remote-terrain departure, agree an offline fallback before the trip leaves: a physical meeting point at each overnight stop if the group can't be reached digitally, and a phone tree through your local drivers. The driver calls the next driver down the convoy, who calls the ground handler's landline, which someone eventually gets through to even when mobile data is down. It's low-tech on purpose. For the wider playbook on handling a destination-level disruption once it's underway, see the crisis playbook for tour operators.

Common questions

How does a three-person team realistically offer 24×7 support?

Not by having three people awake at all hours. Instead, rotate a single duty-phone weekly so each person covers emergencies for roughly a third of the season and is fully off the rest, backed by a severity matrix that filters routine questions to normal hours.

What actually justifies waking someone up at midnight?

Only Tier 1 situations: accidents, hospitalisation, a missing traveller, or a vehicle breakdown somewhere unsafe. Flight delays, itinerary questions and general "what time is X" messages wait for the next response window, even if they arrive at midnight.

Should support run on the free WhatsApp Business app or the paid API?

Either works for a three-person team; the free app is enough if one person can rotate through checking a single device. The API earns its cost once you're running enough departures that automated confirmations and reminders justify the per-template pricing. Support replies themselves stay free either way, inside the 24-hour window.

What if the ground handler doesn't answer during an emergency?

This is exactly what the written SLA is for: it should name a backup driver or contact, not just "we'll arrange something." If a handler can't produce that name before the season starts, that's information about whether to keep booking them.

The short version

• Sort every on-trip message into a severity tier before deciding whether to call at midnight or reply at 9 am; most "urgent" messages are Tier 3.
• Open a dedicated WhatsApp group per departure the day it's confirmed, with pinned group rules and a one-message emergency contact card.
• Get written SLAs, with a named backup contact, from every ground handler and DMC before the season starts, not after a driver goes silent.
• Rotate a single duty-phone across your team weekly so 24×7 coverage doesn't mean 24×7 exposure for one person.
• Reactive WhatsApp support inside the 24-hour service window costs close to nothing. Save templated broadcasts for marketing, not for replying to your own travellers.
• For hill and remote departures, agree an offline meeting point and driver phone tree in case the network itself goes down.