Notes for owners · Channel and customer growth
How to handle customer complaints and escalations
Handle a complaint by acknowledging it fast, giving it one owner, telling the customer what will happen and when, then fixing the cause.
The GullySales team · Updated 15 Sept 2026 · 7 min read
Rules for this trade differ by state and professional body, and they change. Check the current position with your own council or adviser before you act on anything here.

On this page
Handle a complaint in four moves. Acknowledge it within the hour, by voice if the customer is angry. Give it one owner and one reference number. Tell the customer what will happen, who is doing it and by when, then keep them informed even when there is nothing new. Fix the underlying cause afterwards and tell them you did. Most customers who leave after a problem do not leave because of the problem. They leave because nobody told them anything for four days and they had to ask twice.
Why complaints turn into escalations
An escalation is almost always a failure of communication rather than of repair. The sequence is predictable.
The customer reports a problem to whoever they have a number for. That person is not the person who can fix it, and the message is passed on verbally. No reference is created, so nobody can say what stage it is at. The customer calls again on day two and speaks to somebody new who asks them to explain from the beginning. On day three they call the owner's mobile, or they write a Google review, and now three people are working on it while the original repair has not started.
Nothing in that story is about technical difficulty. It is about ownership, a record and a promised time. Fix those three and the volume of escalations drops before the quality of your product changes at all.
The first hour
The first hour decides the tone of everything that follows. Four things belong in it.
Acknowledge, by the channel they used and by phone if the tone is angry. A written acknowledgement to a furious customer reads as hiding.
Create the record. A reference number, the customer, what happened, when, who is affected, and the impact. The impact line is what sets the priority. A bakery whose oven has stopped is losing a day of sales, which is not the same as a cosmetic defect on a delivered cupboard.
Name the owner out loud. "Rajesh from our service team is handling this, his number is this, he will call you by four o'clock."
Set the next contact time, not the resolution time. You often cannot promise a fix in the first hour. You can always promise a call, and keeping that promise buys you the time to fix properly.
An escalation ladder
Write this once, put the names on it, and give it to everybody who answers a phone.
| Level | Trigger | Owner | Respond within | Resolve within |
|---|---|---|---|---|
| 1 | Any complaint received | Service coordinator | 1 working hour | 2 working days |
| 2 | Level 1 time missed, or work stopped at the customer's site | Service or operations manager | 2 hours | 1 working day |
| 3 | Customer asks for a senior person, or a second occurrence of the same fault | Department head | Same day | Agreed date, communicated |
| 4 | Public review, legal notice, consumer forum, or a key account at risk | Owner or director | Same day, by phone | Written response and a plan |
Two rules make the ladder work. Escalation is automatic on the clock, not on the customer's anger, so the coordinator does not have to judge whether somebody is upset enough. And the lower level stays involved after handing up, because the customer should not have to re-explain.
Say the four sentences
Train your team on four sentences and most calls improve immediately.
"I understand, and I am sorry this happened." Not an argument about who is at fault.
"Here is what I know, and here is what I do not know yet." Honesty about the unknown is what makes the rest believable.
"This is what I am doing next and when I will call you back." A time, not "shortly".
"Is there anything that makes this urgent at your end today?" This one is the most valuable, because it uncovers the wedding on Saturday, the audit on Monday, or the export shipment that changes your priority.
What to leave out: "as per our policy", "the system does not allow", and "that is the vendor's problem". Also leave out any mention of what the customer did wrong before the matter is settled.
Fix the cause, not just the case
A complaint that is closed without a cause is a complaint you will receive again. Once a month, take every complaint from that month and sort them into buckets: product defect, delivery, installation, communication, billing, expectation set during the sale.
The last bucket is the one owners are most surprised by. A large share of complaints in Indian SMEs originate in the sale, where something was promised that operations never agreed to: a delivery date, a specification, a free service visit. That is not a service problem and no amount of service training fixes it. It is fixed by changing what the sales team is allowed to promise.
Feed the monthly summary back into the sales process, the installation checklist and the product page on your website, where the honest answer prevents the complaint before it happens.
A worked example
For example, imagine a facility management company in Bengaluru with forty sites across the city, including office parks in Whitefield and two apartment complexes near Hebbal. The details and figures below are illustrative. Complaints arrive on the supervisor's phone, on a WhatsApp group with the client's admin head, and occasionally to the director.
For example, the change is small and structural. Every complaint enters one WhatsApp business number that writes into a register with a reference. The site supervisor owns level one with a one-hour acknowledgement. Anything open beyond two working days moves to the operations manager automatically. A weekly sheet shows complaints per site, and the director's review looks at the three sites with the most.
The finding is usually that a small number of sites generate most of the complaints. The reason is staffing or an unrealistic promise in the contract, rather than the quality of work. That is a contract and rostering decision. Without the register, it looks like a general service problem and the company trains everybody.
What to measure
Complaints received, by cause and by site or product. Acknowledgement time. Resolution time against your promise. Escalations as a share of complaints, which should fall as the ladder becomes habit. Repeat complaints on the same cause, which is the only real measure of whether you fixed anything. And retention of the customers who complained, because a complaint handled well leaves a customer more loyal than one who never had a problem.
What to do next
Write your escalation ladder on one page this week, with real names, real mobile numbers and real hours, and give it to everyone who answers a customer. Then take last month's complaints and sort them by cause. If a third of them trace back to something promised during the sale, start there. If you would like an outside view of where your complaints originate and what they are costing you in repeat business, tell us what you need.








