Skip to content
GullySales
← All articles

Notes for owners · CRM, automation and RevOps

Missing enquiries in a short tourist season: one watcher and an honest auto-reply

Why a camp or hotel with a short season loses enquiries in its busiest weeks, and how one named watcher for every channel and an auto-reply promising a reply time you can meet stop it.

The GullySales team · Updated 17 Oct 2026 · 6 min read

Editorial illustration for Lead response and follow-up
On this page
  1. Where the enquiries go missing
  2. Draw the channel map before the season
  3. Who the watcher is, and what they may decide
  4. The auto-reply promises a time you have already met
  5. For example: the ten-minute promise at a camp near Sam
  6. When you can skip the watcher
  7. Draw the map in the hot months

In a desert camp's Christmas week the phones are busiest and the staff are busiest, so enquiries go unanswered. If your season is a few busy winter months, name one person whose only job in season is to watch every channel enquiries arrive on. Then set an auto-reply on each channel that promises a reply time you already met on your busiest day last season. Not the fastest time you ever managed. The slowest normal one.

Where the enquiries go missing

In a short season, the people who answer enquiries are also running the place. The owner is meeting a tour group's bus. The manager is at the camp, where the signal comes and goes. The receptionist is checking in a family of eleven while three WhatsApp messages wait.

And the enquiries do not arrive in one place. A couple from Ahmedabad writes on Instagram. A family from Delhi calls the number on your Google listing. A travel agent in Mumbai emails about a group of forty for the Desert Festival. Someone fills in the website form, which goes to an inbox nobody has opened since October. Each channel has someone who might see it, so nobody owns any.

A visitor to Rajasthan with fixed dates may book the first camp that answers, and a half-day wait gives another camp the chance.

Draw the channel map before the season

In the quiet months, list every place an enquiry can arrive. For each, write where it lands today and who will watch it in season. The rows below are illustrative, for a desert camp with a small office in town.

ChannelWhere it lands nowWho watches it in seasonWhat the auto-reply does
WhatsApp on the listed numberOwner's phoneThe watcher, on a laptop in the town officeNames the watcher, gives the reply time, asks for dates and guests
Calls to the listed numberOwner's phone, rings out at the campForwarded to the office phone in seasonA short recorded line in Hindi and English with the WhatsApp number
Instagram messagesA relative who postsThe watcher, logged in on the same laptopSame reply time, points to WhatsApp for a quote
Website form and chat buttonAn email address nobody readsChat button opens WhatsApp with the watcher; form copies to the watcherConfirms receipt and the reply time
Booking site messagesThe manager's phone, at the campThe watcherThe booking site's own tools; check its current rules
Travel agents' emailsOwner's inboxThe owner, at a fixed hour each eveningStates when the owner replies to group requests

The last row is deliberate. Group and agent bookings carry rates and terms the watcher should not set, so they go to the owner. Everything else goes to one person.

Who the watcher is, and what they may decide

Pick someone in town, where the network holds, with a laptop and every login on it. Not the owner, who is pulled in many directions, and not the camp manager, who has guests to feed.

The watcher may quote from the dated rate sheet, hold a date until a stated clock time, and send the advance details. They may not change a rate. Nor may they promise a tent that is not free, or agree a group deal. Anything outside that list goes to the owner, with a reply to the guest saying when they will hear. Our note on preparing for a short tourist season in Kullu and Manali covers rehearsing the desk; the checks work in Jaisalmer too.

Write down the hours the watcher covers. Outside them the auto-reply carries the promise, so it must be true.

The auto-reply promises a time you have already met

Many auto-replies promise what the owner wishes were true: "We will get back to you shortly." A guest reads that as minutes. Promise a clock time instead, and choose it from evidence.

Open last season's WhatsApp chats for the busiest week. For a sample of enquiries, note when each arrived and when someone replied. Ignore the best day. Find the longest wait on an ordinary peak evening, round it up, and promise that. If it is three hours, write three hours. A guest can plan around that, not around "shortly".

Then write the message. This one fits the away message in the ordinary WhatsApp Business app; change the brackets.

Namaste, and thank you for writing to (camp name), Jaisalmer. (Watcher's name) answers every message between (start time) and (end time) and will reply within (the time you met last season). Messages after (end time) are answered by (morning time you can keep). To get your quote faster, send your dates, the number of guests, and whether you need a pickup from Jaisalmer.

Write it in the language most of your guests use.

For example: the ten-minute promise at a camp near Sam

Imagine a family-run desert camp near the Sam dunes with a booking office in Jaisalmer town. The details are illustrative. Before last season someone in the owner's family set an auto-reply promising "a reply within 10 minutes". The person answering was the camp manager, on a personal phone, at the dunes.

In the week before New Year the manager was serving dinner to sixty guests when most enquiries came in. Replies went out two and three hours later. Several guests wrote back quoting the ten minutes, and one review said so in public.

The next season the camp changed two things. The office clerk in town became the watcher from 8 am to 10 pm, with WhatsApp, Instagram and the booking site messages on one laptop. The auto-reply changed to "within two hours", the slowest time the clerk had actually met on a peak evening. The manager stopped answering enquiries altogether. The promise was slower than before, and complaints about the wait stopped, because the reply came when the guest was told. The cost was a clerk's season wage and a laptop moved from the accounts desk.

When you can skip the watcher

If you run four rooms and the owner answers every message personally within the hour, you do not need a watcher. You need a phone charger. And if your season is spread across the year, put the effort into a steady lead response and follow-up routine instead.

Draw the map in the hot months

Draw your channel map now, with a name in every row and none marked "everyone". Then find last season's slowest honest reply time and put it in the away message before the first winter booking arrives. If you would like the map, the routing and the replies worked out before the season, with lead routing and assignment in mind, tell us what you need.

Questions

Questions owners ask.

Should the auto-reply give our room or tent rates?
No. Peak rates change with the date and the group size, and a rate in an automatic message gets quoted back to you weeks later. Let the auto-reply ask for the dates and the number of guests, and let the watcher send the rate from the current rate sheet once they have both.
Do we need a chatbot on the website?
Only if your website brings enquiries in numbers the watcher cannot read in time. For a small camp or hotel, a chat button that opens WhatsApp with the watcher is usually enough, because it puts the message where the watcher already looks. A bot that answers badly is worse than an honest auto-reply.
What if the watcher falls ill in the middle of the season?
Name a second person before the season starts and give them the logins and the rate sheet on day one, even if they never use them. Change the name in the auto-reply the same day the watcher changes. A different name matters less to a guest than a promise nobody keeps.

From the blog

More notes for owners.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.