Get Started
Chapter 28 min read

Customer Communication Without Losing the Relationship

Faster replies that still sound like your business — and the line you should never cross.

The fear is reasonable: if replies start sounding generated, you lose the thing that makes a small business worth choosing. The solution is not to avoid the tool — it is to be precise about which part of the job you hand over.

You hand over typing. You keep judgement, tone and the send button.

Build your answer bank first

List the ten questions you answer most: price, delivery time, availability, warranty, location, payment methods, customisation, lead time, after-sales, bulk orders.

Write your best answer to each, once, in your own words. This is the highest-value hour you will spend, because everything afterwards adapts these rather than inventing from nothing.

Adapting a stored answer to a specific customer

Here is how we normally answer this question:
{{your standard answer}}

Here is the actual message from a customer:
{{their message}}

Rewrite our standard answer as a reply to this specific person:
- Address what they actually asked, in their order
- Keep our facts exactly as written above — do not add or change any price, timeline or condition
- Warm but brief, under 120 words
- End with one clear next step

If their message asks something our standard answer does not cover, say so rather than inventing an answer.

Keep the send button human

Read every reply before it goes. This is not paranoia; it is a thirty-second check that catches wrong prices, misread questions and tone that does not fit the relationship.

The saving is in not starting from a blank message. That saving survives the review; the risk does not survive skipping it.

Working in Nepali

AI handles Nepali far worse than English, especially in formal register and honorifics. The errors are subtle to a non-native reader and obvious to your customer.

Practical approach: draft in English if the model helps you think, then write the Nepali yourself using it as a scaffold. Never send AI-generated formal Nepali unedited, and never let someone who does not read Nepali approve Nepali output.

What not to automate here

  • Complaints and refunds — these need a person from the first line, because how you handle them is the relationship
  • Anything involving a price you have not already agreed internally
  • Messages to a customer who is already unhappy
  • First contact with a high-value prospect, where the personal effort is itself the signal

What to take from this chapter

  • Write your ten standard answers once; adapt them rather than generating from scratch
  • Instruct explicitly that facts must not be added or changed, and gaps must be flagged
  • A human reads and sends every customer message
  • Never send unedited formal Nepali, and keep complaints fully human

Try it

Write out your three most-asked questions and your best answer to each. Use the adaptation prompt on a real customer message. Compare the draft to what you would have written — note what you had to fix, and add that as a rule to the prompt.