Customer Complaint Management in a CRM: A Ticket per Issue

Customer complaint management in a CRM means every complaint, return request or service call becomes a ticket with a category, an owner, a priority, a target time your business sets and an escalation path, and it closes only when the customer confirms the problem is over. In part four every sales opportunity got a stage and a next step; this fifth part of Digitizing CRM, a 7-part series, moves to what comes after the sale: 5 fields on every ticket, personal data requests that the implementing regulation caps at 30 days, the rule of closing on the customer's confirmation, and how recurring complaints feed back into operations, with an exercise on last month's complaints.

From an angry message to a ticket: what goes in and where it comes from

After the sale, a customer comes back to you for one of 4 reasons. A complaint, because something did not happen as you promised: a late delivery, a defective product, the wrong item, or treatment they were unhappy with. A service request: an installation, maintenance, a technician visit or a spare part. A return or exchange request. Or a request about their personal data, such as correcting their name or deleting their number, which we cover below because it carries a legal deadline.

These requests arrive through the same channels as inquiries: WhatsApp, calls, email, the branch, the salesperson's phone, and a note a technician writes at the customer's site. In part three we brought these channels into one inbox where every message has an owner and a reply deadline. The difference here is that an inquiry closes with an answer, while a complaint is not closed by an answer but by a fix that may take days and pass through more than one department. So the message is not closed in the inbox; it becomes a ticket.

A ticket is one record for one problem: a number sent to the customer as soon as it opens, a description of the problem in the customer's own words, a link to the customer record we built in part two and to the order or item it concerns, and everything that happened in it, with dates and the name of whoever did it. Each problem gets its own ticket: if a customer complains about a late delivery and a defective product together, that is two tickets, because each has a different owner and a different fix. The ticket number alone saves the customer from retelling the story on every call, and saves your employee from searching old chats.

5 fields on every ticket: category, owner, priority, target time and escalation

A ticket that carries only a description stays an archived message. What turns it into a management tool is 5 fields filled in when it opens:

• Category. Chosen from a short fixed list your business writes, such as: late delivery, defect or damage, wrong item or quantity, staff conduct, maintenance or visit request, return or exchange, personal data request. A fixed list is what makes complaints countable and comparable, just like the lost reasons in part four, and the employee adds a note beside it.
• Owner. One person's name, not a department. A ticket owned by the whole maintenance department is owned by nobody. The owner may need a colleague in the warehouse or a technician in the field, but they remain the one who tells the customer where their problem stands.
• Priority. 3 levels are usually enough: urgent, normal and low. Write a condition for each level that any employee can check, such as the customer's work being stopped by the problem, or the problem posing a safety risk. Priority is set by the problem's impact on the customer, not by how loud they are on the phone.
• Target time. Two times for each priority: a first-reply target and a resolution target. This is what is called a service level agreement, or SLA: a commitment to a stated time that gets measured. Do not copy another business's numbers; measure how long your complaints take today, then set a target you can meet and tighten it gradually.
• Escalation. Who receives the ticket when its target time passes: the owner first, then their supervisor, then the department manager or the owner of the business. In the system, escalation is an automatic alert when the time passes, not an angry call from the customer that tells the manager something is late.

Escalation you do not build inside your business, the customer may take outside it. Through its Receiving a Commercial Complaint service, the Ministry of Commerce lets a consumer report a violation by an online store or a shop from the Commercial Report app and track the report's status online, and they can also reach the ministry on the unified number 1900. A target time you announce to your customer and keep means they follow up their complaint with you first.

One category is not yours alone to time: customer requests about their personal data, such as correct my name, send me what you hold about me, or delete my number. The customer rarely mentions the law, but Article 4 of the Personal Data Protection Law gives them rights including the right to be informed, the right to access their personal data held by the controller, the right to request a copy of it in a readable and clear format, the right to request its correction, completion or update, and the right to request the destruction of what is no longer needed. Article 21 requires the controller to respond to these requests within a set period and through an appropriate means, both specified by the regulations.

The Implementing Regulation of the law sets this out in its Article 3: requests to exercise rights are carried out within a period not exceeding 30 days without delay, which may be extended by no more than 30 additional days if carrying them out requires unexpected or unusual extra effort or the data subject has made multiple requests, provided the data subject is notified in advance of the extension and its reasons. It also requires verifying the requester's identity before carrying out the request, and documenting and keeping all requests submitted, including oral ones (our reading of the official Arabic text).

In practice, these requests become a category with 4 rules: an internal target time shorter than the regulation's ceiling, an owner who knows the procedure, an identity check before anything is done, and a record of every request, even one made on a call. Article 34 of the law states that the data subject may submit any complaint arising from the application of the law and its regulations to the competent authority. This is not legal advice, so confirm the details with SDAIA or a lawyer.

