A complaint hiding in the support queue
A customer emails support about a bill that doubled after a tariff change. The engineer answers the technical part and closes the ticket. The customer emails again, more angry, and copies in the account manager, who replies from their own inbox. A week later the customer writes to a director saying they have raised a complaint three times and nobody has taken it seriously.
Were they right? Looking back, the first email was clearly a complaint. It just did not look like one to someone fixing a bill. There is no complaint reference, no start date, and three people have partial copies of the conversation. If the customer asks for a letter they can take to an alternative dispute resolution scheme, nobody is quite sure what the right date to count from is.
Most small telecoms businesses handle complaints well in practice. What they lack is a record that shows it.
Why complaints slip through
- Complaints arrive through support, sales, finance and directors, not one channel.
- Staff fixing a problem do not always recognise that the customer has complained.
- Your complaints code sets stages and timescales, but nobody is counting the days.
- Letters (acknowledgement, final response, deadlock) are written from scratch each time.
- There is no summary of complaint numbers, causes and outcomes for your own reviews.
The regulator's rules for complaint handling and your own published code decide what you must do. This article is about keeping the record; the requirements themselves are for you and your adviser to confirm.
What weak records cost
| Gap | Result |
|---|---|
| Complaint not recognised | Customer escalates, trust lost |
| Dates not tracked | Response deadlines under your code missed |
| Letters inconsistent | Customer confused about their options |
| No single history | Hard to show what was done if asked |
| No summary of causes | Same problem keeps causing complaints |
The quieter cost is repetition. Without a log of causes, you cannot see that most complaints come from the same two things, such as price change communication or port delays, which is where fixing the process would help most.
Staff time goes too. A complaint that sits unowned in three inboxes gets answered three times, slightly differently each time, and then someone senior has to read all of it to work out what the customer was told.
The complaint log we build
- A 'this is a complaint' action is added to your helpdesk and email tools, so anyone can flag a message in one click. Messages containing common complaint words are also suggested for review.
- Each complaint gets a reference, a start date, a category and an owner, with the full history of messages linked, whoever received them.
- The stages and timescales from your own complaints procedure are set up as rules. The log counts the days and warns the owner before each deadline.
- Letter templates (acknowledgement, update, final response, and the letter explaining the customer's right to take the matter further) are filled from the case and reviewed before sending.
- Resolution, any credit or goodwill given, and the root cause are recorded when the complaint closes.
- A monthly summary shows numbers, causes, time to resolve and outcomes, ready for your management meeting.
We set this up to follow your procedure as written. If your procedure needs updating, that is a conversation for your compliance adviser; we build to what you decide.
What you have afterwards
Every complaint has a reference, an owner and a clock. Customers get consistent letters at the right points. Directors see open complaints and approaching deadlines at a glance. And if you are ever asked to show how a complaint was handled, the history is in one place rather than spread across four inboxes.
Over time, the cause summary becomes one of the more useful reports you have, because it points straight at the processes that annoy customers most.
Signs your complaint handling needs a proper log
- Complaints are handled in normal support tickets or personal inboxes.
- Nobody could tell you today how many complaints are open.
- Deadlines under your complaints code are tracked from memory.
- Letters are written fresh each time.
- You do not know the most common cause of complaints.