Handling complaints in written channels: a process, not just good intentions

Complaints rarely go wrong because of tone of voice. They go wrong in places no training course discusses: a case arrives after hours on Friday and nobody takes ownership, the customer receives a confirmation with no deadline, and when they follow up a week later, there is no history because it sat in a private inbox. Empathy is necessary, but it cannot replace a process.

Why a complaint is not an ordinary ticket

An ordinary question about product availability can be handled in any order, and nobody will remember whether the answer came after two hours or five. A complaint is different because the person on the other side has already paid and is already dissatisfied. Every hour of silence feels like evasion. That changes the requirements of the process, not the people. A subscription cancellation request is just as urgent, because a delay can mean another charge; our guide to subscription cancellation without a retention maze covers how to handle it.

• It has a deadline, not just a priorityThe case cannot simply “wait until tomorrow,” because the passage of time is part of your commitment to the customer.
• It requires a decision, not informationSomeone must accept it, reject it, or propose a solution — replying alone does not close the case.
• It may be read laterThe correspondence may reach a consumer ombudsman, a bank, or a court. Write it as if a third party will read it.
• It has an emotional clockCustomers remember not only the problem, but how many times they had to follow up.

The conclusion is simple: a complaint needs a separate path in the same system where you handle all other contact. Not a separate tool and not a separate inbox — a separate path. If you do not yet have a layer that gives cases a number and status, start there, because the rest of this article has no foundation without it. We describe that layer in our article about a customer service ticketing system.

Statutory complaint-handling deadlines depend on who submits the complaint, what it concerns, and the agreement between the parties. This article covers operations only and is not legal advice. Confirm specific deadlines and mandatory response elements with a lawyer who understands your industry, then enter them in the process as fixed parameters.

The case journey: intake, confirmation, deadline, escalation, closure

A good complaint process fits on one sheet of paper, and every stage answers the question: who needs to act now, and by when? If the answer at any stage is “someone on the team,” that is exactly where cases disappear.

1. Intake.The case receives a number and enters the unassigned queue with new status. Chat, the form, and a contact request all create the same object.
2. Confirmation.A brief message with the case number, what was recorded, and the date of the substantive response. Without a date, the confirmation does not do its job.
3. Owner and internal deadline.One responsible person and in-progress status. The internal deadline is earlier than the date given to the customer, leaving time for verification.
4. Findings.Everything agreed with the warehouse or accounting goes into an internal note on the case, not a messenger. Set waiting-for-customer status only when you are genuinely waiting.
5. Escalation.A rule, not a reflex: after an agreed period, a case without a substantive response goes to a supervisor together with its history. This is a change of assignment, not a hallway conversation.
6. Closure.Set resolved status after sending the decision, and closed after the period in which the customer may return with a follow-up question.

If an earlier reply contained incorrect information, use the guide: Correcting wrong information sent to a customer.

The anatomy of a good written response

A complaint response has one job: end uncertainty. The customer wants to know whether you understood their report, what decision was made, what will happen now, and when. Everything else is filler, and filler in a complaint response reads like a smokescreen. The proven paragraph order runs counter to instinct — the decision goes near the top and the reasoning below it.

1. Paragraph 1 — what the customer reported.Two sentences in your own words, including the order number and date. Proof that someone read the case rather than pasted a stock phrase.
2. Paragraph 2 — the decision.Complaint accepted, partially accepted, or rejected. A direct statement with no preamble.
3. Paragraph 3 — why.A brief explanation based on what you checked. Facts and findings, not clause numbers without explanation.
4. Paragraph 4 — what happens now.A specific action, date, and person. “The PLN 249 refund will reach your account by 20 August” instead of “the refund will be processed.”
5. Paragraph 5 — what to do if this is not enough.One sentence with a contact channel and the case number. A customer who knows where to return is less likely to go elsewhere.

• The decision appears in the first half of the message, not the final sentence.
• Every promise has a date, and that date is entered in the system as the case deadline.
• The case number appears in the body, not only the subject line.
• Replace “an error occurred” with “we made a mistake.”
• Do not refer to internal departments and procedures the customer does not know.

Templates are necessary because without them, responses vary from person to person. The problem begins when a template covers the entire message. A good compromise is to standardize only the first and fifth paragraphs, while writing the decision, reasoning, and action plan from scratch for every case. That is a difference of four sentences, but it completely changes how the message is received. For fault reports, add a sentence to the fixed part of the template that names both of the customer’s routes, as shown in our guide to warranty vs statutory rights.

The language of each sentence is a separate layer — it determines whether a correctly structured response sounds human. We collected examples in our article about plain language in customer service responses.

When replying to an upset customer, use the guide: Replying to an angry customer: six practical examples.

Phrases that make the situation worse

Some phrases survive in complaint correspondence only because they seem safe and polite. From the customer's perspective, they do the opposite: they shift blame or leave the customer without a deadline. Below are alternatives worth adding to your team's templates.

↔ Scroll the table sideways to see all columns.

Once a quarter, review closed complaints and note the phrases after which customers replied with irritation or asked for a phone call. It is the least expensive source of template improvements because it comes from your own cases, not a generic guide. A complete event timeline for every ticket reduces such a review to an hour.

When to move the conversation to the phone

Written channels have an advantage that is easy to forget: they leave a record. That is why complaints should be handled in writing by default, with the phone used to unblock a case rather than escape a difficult message.

• You have exchanged three or four messages and still disagree about the facts.
• The case requires details the customer cannot describe in writing, such as a fault symptom or installation method.
• The decision is a refusal and the case is emotionally difficult: the call precedes the written response, not replaces it.
• The customer asks for a phone call.
• You are not calling to avoid a documentary record or a written decision.

One condition is non-negotiable: after the call, the agreement goes back into the case. A short message saying, “as agreed in today's conversation, we established X and will complete Y by Friday” closes the gap that generates the most disputes. The call itself should not be improvised either — a contact request with a chosen time prevents a series of missed calls. We describe the mechanics in our article about website callbacks.

Measurement: how to tell whether the process works

Complaints are where it is easiest to confuse an improved metric with improved service. Simply send intake confirmations faster and first response time looks excellent even though resolution time remains unchanged. That is why four numbers should always be read together, never separately.

↔ Scroll the table sideways to see all columns.

Two things determine whether these numbers are reliable. The first is measuring in the team's working hours — a complaint submitted on Friday evening should not be burdened with the weekend, because then the report measures the calendar rather than service. The second is reading the median alongside the extreme value: one case dragging on for three weeks matters more than ten closed in an hour. We break down the calculation method in our article about first response time in live chat, and cover the quality dimension in our piece on customer satisfaction surveys.

A practical review rhythm: once a week, list overdue cases; once a month, check the median and extreme values for both time metrics; once a quarter, review reopened cases and ratings alongside a sample of responses. That is enough to keep the process from stagnating and costs less than another communication course for a team that has no way to see where cases stop.

Some cases end in a public review that tells a different story from your records. We explain what you may and may not write publicly in our article about negative reviews and case histories.