How One Small Team Won Customers Back by Dropping Jargon

How One Small Team Won Customers Back by Dropping Jargon

Picture a small team that sold weekend trips and kept losing people at the very last step. The trips were fine. The prices were fair. What went wrong was the writing, and the fix turned out to be dull, cheap and surprisingly effective: choosing plain words over jargon. The team is made up, but I have watched the same thing play out in so many small businesses that the details will probably feel familiar.

The problem nobody could see

The team had five people and a shared inbox. Each person had picked up the habit of writing booking notes in the shorthand of the travel trade. Confirmation emails talked about “OTA bookings”, “pax counts”, “inclusions”, “ex-airport transfers” and “subject to availability at time of reservation”. Everyone on the team knew exactly what these meant. Customers did not, and rather than ask, they simply stopped replying.

For months the team blamed timing, then pricing, then the season. Only when someone on the team asked a friend outside the business to read a confirmation email aloud did the pattern show up. The friend stopped three times in the first paragraph. “What is a pax?” “Is the transfer included or not?” “Do I have a room or do I not?” Nothing in the email was false, and yet a normal reader could not tell what they had bought.

The experiment: one week of plain words

The team decided to try something small. For one week, every outgoing message would follow three simple habits. First, the main answer comes in the opening sentence. Second, any trade word gets swapped for an everyday one, or explained the first time it appears. Third, no sentence runs longer than a breath.

The first draft of a rewritten confirmation looked like this: “Your room is booked for two nights. A car will meet you at the airport and take you to the hotel. Breakfast is included on both mornings. Dinner is not, so you will want to plan for that. If anything changes, reply to this message and we will sort it out.” Compare that with the old version and the difference jumps out. A stranger could read the new one on a phone, standing in a queue, and know what happened to their money.

What changed in the first month

Nothing dramatic happened overnight, which is why the story is believable. Replies came faster, though. Customers who used to go silent started answering with small, practical questions such as the time of arrival or whether a late check-in was possible. The team spent less time chasing and more time helping. The inbox got quieter in the right way: fewer “just checking” messages, more “see you Friday” messages.

There was a quieter win inside the team as well. New hires picked up the work faster, because the internal notes had been rewritten the same way. A note that said “pax confirmed, ex-transfer pending” became “all four guests are confirmed; the airport pickup still needs a driver”. Nobody had to decode anything. When someone was out sick, a colleague could take over a booking by reading a few clear lines.

Where the plan tripped

The road had a few potholes. In the second week someone over-corrected and began writing so casually that a message about a cancelled pickup read like a joke. The team agreed that plain does not mean flippant: a serious change deserves a calm, direct sentence. Another slip was swapping a trade word for a vague one. “Subject to availability” became “it depends”, which helped nobody. The better rewrite said what it depended on: “if the hotel is full on that date, we will offer the nearest alternative and tell you before charging anything”.

A third lesson came from a regular customer who wrote back to say the new emails felt shorter but she missed one detail. The old messages had always listed the pickup time. The rewrite had pushed it out by accident while trimming. The team added a small, fixed block at the end of every confirmation with the three things people most often look for: when, where and who to call. Shortening a message is only a win if the facts people need are still in it.

A single message, before and after

Here is how one real-sounding line changed. Before: “Kindly note that early check-in is contingent upon property discretion and cannot be guaranteed.” After: “You can ask for an early check-in, but the hotel decides on the day, so please do not plan around it.” The second line is longer in words and shorter in effort. It tells the reader what they may do, who makes the call, and what to expect. That is the whole trick, repeated across a hundred messages.

The habits that stuck

  • Lead with what the reader needs. Dates, places and what is covered go in the first lines.
  • Swap the shorthand. “Guests” instead of “pax”, “flight” instead of “sector”, “not included” instead of “excluded”.
  • Explain once, simply. When a word must stay, it gets half a sentence of explanation the first time.
  • Prefer short sentences. A long sentence is usually two sentences hiding together.
  • Test on an outsider. Hand it to a friend from another line of work and listen to them read it out.

Why it works outside travel too

The same idea applies to any business that talks to the public. A bakery writing “allergen information available on request” could just say “ask us if you are worried about nuts”. A software team writing “service degradation observed” could say “the app is running slowly for some people, and we are fixing it”. Every field has a house dialect, and every house dialect makes insiders feel competent and outsiders feel small. The cure is rarely a big rewrite. It is a steady habit of picking the word the customer already uses.

If you like seeing how this plays out on the road, our own pages on trips make a good test. Have a look at a motorcycle journey through Colombian cities and coast and ask yourself whether a first-time reader could plan from it. Another one worth a skim is our rundown of road trips by rented bike or car in Canada, where the choice of everyday words does a lot of the work.

Where the team looked for inspiration

Part of the team’s habit was reading how other places talk to ordinary people. One teammate liked browsing city websites that mix practical pages with chatty ones. DelhiOrbit is one such site about Delhi, with pages for events and venues, a blog and a forum, and it gave the team a reminder that a page can be useful without sounding like a manual. The lesson they took was not about content but about tone: write as if you are explaining to a neighbour.

What they would tell another small team

Asked what they would pass on, the team kept it short. Start with one message type, the one customers see most. Rewrite it until a friend outside the work can read it once and answer “what happens next”. Then keep that version as the model and let it spread from there. Do not wait for a style guide or a meeting. The plainest rewrite you can do today is better than the perfect one you plan for later.

Looking back, the team noticed something that surprised them. The plain versions were not only clearer but also friendlier, and more honest. When you cannot hide behind a trade word, you have to say what you mean: this is covered, that is not, here is who to ask. Customers noticed. The team is imagined, yet the takeaway holds up, and you can test it on whatever message you write next.