Imagine a small Chennai tour desk we will call Marina Trails: three people, two shared phones, one whiteboard. They arrange heritage walks, temple-town day trips and airport transfers for visitors who find them through word of mouth. Business was decent, and complaints were few, but the owner, Latha, kept noticing a pattern. Nearly every problem began with a sentence like “I thought you said.” This is the story of how Marina Trails stopped losing time and goodwill by adding one small step to every booking call, and what any Chennai host, driver or traveller can borrow from it.<\/p>\n
It started on a Monday. A visitor had booked a morning walk through the old city and was told, by phone, that the guide would meet her “near the main entrance.” The guide, Suresh, understood that to mean the car park. The visitor waited at the road. They found each other forty minutes later, and the visitor, tired and cross, said she had been promised a private walk, not a shared one. Suresh insisted the booking was for a small group. Latha, who had taken the original call, genuinely could not remember which she had said.<\/p>\n
On Wednesday, a family arriving by train asked for an airport transfer the next day; the driver heard “evening” and the family meant “early evening.” On Friday, a couple disputed whether lunch was part of the day-trip price. Three problems in five days, none of them anyone’s malice, all of them rooted in a conversation that left no trace.<\/p>\n
Latha called a ten-minute meeting and wrote one rule on the whiteboard: after any booking call, send a short message. No exceptions, no templates stored in a drawer. The message had to state three things in plain words:<\/p>\n
Each message ended with the same closing line: “Please reply yes if this matches, or tell us what to fix.” That small invitation mattered. It made correcting the desk feel normal rather than rude.<\/p>\n
The new rule paid off almost immediately. A visitor named Dev had booked a day around the city’s beaches and old quarters. The confirmation said the car would collect him at 8:00 and that entry charges were separate. His reply came within minutes: “I understood entry charges were included, and 8:30 is better for me.” Neither point had surfaced on the call. Latha adjusted the pickup, explained the charges and Dev decided to go ahead, now fully informed. The day cost the same as it would have, yet it avoided an argument that would have arrived at the ticket counter.<\/p>\n
If you are building your own itinerary, our overview of planning a first visit to Chennai<\/a> pairs naturally with this approach, because every plan on that list involves at least one promise from someone else.<\/p>\n Within a month, Marina Trails noticed side benefits that Latha had not predicted.<\/p>\n Perhaps the biggest change was cultural. People at the desk started listening harder on calls, knowing they would have to summarise the conversation within the hour. Vague phrases such as “around morning” got sharpened into specific times before the call even ended.<\/p>\n After a few weeks, the team settled on a house style that anyone could copy. A typical message read: “Hello, and thank you for booking. We will meet you at the gate of your hotel at 8:00 on the day we discussed for the old-city walk. The price covers the guide and the car for the morning, and entry charges are paid separately at the gate. If it rains heavily or you are running late, message this number and we will move the start. Please reply yes if all of this is right.”<\/p>\n That is about seventy words. It takes a minute to write and perhaps thirty seconds to read. Because it follows the same order every time (what, when, what is covered, what if), visitors learn quickly where to look for each detail, and the desk spots gaps in its own offers before the visitor does.<\/p>\n The system was not flawless. One driver, new to the desk, preferred voice notes and ignored the written messages. A transfer mix-up followed. Latha did not scold; she simply asked him to reply with a thumbs-up to each confirmation and showed him how a single line could prevent a long wait at the airport. Within a fortnight he was sending his own confirmations to the desk.<\/p>\n That episode taught the team something practical: the habit only works if both sides see the message. A confirmation that nobody reads is no better than silence, so make sure the reply is part of the routine.<\/p>\n As Marina Trails took on more bookings, Latha began thinking about invoices, supplier payments and how to organise the business’s records for the year. These are not questions a whiteboard can answer. She looked for a chartered accountant who could work with a small tourism business, and a directory like BestCaNow<\/a> gave her a place to start, since the site is organised around finding chartered accountants by city, area of expertise and preferred consultation style. What she asked each accountant at the end of every call was the same thing she asked of her own drivers: send a short note stating what we agreed.<\/p>\n Whether you are a visitor or someone who hosts visitors, the story offers a few ideas that carry over directly.<\/p>\nWhat changed inside the team<\/h2>\n
\n
What a good confirmation looked like in practice<\/h2>\n
The one hiccup<\/h2>\n
When the desk grew<\/h2>\n
Lessons any Chennai host or traveller can borrow<\/h2>\n
\n