Close the ticket only on the customer's confirmation

When an employee writes resolved, that is their opinion. The problem is over when the customer says it is over. So a ticket moves through clear statuses: new, then in progress, then waiting for the customer if you need a photo or an appointment from them, then resolved pending confirmation, then closed. In the system, the rule means 3 things:

• A confirmation message on the same channel. When the employee moves the ticket to resolved, the system sends the customer, on the channel they complained through, one clear question: is your problem solved? It saves their reply and its date on the ticket.
• A no reopens it. If the customer says no, the ticket goes back open to the same owner with their reply attached, and no new ticket is opened that would hide the fact that the first fix failed. The same applies if the same problem comes back within a period you set.
• Silence is not confirmation. If the customer does not reply after a number of attempts and a period your business sets, the ticket closes with a separate status called closed without confirmation, so it does not mix with tickets whose customers confirmed the fix, and its count shows up in the monthly review.

When the fix needs a technician visit, the ticket creates a work order carrying the customer's location, the appointment, the technician and the parts needed. The work order itself, from the request number and its status to the notes, photos and customer signature on site, is covered in Work Orders: From WhatsApp Messages to a System That Tracks Every Request. The rule here is that closing the work order does not close the ticket: the technician has finished the visit, but the ticket waits for the customer to confirm the problem is solved.

From complaints to operations: what recurring categories tell you

A closed ticket solves one customer's problem. A category that keeps recurring reveals a cause in operations that will keep producing new complaints until it is fixed. So review tickets once a month with fixed questions:

• The number of tickets in each category compared with last month: which category is growing, and which shrinks after its cause is fixed.
• The actual resolution time in each category compared with the target you set, and how many tickets passed it and reached escalation.
• Reopened tickets, because they say the first fix treated the symptom, not the cause.
• Tickets closed without confirmation, because a rising count means the confirmation message is not arriving, or customers have given up on replying.

Then each recurring category gets an owner in operations, not in customer service: late delivery to whoever runs delivery, damage to whoever runs the warehouse and packing, wrong items to whoever prepares orders, staff conduct to the branch manager. The question shifts from who handled this ticket to why this cause recurred this month, and what we will change. Open tickets also show on the customer record, so a salesperson sees them before calling the customer with a new offer while their problem is still unsolved.

And because tickets carry personal data, from name and mobile number to address and photos of the product in the customer's home or site, permissions are part of their design: a service employee sees the tickets in their categories, photos and addresses go to those who need them to fix the problem, and export is limited to a few people, with a log of who did what and when. Article 19 of the law requires the controller to take the necessary organisational, administrative and technical measures to safeguard personal data.

The Origami view

We are a technology company that builds custom systems, apps and integrations, and in after-sales service projects we do not start with a screen: we sit down with the service manager to write the list of categories, the priority conditions, the target times, the escalation path and who sees what. The reason is that a ticket system whose categories the team never agreed on quickly turns into one more field where each employee writes whatever they like, so complaints can be neither counted nor compared.

Then we build tickets on top of the customer record and the unified inbox described in parts two and three, so a WhatsApp message becomes a ticket with nothing typed twice, the confirmation message goes out on the same channel, a work order is created from the ticket when a technician is needed, and the monthly category report is built from the same data. What we build is described on our services page.

Exercise: last month's complaints from every channel

This is an exercise you can run in one or two sessions with your service team, and it measures how many of your complaints close today with the customer's confirmation:

• Gather every complaint, service request and return request from last month from every channel: WhatsApp chats, the call log, email, the branch notebook, and salespeople's and technicians' phones.
• Give each one 4 columns: when it arrived, who handled it, when it ended, and whether the customer confirmed the problem was solved.
• Mark every complaint where nobody knows who handled it, or nobody knows whether it ended.
• Sort the complaints into categories from your list and count each category.

The number of complaints whose customers confirmed the fix, divided by the total number of complaints, is your confirmed closure rate today, and it is the figure you measure against a month after applying the confirmation rule. The largest category on the list is the first operational fix to start with, while the marked complaints are exactly what gets lost between channels today, and what the single-owner rule will stop.

In the next part

Every complaint and service request now has a ticket with an owner and a target time, it closes only on the customer's confirmation, and recurring categories feed back into operations. Part 6, Customer Marketing Messages: Consent First, by Law, moves to what you say to your customer when they are not complaining: how to obtain their consent to promotional messages and give them a clear way to stop them, as Article 25 of the Personal Data Protection Law requires, how to record that consent in the system with its date and source, how opting out works on every channel, and how to invite them to buy again from their record rather than from a mass list.