Complaint Management: A Process, a Triage Table and a Simple Way to Track Complaints in a CRM

Complaint management is the process of receiving, recording, resolving and learning from customer complaints: every complaint gets an owner, an acknowledgement, a resolution and a check that the customer accepts the outcome. A small team can run it in a CRM such as Customermates by keeping complaints in their own list linked to the customer, as shown below, but Customermates is not a helpdesk and not a regulated complaint-management system.

This guide covers what a complaint management system is, how a complaint differs from a warranty claim, a triage, ownership and escalation table, the seven process steps, ten rules for a good answer, and a worked example of tracking complaints in Customermates with its limits stated next to it.

What is complaint management, and what is a complaint management system?

Complaint management covers everything a business does from the moment a customer says something went wrong until the cause is fixed: receiving the complaint on any channel, recording it in one place, answering, finding the cause, putting it right, checking back and using what you learned so the next customer does not meet the same problem. Two jobs run side by side. One is to solve this customer's problem. The other is to learn from all complaints together.

A complaint management system is whatever holds that process together. It can be a shared spreadsheet, a list in a CRM, a helpdesk with ticket queues, or, in regulated sectors, dedicated software with audit trails. What matters is that every complaint has a record, an owner, a status and a closing decision. Complaint management also differs from general customer service: service answers questions and requests, while complaint management is the defined route for expressed dissatisfaction.

A standard exists. ISO 10002:2018 gives guidelines for complaints handling in organizations of any size, to be used as one process of a quality management system. This guide is not based on it and claims no compliance with it.

What is the difference between a complaint and a warranty claim?

In everyday English the two words overlap. The difference matters when the customer wants a remedy for a defect, because a claim can carry legal consequences and dates that a complaint does not.

Germany makes the split visible. A Beschwerde is any expression of dissatisfaction. A Reklamation is a notice of a defect, usually under the statutory warranty (Gewährleistung). If an item is defective, section 437 of the German Civil Code (BGB) lets the buyer, under the conditions of the following provisions, demand subsequent performance, withdraw from the contract or reduce the price, and claim damages. Section 438 BGB sets limitation periods, generally two years. Between merchants, section 377 of the German Commercial Code (HGB) adds that goods are to be inspected and defects notified without delay. Rules differ by country, between consumers and businesses and by contract, and this is not legal advice.

For your process the lesson is practical: log both in the same list with a Type field, but treat claims as time-sensitive and keep every date, because deadlines can run from them.

How do you triage complaints and decide who owns them?

Triage sorts complaints by type and severity so the right person answers at the right speed. Write the table once, share it with the team and change it when real cases show where it is wrong. Every complaint needs exactly one owner, even when several people help.

Read severity like this as a starting point: Critical is a risk to safety, a legal or data protection issue, or a key account at risk; High means the customer cannot work or a promised date is missed; Normal is a problem with a workaround; Low is a suggestion or a minor irritation.

The response targets above are examples for a small B2B team, not a standard or a legal requirement. You set the first response time yourself: pick targets you can keep, write them down and check them against the real dates. Regulated sectors such as financial services and healthcare can have rules and deadlines of their own for complaint handling; check those for your sector.

What are the steps of the complaint management process?

Seven steps cover the whole route, from the first message to the lesson. Shorter and longer models describe the same route with fewer or more boxes.

1. Receive

   Accept complaints on every channel you use: email, LinkedIn, phone, a remark at the customer's site. Say where customers should send them. Note the channel and the real date and time they arrived.

2. Record

   Create one record per complaint before you reply, linked to the customer. Capture the customer's own words, the type, the severity, what the customer wants and any order, project or invoice reference.

3. Acknowledge

   Tell the customer that the complaint arrived, who owns it and when they will hear back. Do this within the first response target from your triage table, even if you have no answer yet.

4. Investigate

   Find out what happened. Ask the people involved, check the order, delivery or invoice, and write down the cause. Keep blame out of the first reply.

