The pre-trip documents checklist to WhatsApp every client

The same three calls happen every departure week. "Which form is TDAC again?" "Kitna cash le jaana hai?" "Sir, Dubai wale bol rahe hain hotel booking chahiye, maine to visa fees diya tha na?" None of these calls are the client's fault. They're yours, for not sending the right information at the right time.

A pre trip message to a client shouldn't be one giant PDF dumped the night before departure. It should be four short WhatsApp messages, spaced out from thirty days before the trip to the day before, each covering exactly what that client needs to act on right then. Build the four templates once per destination and you reuse them for every booking on that route.

This is also, quietly, how you cut a big chunk of the "how to reduce customer queries" problem every travel agency has. Vague, late, or missing information is one of the most-cited reasons clients complain about agencies and don't rebook: industry data on operator complaints puts poor communication and vague trip information near the top of the list. A documented send-sequence fixes that at the source, and it pairs well with whatever round-the-clock coverage plan you already run for a small team.

The four-message sequence that replaces the panic calls

Send these on a fixed schedule, destination-specific, and store them as reusable WhatsApp templates rather than retyping for each client.

When	Message name	What it covers
T-30 days	Documents & visa	Passport, visa/e-visa/TDAC steps, forms, upload checklist
T-7 days	What-to-expect pack	Packing, weather, food, eSIM, forex vs card, tipping
T-72 hours	Confirmation	Flight PNR, hotel voucher, driver/guide contact, insurance copy
T-24 hours	Day-before	Reporting time, airport gate, baggage limit, emergency number

The first message is the one that prevents visa and entry rejections. The rest prevent the "what do I pack / what do I do" questions that eat your afternoon.

T-30: documents and visa, destination by destination

This is the message clients read the most carefully, and the one where a missing line item genuinely costs a rejected visa and a client who blames you for it.

For a Dubai trip, the checklist changed meaningfully after December 2024. UAE authorities tightened scrutiny and Indian tourist visa rejection rates reportedly rose from roughly 1-2% of daily applications to 5-6%. A return flight ticket, a hotel booking confirmation carrying a QR code, and proof of funds are now effectively mandatory uploads. Anyone staying with relatives instead of a hotel needs the host's tenancy contract and Emirates ID copy as well (Business Today, Dec 2024). Your T-30 message for Dubai should list each of these as a separate line the client ticks off, not a paragraph they skim. You're also collecting Emirates ID and passport copies over WhatsApp, so check what the DPDP Act actually expects you to do with them afterward.

For Thailand, the document is the Thailand Digital Arrival Card (TDAC), mandatory for every foreign national including Indians since 1 May 2025. It replaced the old paper TM6, it is free, and it must be submitted online within three days before arrival. It generates a QR code the client shows at immigration (Tourism Authority of Thailand). Send the direct portal link, not a description of "the Thailand form."

Careful: the official TDAC portal is tdac.immigration.go.th and it charges nothing. Paid lookalike sites rank on Google for "Thailand digital arrival card" and clients who search it themselves will pay someone else ₹500-1,000 for a free form. Put the exact URL in your T-30 message so nobody has to search.

For domestic hill destinations (Himachal, Uttarakhand, Sikkim), the T-30 message is lighter on paperwork and heavier on a weather-and-road disclaimer, covered in the T-7 pack below. There's no visa step, but there's a genuine safety expectation to set early, especially for June-September departures.

Whatever the destination, close the T-30 message with the money question every client eventually asks: "why is there a 2% charge on my invoice that wasn't in the quote." From 1 April 2026, overseas tour packages attract a flat 2% TCS with no threshold, replacing the earlier 5% (up to ₹10 lakh) / 20% (above ₹10 lakh) structure (Budget 2026-27, LRS amendment). See the flat-2% TCS playbook for the full mechanics. Pair it with a plain answer on why the invoice shows 5% or 18% GST, and the T-72hr call won't turn into a dispute. TCS and GST slabs move; confirm the current rate with your CA before printing a template.

T-7: the what-to-expect pack

This is the message that does the most work against repeat calls, because it answers the questions clients don't know to ask until they're already anxious about the trip. Send it as one structured message per destination, built once and reused.

Cover, in this order:

