Nobody sets out to spend their evenings retyping the same message. Yet that is what happened to a small three-person tour desk in Patna that arranged homestay visits and day trips around Bihar. This is a story told as a team narrative, with invented people and an invented schedule, but the sequence it follows is a sound way to think about how to automate repetitive booking replies: do the job by hand first, watch what never changes, then template that part and leave the rest to a human.
The evening the desk counted its own typing
The desk handled enquiries from travellers who wanted to see Nalanda, Bodh Gaya or a rural farmstay. Every enquiry produced roughly the same reply: a greeting, pickup details, what to carry, a note about local timings, and a polite request for the traveller’s arrival date. The three coordinators called it “the long message”, and each had a private version saved in a notes app, slightly different in every case.
The first analytical step was embarrassingly simple. For one week, they kept a tally on paper. Each time a coordinator typed a reply, they marked whether the text was brand new, lightly edited or pasted from a saved copy. By Friday the tally showed that most replies were pasted copies with a name swapped in. Only a small share needed real thought, such as a traveller with a particular mobility need or a group arriving during a festival.
That ratio is the evidence this whole approach rests on. If most of a task is identical each time, it is a candidate for a template. If most of it is different each time, automation will make it worse. The desk had data now instead of a feeling.
Why they did not automate on day one
One coordinator argued for an auto-reply system right away. The other two held back, and their caution proved correct. Their saved messages disagreed with each other on small facts, such as how early guests should reach the pickup point. Automating three inconsistent versions would only have produced inconsistency at speed.
So they spent two more weeks answering by hand while keeping one shared document open. Every time someone corrected a detail, the correction went into the document. At the end of that period the document had stopped changing. That was the signal. A step that has stopped changing is stable enough to be written down once and reused.
- A step that changes weekly is not ready to automate.
- A step that has been identical for a month probably is.
- A step that depends on the traveller’s situation stays with a person.
What went into the template, and what stayed out
The team split the long message into blocks. The fixed blocks were the greeting, the pickup and meeting-point explanation, the packing note and the closing line. The variable blocks were the traveller’s name, the dates and any special request. A short checklist sat beside the template listing the details to confirm before sending: the traveller’s name, dates, group size and which stay was being discussed.
They also wrote down what the template must never do. It would not promise a price on its own, it would not confirm a room without a coordinator checking availability, and it would not answer questions about permits or documents beyond pointing to a reference. For document questions they kept a link to their own earlier write-up on what paperwork rental pickups usually demand across Asian countries, because that kind of question deserved a considered answer, not a canned one.
This division is the heart of the method. Templates carry the parts that are the same. People carry the parts that carry risk.
A look at the numbers they tracked afterwards
After the template went live, the desk did not trust their impression that things were better. They compared two simple measures across a fortnight before and a fortnight after: the average time from receiving an enquiry to sending a first reply, and the count of follow-up messages travellers sent asking for details already covered in the first reply.
The reply time dropped noticeably because the coordinators were no longer composing from scratch. More interesting was the follow-up count, which also fell, since the template always covered the same details in the same order and nothing got forgotten on a busy evening. Handwritten replies had been missing the packing note about a third of the time, according to the tally, and travellers had been writing back to ask.
The desk was careful about what it claimed from this. Two weeks is a short window, and a festival period had ended in between, which could account for part of the change. They noted the caveat in their own document and kept measuring. Analytical habits like that are what separate a useful template from a lucky one.
Automating the bookkeeping behind the replies
Once the replies were templated, the coordinators noticed the next chore. After each confirmed visit, someone copied the traveller’s details into a shared spreadsheet row, then copied the same details into a pickup sheet for the driver. Again they did it by hand for a couple of weeks. Again they saw that the columns never changed.
Only then did they use a simple form that fed both sheets from a single entry. It was a modest piece of automation, nothing exotic, and it took an afternoon. They did not attempt to automate the part where a coordinator phones a village host to confirm availability, because that call was where surprises surfaced: a family wedding, a power cut, a road closed for repairs.
The same logic applies to anyone planning a trip around Bihar on their own. If you are comparing village hospitality stays and cultural homestays across several districts, keep a reusable checklist for the questions you ask every host. You will be asking them again.
Where an outside site fits into the routine
The desk’s coordinators sometimes met visitors who were travelling in Bihar for reasons other than sightseeing, and a few were planning visits to hospitals abroad. For those cases they knew of HipHospitals, a portal for people travelling abroad for care, arranged country by country, with forms for free quotes and online appointments. The coordinators never gave health guidance and treated it purely as an admin reference.
What the desk would tell another team
When asked later what they had learned, the coordinators gave answers that were less about software and more about order of operations. Three of them stuck.
- Count before you build. A week of tallies replaced a month of arguing.
- Wait for the wording to stop changing. A template written too early freezes mistakes.
- Name the steps that must stay human, and write that list down where everyone can see it.
They also reviewed the template every few months, reading it aloud as if they were a traveller receiving it for the first time. Twice they found an instruction that had gone out of date. A template that nobody rereads becomes the kind of habit it was meant to replace.
Applying the same sequence to your own routine
You do not need a tour desk to use this. Think of any message, form or booking step you repeat. Do it by hand at least four or five times, with a paper tally if you like. Write down the pieces that never changed. Build a template for exactly those pieces. Add a short checklist of what to confirm before sending. And list the exceptions that always go to a person.
For Bihar travel in particular, a reusable booking checklist might hold arrival dates, group size, pickup point, dietary notes and the contact for a local host. If heritage stays are on your list, our notes on comfortable heritage stays for modern explorers are a reasonable place to build the first draft of that list.
The Patna desk still writes some replies from nothing. Those are the ones that matter most, and they now have the time to do them properly.
