Playbook, online store
They have read the policy already. Quoting it back is the wrong move
Everything else in this file is somebody looking for information. This is somebody who has the information, has had it twice, and wants a person to be responsible. That changes what a good reply contains: not more facts, fewer. The specific failure available here is the reflex an assistant has of being helpful by restating the terms, which to this reader is the company saying the same thing a third time.
Why this is not the general answer
The handling pattern for complaints holds across every trade. What follows is the part that does not.
- A complaint on a shop is almost never a first contact. It follows a delivery that went wrong, an email nobody answered, or a refund that did not appear, and the person has already had the relevant policy quoted at them at least once.
- The escalation threat specific to this trade is a card dispute, and once it is raised the shop is on a clock to assemble evidence, so the only thing worth optimising in the reply is the speed at which a person sees it.
- A public review is being drafted in the same sitting, frequently in another tab, which means a defensive or templated reply is not a private exchange but a screenshot with a caption on it.
- What is being demanded is accountability rather than information, a person with a name and the authority to decide something, and an assistant that responds with more information reads as the company hiding behind a form.
How it arrives
- this is the third time ive contacted you
- nobody has replied to my emails
- i want to speak to a manager
- im going to my bank about this
- ill be leaving a review about this
- who is actually in charge of customer service
What has to be indexed for this to work
| Your complaints route, written as a named process | Where a complaint goes, who owns it, and what the stages are if there is more than one. Not the general contact address. A complainant who is given the same address they have already written to twice reads it as being sent round the loop again. |
|---|---|
| What a complaint needs to contain to be actionable | The order number, the checkout email, the dates of previous contact and what outcome they are asking for. That last one is the field nobody collects and the one that lets a person resolve it in a single reply rather than four. |
| The response time you publish for a complaint | If it differs from ordinary support, say so and say what it is. If it does not differ, say that instead. What must not happen is an invented timescale, because the person reading it is already keeping a record of what they were told and when. |
| An acknowledgement you would stand behind in writing | One or two sentences, drafted in advance, that recognise the situation without accepting fault, agreeing an outcome or characterising what went wrong. This is the material that stops an improvised apology becoming an admission somebody quotes later. |
The reply
I am sorry this has taken three attempts, and I am not going to repeat the policy at you. I cannot open orders or make a decision on this, so the useful thing I can do is get it in front of somebody who can, with everything they need to act on it first time. If you leave your name, the email on the order, the order number and one line on what you want to happen, that goes to the team as an enquiry and they reply to that address. Please include the dates you contacted us before, because that is the part that gets your message treated as a repeat rather than a new one.
The apology is for the number of attempts, which is a fact, rather than for what went wrong, which is a judgement nobody has made yet. Saying outright that the policy is not coming again defuses the thing this reader is braced for. Asking what outcome they want is the one question nobody has asked them, and it changes the tone of the reply that comes back. The dates matter because they are what stops the message joining the back of the same queue.
Where it stops
The trigger. Anything that reads as a complaint rather than a question, and immediately on any mention of a bank, a dispute, a review, a regulator, a solicitor or a manager.
This needs a person, and I would rather get you to one now than keep you here. Leave your name, the email on the order, your order number and what you want to happen. It goes to the team as an enquiry and the reply comes back to that address.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never quote the returns, delivery or refund policy at somebody who has said they have already been told it, which is the single most inflammatory thing available in this conversation.
- Never accept fault on the shop's behalf, agree that a colleague was wrong, or characterise what happened, since the transcript is likely to be attached to a dispute.
- Never ask somebody to explain the whole thing again from the start when they have said this is a repeat contact, because it confirms exactly what they are complaining about.
- Never promise a manager will call, name an individual, or commit to an outcome or a timescale nobody in the shop has agreed to.
Questions
- Should it try to resolve the complaint itself?
- No. It cannot open an order, issue anything or make a goodwill decision, and a complaint is a request for exactly those. Attempting a resolution it cannot deliver adds a fourth failed contact to the list the customer is keeping.
- Does an assistant make complaints worse?
- It does if it answers them. It helps if it recognises one and gets out of the way fast, with the identifiers collected. The thing complainants object to is the loop, and a form that reaches a person in one step is shorter than the loop they are in.
- What should the acknowledgement actually say?
- As little as possible while still sounding human. Sorry it has taken this many attempts, I cannot decide this, here is what I need to get it to somebody who can. Every additional sentence is a sentence somebody can quote in a review.
Keep reading
- Everything for a online storeDelivery cut-offs, the returns window and restock questions get asked before purchase. The one thing an assistant cannot do is find an order.
- Handling complaints in generalThe job is to route, not to resolve. Acknowledge without conceding, name the escalation route, and get it to a person fast.
- There is no such thing as a size on a general storeOne store, a dozen suppliers, a dozen charts that disagree. What size means changes by aisle, and the chart is usually a picture.
- Sending them to the manufacturer is the reflex that causes the complaintA maker's guarantee and a seller's own obligation are different things, and pointing the customer at the manufacturer is often wrong.
- There was never an account, only an email address on an orderGuest checkout leaves an email with orders behind it and nothing to sign into. Most access problems on a shop start right there.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.