Skip to main content
FHAVI

Free template

Ten replies that end a conversation instead of extending it

Most support threads escalate because the first reply answered the process instead of the question. These are the ten situations that generate nearly all ecommerce support volume, with the structure that closes each one — copy, then adapt the details.

Before the templates

Four rules that matter more than the wording

Answer the question in the first sentence. Customers read one line and decide whether you are helping. “Thanks for reaching out, we understand your frustration” before an actual answer reads as deflection.

Give a specific next step with a date or an owner. “We will look into it” creates a follow-up; “I have asked the courier and will reply by Thursday” does not.

Never promise what you cannot control. If the courier is late, say what you know and what you will do, not what you hope.

One thread, one owner. Reassigning a thread mid-conversation forces the customer to repeat themselves, which is the most reliable way to turn a question into a complaint.

The ten

Structure first, wording second

01

Pre-delivery

  1. Where is my order — state the dispatch date, the tracking link, the expected window from your measured times, and what you will do if it passes that window.
  2. Change of address — confirm whether it has dispatched. Before dispatch: change it. After: explain the carrier redirect option rather than promising a change you cannot make.
  3. Cancel my order — dispatch status first. Before dispatch, cancel and confirm the refund method and timing. After, explain that it becomes a return.
  4. Order confirmation follow-up — a short message restating what was ordered, where it ships and the delivery window. This one prevents more tickets than it answers.
02

Post-delivery

  1. Damaged on arrival — ask for photographs, confirm the replacement or refund immediately, and say who covers the return. Do not open with a policy.
  2. Wrong item received — same structure, plus what to do with the item they have. Usually cheaper to let them keep it than to arrange a return.
  3. Item not as described — accept, ask what differs, and offer the two options in the same message rather than a negotiation.
  4. Does not fit — give the return instructions, the size guidance for next time, and the refund timing in one message.
03

Difficult ones

  1. Refund chase — state the refund date, the method, the number of working days, and the reference. If it is late, say so and give a new date.
  2. Chargeback or dispute — respond with facts only: order details, delivery evidence, the customer's own messages. Never argue about intent, and never mention the word fraud in the first reply.

After the templates

Three numbers to track monthly

04

What to measure

  1. First-response time, in working hours, not calendar hours.
  2. Share of threads resolved in one reply — the number that actually measures whether the template works.
  3. Refund and dispute rate per hundred orders, split by reason, so you can see which page or supplier is generating the contacts.

More resources

Keep going

The rest of the library

Every checklist here is free and ungated. The research pages carry the reasoning behind them.

All resources · Research library

Support volume growing faster than orders?

That is usually a product-page or delivery-promise problem showing up in the inbox. Tell us your top three ticket reasons and we will say which.

Prefer email? Write to md@fhavi.com