Priya and Dev ran a tiny desk that matched hobbyist builders and small flying clubs with aircraft parts, and by their second spring the inbox had taken over their lives. Imagine a Tuesday morning: nineteen new messages, and fourteen of them asked some version of the same thing. Is this part still available? What details do you need to confirm fit? How long until it ships? Their story is invented, but anyone who handles aircraft parts enquiries will recognise the rhythm, and it shows neatly when to automate a repetitive step and when to leave it alone.
Week one: answering everything by hand
At the start, Priya wrote every reply from scratch. It felt personal, and in a business where buyers worry about getting the right component, personal matters. She learned things that way too. She learned that people often forgot to mention the aircraft type, that some did not know where to find a part number on a worn label, and that a surprising number wanted to know what paperwork travels with a used item.
Dev suggested building a canned reply system straight away. Priya said no, and she was right. You cannot template what you have not yet understood. The first weeks of manual replies were research, even if neither of them called it that.
Week four: noticing what never changes
One evening Priya pasted her last thirty replies into a single document and read them in a row. The experience was a bit embarrassing. Whole paragraphs repeated almost word for word. Greeting, a request for the aircraft type and part number, a note on what documentation they could provide, a line on shipping timelines. The variable bits were small: the part itself, the quantity, one or two personal touches.
That was the moment to automate. They wrote four short building blocks:
- An opening that thanks the sender and restates the part they asked about.
- A block asking for the details needed to check fit, in a short list.
- A block describing what records they can supply with a part.
- A closing line setting expectations about the next reply.
Each block lived in a shared note. A reply became a matter of pasting two or three blocks and then writing the one sentence that was truly specific to that person.
What they kept manual on purpose
Their decision about what to leave alone matters as much as what they templated. Anything that touched safety or airworthiness stayed hand-written. If a buyer asked whether a part was suitable for a particular aircraft, Priya or Dev answered personally, checked the reference material and, when unsure, said so plainly. A template that confidently answered a fitment question would have been worse than slow.
They also kept the first line of every reply human. A canned opening paragraph that sounds canned makes the sender feel processed. A single genuine sentence at the top, mentioning what the person is building or flying, changed the entire tone.
The unexpected benefit: fewer misunderstandings
Dev had expected time savings. What surprised them was consistency. Once the questions about the aircraft type and part number were in a block, buyers stopped sending half-complete enquiries. The back-and-forth dropped from three or four messages to one or two. Fewer messages meant fewer chances for a detail to slip through the cracks, which in this trade is worth more than speed.
A glance at how other industries do it
Priya liked to show the idea to friends in unrelated fields. A friend who works near travel health pointed her to HipHospitals, a site for medical travel whose pages say it sorts hospitals and doctors by country for overseas patients and offers request forms for free quotes and appointments. Priya’s take was that the forms do the same job her building blocks did: collect the same handful of basics from everyone in a predictable order so the human on the other end can concentrate on the question itself.
Making the templates earn their keep
Every month the pair read through their blocks and trimmed them. Some lines stopped being useful, such as a shipping note that had changed. Others needed splitting. A template library that is never reviewed becomes a museum of outdated promises, and that is a real risk when customers rely on what you wrote.
They also tracked how often they overrode a block. If Priya found herself rewriting the documentation paragraph more than half the time, it was a sign the block described a situation that no longer matched reality, so she rewrote it.
Lessons they pinned above the desk
- Write the first batch of replies by hand and treat them as research.
- Read a month of replies together and underline what repeated.
- Turn only the repeating parts into blocks; keep one sentence personal.
- Never template anything that touches airworthiness or fitment judgment.
- Review the blocks monthly and delete what has gone stale.
Money, time and attention
Priya has said the real saving was not minutes but attention. When you stop retyping the same paragraph, your attention goes to the unusual message that really needs it. She even wrote down a note about where small costs go, inspired by a post on tracing where everyday money slips away each month. Her version for the business was a list of where hours leak, and replying to repeated questions topped it.
For readers who like the broader picture of making journeys smoother, there is also a friendly read on starting a trip with a rental platform, which shares the same spirit: standard steps handled once, so the trip itself gets your focus.
How the story ends
A year on, the desk handles more enquiries with the same two people. Mornings begin with a quick scan of the inbox, a handful of replies assembled from blocks, and a longer stretch left for the messages that need real thought. Priya still writes a personal line in every reply. Dev still refuses to let anything about fitment go out without a second look. The tools changed their workload, but not their standards, which was exactly the point.
If your own inbox feels like Priya’s did in week one, do the dull thing first: answer by hand for a few weeks, collect your replies in one place and see what never changes. The template is already hiding in there.

