The complaint has been open for two days. It runs to four paragraphs, two of them about how long this has already taken. Somebody has to answer it, and the reply that gets written in a hurry tends to contain the one sentence that turns a solvable problem into a formal escalation.
Templates help with this, but not in the way most template lists assume. The wording matters far less than the order, and the order follows from one question: what is this person actually asking for? Get that wrong and a beautifully written reply answers a complaint nobody made.
Work out what is being asked for before writing anything
Almost every complaint contains one or more of four asks, and they are not interchangeable.
Fix it. The parcel is missing, the invoice is wrong, the account is locked. The sender wants an outcome and is largely indifferent to the explanation. Long apologies delay the only thing they came for.
Acknowledge it. Something happened that cannot be undone. A missed appointment, a rude exchange, a deadline gone by. The sender wants it recorded and taken seriously. An offer of a discount in place of that acknowledgement reads as an attempt to buy silence.
Stop it happening again. Often the ask in complaints from long standing customers and from people reporting something they were not personally harmed by. These senders are giving away useful information, and they notice when the reply treats them as a case to be closed.
Compensate. Sometimes stated outright, sometimes implied by a list of costs incurred. This is the one ask that should never be answered faster than the organisation can actually decide.
Two of those asks can be satisfied in the first reply and two usually cannot. Naming which is which, in the reply itself, is most of what distinguishes a good complaint response from a defensive one.
A second reading is worth the thirty seconds it takes: mark the specific verifiable facts. Dates, order numbers, names, amounts. Those are what the reply must reflect back, because reflecting them back is the only convincing proof that the complaint was read rather than processed.
The order that lowers the temperature
There is a sequence that works across almost all complaint types, and it is not the sequence that comes naturally under pressure.
First, the specifics. One sentence that restates what happened, using their dates and their numbers. This is where a reply earns the right to say anything else. "The order placed on 12 September arrived on 24 September, nine days after the date given at checkout" tells the reader they have been understood.
Second, the apology, and only for the thing that happened. Short, specific, unconditional. The apology belongs early, but after the restatement, because an apology that arrives before any evidence of comprehension reads as a formula.
Third, the explanation, kept brief and never used as a defence. Two sentences at most. The purpose of an explanation is to show that the cause is known, which is what makes a promise of prevention credible. The purpose is not to transfer responsibility to a courier, a supplier, a system or a policy.
Fourth, what has already been done. Past tense, concrete. This is the single most effective element of any complaint reply, and it is the one most often missing, because it requires doing something before writing.
Fifth, what happens next, with a date and an owner. Including a date for the next contact even when the resolution is not yet known.
Sixth, the route to escalate. In regulated sectors this is usually mandatory. Everywhere else it is a sign of confidence, and it tends to reduce escalation rather than invite it.
The apology is the one element people get wrong twice: once by leaving it out, once by spreading it across every paragraph. One clear apology, positioned second, is worth more than five hedged ones.
The phrases that make it worse
Each of these is common, and each of them predictably escalates.
We apologise for any inconvenience caused. The conditional turns an apology into a disclaimer. There was no any. There was a specific inconvenience, and naming it costs nothing.
As per our terms and conditions. Quoting the contract in a first reply signals that a dispute is anticipated. Where the terms genuinely decide the matter, say what they mean in ordinary words and cite them only if the reply is refusing something.
Unfortunately, our policy is... Policy is not a reason. It is a decision somebody made. A reply that hides behind it invites the sender to ask who made it, which is a worse conversation.
Could you provide your order number and the date of purchase? When the complaint already contains both. Asking for information the sender has already supplied is the fastest way to prove the complaint was not read.
Your complaint has been escalated to the relevant team. No named person, no date, no commitment. This sentence is experienced as a filing cabinet closing.
I am sorry you feel that way. An apology for their emotional state rather than for the event. It reads as a denial that anything happened.
Adding people to the copy line without saying why also belongs here. From the sender's side, a reply that suddenly involves four addresses looks like an internal defence being assembled.
A service failure, where the fix is available
Subject: (reply in the existing thread)
The order placed on 12 September arrived on 24 September, nine days
after the delivery date shown at checkout, and two calls to the
support line went unanswered on 18 and 19 September.
That is a clear failure and the apology here is unreserved.
The cause was a warehouse transfer that left a batch of orders
unallocated for several days. The unanswered calls were a separate
problem with the line during that week.
What has been done: the delivery charge of 8.50 has been refunded to
the original card this morning, and the order record now shows the
correct dates.
What happens next: the batch handling fault is with the operations
lead, and a note will follow by Friday 3 October confirming the check
that has been added. Replying to this message reaches the same person
throughout.
A complaint about conduct, where nothing can be undone
Subject: (reply in the existing thread)
The account of the appointment on 22 September has been read in full,
including the exchange at reception and the comment about the waiting
time.
That is not the standard this service holds itself to, and the
apology for it is unqualified.
What has been done: the account has been recorded in full and passed
to the manager responsible for the reception team, named below, who
has it today.
What happens next: a reply setting out what has been addressed will
come from her by 7 October. No further detail is needed from your
side unless there is something to add.
If the response is not satisfactory, the complaints procedure is set
out on the website and a formal complaint can be made at any point,
including now.
A billing error
Subject: Invoice 20260914, corrected
Invoice 20260914 charged 480.00 for three licences. The agreement
signed in March covers two, at 320.00. The overcharge is 160.00.
The error is on this side and the apology for it is unreserved.
What has been done: a credit note for 160.00 was raised this morning
and is attached. The subscription record has been corrected to two
licences, so the next invoice will be right.
What happens next: nothing is needed from your side. The credit will
appear against the account within three working days, and a reply
here will reach the same person if it does not.
Where the answer is going to be no
Subject: (reply in the existing thread)
The request to refund the March and April charges has been read, and
the frustration behind it is understood.
Here is the position honestly. The account was active and in use
throughout both months, and the charges reflect that use, so a refund
for the period is not something that can be granted.
What can be done: the cancellation has been processed today with
effect from the end of the current period, so no further charge will
be raised, and a copy of the usage record for both months is attached
so the position can be checked independently.
If this outcome is not acceptable, the complaints procedure is on the
website and includes a review by someone not involved in this
decision.
Where the answer needs time
Subject: (reply in the existing thread)
The complaint sent on 24 September about the figures in the annual
statement has been received and read.
Establishing what happened means pulling the transaction history for
the whole period, which takes longer than a same day reply allows.
Rather than sending a guess, here is the timetable.
The review is with the accounts lead, named below. A full written
answer will be sent by 10 October. If anything is needed from your
side before then, it will be requested in one message rather than
several.
Every one of those five names a date. That is the element that holds a complaint in place while the work happens.
Timing, and who signs it
Acknowledge within one working day, even when nothing can be resolved. The acknowledgement is not the reply: it is the thing that stops the complaint being repeated to a regulator, a review site or a social network while the real answer is being prepared. A complaint that gets no response for four days generates a second complaint about the lack of response, and the second one is harder to answer than the first.
Sign with a name. A reply from a team, a department or an unattributed mailbox tells the sender that nobody has accepted the matter, which is the specific fear that made them write at length in the first place. Where the person replying is not the person who will resolve it, name both.
Match the channel unless there is a reason not to. Answering an emailed complaint by telephone can be a kindness and can also look like an attempt to keep the exchange off the record. Where a call is genuinely better, send a short email first offering it, and follow the call with a written summary.
How the reply changes with the channel it will end up on
A complaint reply is rarely read only by the person it is addressed to. It gets forwarded to a partner, pasted into a review, quoted to a regulator, or screenshotted. Writing with that in mind changes very little about the substance and quite a lot about the tone.
The test worth applying before sending is whether every sentence would still read well out of context. Sentences that fail that test are usually the defensive ones: the reference to the contract, the note about how unusual this is, the observation that the issue was reported late. None of those help the recipient, and all of them look bad quoted on their own.
A second test concerns the facts. Anything stated as fact in a complaint reply may later be checked against records the organisation holds, so a reply should not assert a cause that has not been established. Where the cause is still unknown, saying that it is being established, with a date, is stronger than a plausible guess that turns out to be wrong. Retracting an explanation in a second email costs more credibility than the delay would have.
There is also the question of length. Long complaint replies tend to be long because they are arguing. A reply that restates the facts, apologises once, says what has been done and names a date rarely needs more than two hundred words, and the brevity itself communicates confidence. Where an explanation genuinely requires detail, the detail belongs in an attachment or a clearly separated section rather than woven through the apology.
Finally, avoid asking the sender to do anything they have already done. Resubmitting a form, repeating an order number, or explaining the problem again to a second person are the three requests most likely to convert a complaint into a formal one. If internal handover is required, carry the information across internally and say in the reply that nothing needs to be repeated.
Complaints that arrive through a form
Most complaints now arrive through a contact form rather than as an email somebody composed, and that changes the operational problem more than the wording one.
A complaint in a mailbox has no status. It cannot be seen to be waiting, it has no owner unless somebody claims it, and it holds no record of the promise made in the first reply. When the reply said 3 October, nothing anywhere knows that, so the date passes and the sender chases. In a shared mailbox the same complaint can also be answered twice with two different dates, which is worse than answering it once badly.
Three things fix the operational half. The form's automatic receipt should confirm what was submitted and give a realistic time frame, so the first hour does not generate a chasing email. Every complaint should get a named owner and a visible stage the moment it lands, so that one sitting untouched for three days is something the team can see. And the emails sent about it should live with the record rather than in someone's sent folder, so that the next person to open it can see what was promised and when. Tools built for the stage after the form is submitted work this way by default, which is the difference between a complaint process and a mailbox with good intentions.
The pattern side matters too. Complaints held as individual threads teach nothing. The same complaints held as records with tags show, after two months, that a third of them concern one step in one process, which is the information that stops the next fifty from being written.
What to change first
Take the last complaint reply that went out and check the order. If the explanation came before the restatement of what happened, or if the apology contained a conditional such as any inconvenience, rewrite those two sentences and use that version as the house pattern.
Then give every complaint an owner and a date on arrival, because the promise made in the first reply is the thing most often broken and the easiest to keep. The Halict questions page covers how the receipt and the status side fit together.
Q1. How quickly should a complaint email be answered?
Acknowledge within one working day even if the investigation will take a fortnight, and give a date for the full answer in that acknowledgement. The delay itself becomes a second complaint once it passes a few days, and the second one is harder to resolve than the first because it is about the handling rather than the original event.
Q2. Should the reply apologise even when the organisation is not at fault?
Apologise for the experience and for anything that genuinely went wrong in the handling, and be straight about the rest. What damages credibility is an unconditional apology followed by a refusal, because the two contradict each other. Stating the position plainly, attaching whatever evidence allows the sender to check it, and giving a route to a review by someone uninvolved is more respectful than a softened refusal.
Q3. What phrases should be avoided in a complaint response?
We apologise for any inconvenience, because the conditional undoes the apology. As per our terms and conditions and our policy is in a first reply, because both read as preparation for a dispute. I am sorry you feel that way, which apologises for an emotion rather than an event. And any request for information the complaint already contains.
Q4. Is it better to send a complaint response by email or to call?
Email, unless there is a specific reason a call is better, because the written record protects both sides and lets the sender read it more than once. Where a call will clearly help, offer it by email first and send a written summary afterwards. A call that replaces the written answer can look like an attempt to keep the exchange off the record.
Q5. How should a team keep track of complaints that arrive through a web form?
Give each one a named owner and a visible stage the moment it arrives, keep the sent emails attached to the record rather than in individual sent folders, and set the automatic receipt to state a realistic time frame. Tagging them also turns a pile of individual threads into evidence about which step in which process is generating the complaints.