Your customer needs an answer, not a paragraph of apologies.

Imagine opening a long, polite reply about a missing parcel. It thanks you twice. It says your patience is valued. It does not say whether anyone has checked the delivery scan.

A good customer service response confirms the actual problem, gives the known answer or action, and says what happens next. Use a template for structure. Rewrite the facts for the person in front of you.

Answer the question before polishing the tone

Read the full message and recent history. Write the customer's question in one sentence for yourself. If the reply does not address that sentence, a warmer greeting will not repair it.

Help Scout's help-writing guidance recommends clear instructions that do not assume the reader already knows the steps. Apply that to replies too: name the button, document or detail the person needs.

Build a reply from four small parts

These are illustrative lines, not a complete promise for every business. Do not paste them without checking your policy, authority and working hours. One precise apology is enough when you made a mistake; the rest of the message should help.

Keep a small set of editable templates

When one detail is missing

Hi [name], I can help with [request]. Please send [specific detail] through [approved route], so I can [next action]. You do not need to send [unnecessary sensitive information].

When your promised time has slipped

I said I would confirm [answer] by [time], and I have not been able to do that. [Known reason, if appropriate]. I am checking [specific action] and will update you by [realistic time]. I am sorry for the extra wait.

When you made a mistake

We [plain description of mistake]. I am sorry. We can offer [authorised remedy and relevant terms]. If that does not address your concern, [named review route] can look at it with you.

When the team is closed

We have received your message. Our team reads this inbox [working days, hours and time zone]. We will review it during our next covered period. For [a genuinely supported urgent situation], use [staffed route].

Only include an urgent route if it works. An automated receipt should be recognisable as one, and should not claim a person has already investigated.

Leave out promises you cannot authorise

The Ombudsman's complaint principles call for evidence-based explanations and appropriate remedies. Their UK public-service context does not set your business's legal obligations, but it is a useful check against unsupported answers.

If you cannot approve a refund, say who is reviewing it and when the customer will hear back. Use the escalation guide for the internal handover. Avoid writing “approved” when the request has only been submitted.

Read once for meaning and once for risk

Check names, amounts, dates, recipients and attachments. Remove leftover brackets. Ask whether a reader unfamiliar with your internal terms can follow the next step on a phone. Never ask for a password or payment authentication code in an ordinary support reply.

Save the final wording with a review owner and date. Use the knowledge-base guide for answers that deserve a reusable page, and the follow-up plan for promises that need another check. A template should reduce typing while leaving the person responsible for what it says.