5. Resolve

   Offer a fix, a replacement, a correction, a credit or a clear explanation of why nothing will change. Decide within your authority or escalate along the table, and tell the customer the decision and the reason.

6. Follow up

   Check that the fix worked and that the customer is satisfied. Close the complaint only when the closing criterion is met, and record the closing date and outcome. The follow-up email guide has a check-in template for after a purchase and a timing schedule; the same habits apply to checking back after a fix.

7. Learn

   Review complaints regularly by type and cause. Fix the cause: a template, a checklist, a supplier, a product bug. Complaints are also touchpoints in the retention stage of the customer journey, so they show where it gets hard.

Which rules make a complaint answer work?

There is no official list of golden rules for handling a claim or complaint. These ten are practical rules that hold up in small teams:

1. Answer quickly, even if the answer is "we are looking into it".
2. Read the whole complaint before you reply.
3. Do not argue, and do not blame the customer or a colleague.
4. Acknowledge the customer's experience, and apologise where the fault is yours.
5. Promise only what you can keep, and name a date.
6. Name one owner in the reply.
7. Record every complaint, including those that arrive by phone or in person.
8. Fix the cause, not only the symptom.
9. Check back after the fix.
10. Count and review complaints so that the same one does not come back.

How can a small team track complaints in Customermates?

This section is about our own product, Customermates, an open-source CRM made in Germany. It has no complaint module. What it has are configurable lists, relationships, a board view, tasks and a unified inbox, and a small team can combine them. The setup below is an illustrative manual for a team of a few people, not a customer case. Lists, relationships, the board and tasks work on every plan, including self-hosted. Conversations from the inbox need Customermates Cloud on the Pro plan or higher.

The list uses these fields. Names and options are yours to change; they mirror the triage table.

1. Create the list

   In Configure, add a list called "Complaints" and the fields above. Changing the data model is its own permission, so ask someone who has it. If only some colleagues should read complaints, restrict the list through roles; permissions apply per list, not per field.

2. Link it to the customer

   Add a Relationship between Complaints and Contacts (one contact, several complaints) and, if you work with companies, Organizations. Both records show the link, so the customer record lists its complaints. How relationships link records explains the options.

3. Bring in the conversations

   Keep the customer's email address, phone number and profiles in the contact's Contact details, so their conversations from the unified inbox appear on the contact. In the relationship drawer, switch on the messages for the Complaints side (for example Show their messages on Complaints) so the complaint's Activities show them too. To attach one specific conversation, open Thread settings and pick the complaint under Conversation records; other conversations with that person stay separate. Conversations in a colleague's own mailbox stay private until that thread is shared with the team, and sharing a whole connected account needs the Business plan or higher. The inbox guide has the details.

4. Work the status board

   In Appearance, choose Board. The cards group by Status, and you drag a complaint to the next column as it moves on. The records guide covers the board and sorting. In the table, sort by Respond by to see what is due first.

5. Add tasks with target dates

   Every investigation or repair step becomes a task. Tasks have no built-in due date, so add a Date field such as "Target date" to the Tasks list, as the task management guide describes, and a relationship between Tasks and Complaints. Assign each task to a teammate.

6. Review and learn

   Save a personal view "My open complaints" (views are personal, so each teammate saves their own) and add a dashboard chart that counts Complaints by Type for your regular review. On Customermates Cloud, Mate or your own AI client through MCP can summarize a complaint with its conversations and draft a reply for you to review before anything is sent.

Customermates is the wrong choice if you handle many tickets a day across phone and chat, need SLA timers and automatic escalation, want customers to follow their case in a portal, or work in a regulated sector. It fits when complaints are few and personal, tied to named customers, and the people answering them already work in the CRM. To place this in a wider setup, read the guide to customer interaction management.

FAQ

Third-party sources checked on 2 November 2026: ISO 10002:2018 (edition 3, confirmed in 2023), section 437 BGB, section 438 BGB and section 377 HGB. The German statutes are quoted in summary only and are not legal advice.