1. Packing list by season: not a generic list, but one specific to the month they're travelling. A December Ladakh list and a July Ladakh list share almost nothing.
2. Weather reality, stated plainly. For Himachal in the June-September window, IMD's standing monsoon advisory tells tourists to track forecasts daily, avoid high-altitude travel during heavy rain, and be ready to halt travel altogether in hazardous conditions (IMD advisory via Outlook Traveller). Quote this, don't soften it. A client who's read it in your message won't call panicked when a landslide closes a road; they'll already know it's a possibility you flagged.
3. Food and dietary reality: veg/Jain availability at the specific hotels booked, and where it genuinely gets thin (remote homestays, long drive days).
4. eSIM or local SIM options, with the one or two providers that actually work at the destination, not a generic "get a SIM at the airport" line.
5. Forex vs card, with the actual money math. This is where the TCS conversation continues from T-30 and where you convert forex-refusers.
6. Tipping norms for the destination, as a rupee/local-currency range, not "tip generously."
7. Hotel check-in reality: standard check-in time, early check-in likelihood, ID needed at the desk.

Example: A client is deciding whether to book their forex through your package or load a travel card independently. Your package's overseas component is ₹3,00,000, so the flat 2% TCS collected on it is ₹6,000, fully adjustable against their income tax liability or refundable via ITR, not a real cost. If instead they load ₹3,00,000 onto a forex card entirely outside the package, that falls under LRS "other remittances," where TCS stays nil up to ₹10 lakh a financial year and only 20% kicks in above that (LRS amendment note). Below ₹10 lakh, the self-loaded card has zero TCS versus ₹6,000 upfront (refundable) on the package. That's an honest comparison, not a sales pitch, and clients trust you more for stating it plainly.

Insurance belongs in this message too, with numbers rather than a recommendation. Overseas hospitalisation can run ₹5-50 lakh in the US, and medical evacuation alone can cross $100,000, while travel insurance for the same trip typically costs ₹19-45 a day (PolicyBazaar). For a ten-day US trip that's roughly ₹190-450 in premium against a five-to-fifty-lakh exposure. That's the comparison that moves clients who "never buy insurance."

T-72hr: the confirmation message

Three days out, the client needs facts, not education. Send flight PNR and check-in status, hotel voucher with confirmation number, the driver or local representative's name and phone number, and a copy of the insurance policy document. Nothing new to decide: everything to have saved on their phone before they lose signal at the airport.

T-24hr: the day-before message

The last message is purely logistical: airport reporting time, terminal and gate if known, checked-baggage weight limit, and one emergency contact number that rings a person, not a switchboard. Keep it to five lines. This is the message most likely to get read in the taxi to the airport, so it can't require scrolling.

The Hindi+English one-pager

Build one bilingual one-pager per destination that compresses the T-7 pack into a single shareable image or PDF: packing list, weather note, forex-vs-card math, tipping range, and the emergency number, in both English and Hindi side by side. Store it once, attach it to every booking on that route, and update only when a rule (TDAC's process, Dubai's document list, the TCS rate) actually changes. That's the difference between rebuilding this checklist for every client and building it once.

Common questions

How do I reduce repetitive client calls before a trip

Send the answers before clients think to ask, on a fixed schedule. Most repeat calls are questions your T-7 pack already covers; the fix is timing, not faster replies.

How do I fill the Thailand TDAC for a client

Send only the official tdac.immigration.go.th link, within three days of arrival. It's free and generates the QR code shown at Thai immigration.

How much TCS applies on a foreign tour package now

A flat 2% on the package value, no threshold, as of July 2026. It's adjustable against the client's income tax or refundable via ITR. Confirm the live rate with your CA before quoting.

What should a Himachal or Kashmir packing list include for clients

A season-specific list plus an explicit weather disclaimer for June-September travel, quoting IMD's advice to track forecasts and halt travel in hazardous conditions.

The short version

• Send four WhatsApp messages per booking: T-30 (documents/visa), T-7 (what-to-expect pack), T-72hr (confirmations), T-24hr (day-before), built once per destination and reused.
• For Dubai, the T-30 message must list return ticket, hotel voucher with QR code, and proof of funds as separate checked items, not a paragraph.
• For Thailand, send the official tdac.immigration.go.th link directly and warn against paid lookalike sites.
• Fold the "what to expect" pack (packing, weather, food, eSIM, forex vs card money math, tipping, check-in reality) into the T-7 message.
• State the flat 2% TCS on packages versus nil-up-to-₹10-lakh on self-loaded forex plainly; the honesty builds trust and cuts invoice disputes. Confirm current rates with your CA.
• Quote IMD's monsoon advisory verbatim for hill destinations instead of a vague weather warning.
• Build one Hindi+English one-pager per destination and reuse it: that's what actually cuts repetitive calls, not answering them faster.