Complaints stop depending on how loudly the customer is willing to complain.
Gully Sales helps you log every complaint in one place, give it an owner and a response time, escalate it on a written rule instead of on temper, and count the causes so the same fault stops arriving twice.
- Every complaint logged in one place, whatever channel it arrived on.
- An escalation matrix that triggers on time and severity, not on anger.
- A monthly complaint review that names causes and closes them.
Gully Sales Private Limited works with small and medium businesses across India, and we build the process with the people who answer your customers.
In one paragraph
What is Complaint and Escalation Management?
Complaint and escalation management is the written rule for what happens when a customer tells you something is wrong. Gully Sales gives every complaint a place in one register, a severity, an owner and a response time, sets the ladder a case climbs and the point at which leadership must see it, and counts the causes each month.
The problem
The angriest customer gets attention, and the patient one quietly leaves.
Nobody plans it this way. A complaint arrives on WhatsApp, on a phone call to the director, through the salesperson who sold the order, or in a public review. Whoever hears it first fixes it, because fixing it is faster than logging it. The customer is usually looked after. But there is no record, no time standard, and no way of knowing which complaints were never heard at all. So the business learns nothing from the ones it solved, and never finds out about the ones it lost.
You will recognise it as
- Complaints reach you personally, on your mobile, because customers have learnt that is the only route that produces a quick answer.
- Nobody can tell you how many complaints came in last month, or what the three commonest causes were.
- The same fault appears again from a different customer, and the team fixes it again from scratch.
- A case only escalates when the customer threatens to leave, write a review or speak to a lawyer.
- Two customers with the same problem get different answers, different timelines and different compensation.
- You hear about a serious complaint days later, usually from the customer rather than from your own team.
What it costs the business
- Customers who did not shout stay unhappy and simply stop reordering, so the loss shows up in revenue long before anyone connects it to a complaint.
- Your senior people spend their week inside individual cases, because every difficult customer eventually becomes the owner's problem.
- Credits, free replacements and goodwill are given case by case, with no limit, no record and no view of what they cost across a year.
- Public reviews become the escalation route, and a private service failure turns into something prospective customers read before they call you.
Why it persists. It persists because handling a complaint well and recording it are two different jobs, and only the first one feels urgent. The person on the phone is judged on calming the customer, not on the note afterwards, so the note never happens. There is also nobody who owns complaints as a subject. Support owns tickets, sales owns the relationship, operations owns the fault, and a complaint touches all three without belonging to any of them. So it belongs to whoever is standing closest.
If it stays unresolved. Left alone, the informal route becomes the official one. Customers stop using your support number and go straight to the director, or straight to a public review, because both work faster. Your team stops raising problems it cannot solve on its own, and the complaints you never saw become the reasons you are given for losing customers a year later.
What changes
What changes once a complaint has an owner, a clock and a route upward.
In the first weeks
- Every complaint is logged the same way, whether it arrived by phone, WhatsApp, email, a dealer or a public review.
- Each case has one named owner and a stated time by which the customer will hear something substantive.
In how the work runs
- Your team escalates on a written trigger, so raising a case is a normal step rather than an admission of failure.
- Frontline staff know what they may offer to put things right without asking, and where the limit sits.
- Serious cases reach you early and with the facts attached, instead of late and through the customer.
In sales and marketing
- Recurring causes get fixed once, so the cost of repeating the same rework and the same goodwill gesture falls.
- Customers who complained and were handled well often stay, because recovery is the moment the relationship is decided.
In what management can see
- You can see complaint volume, causes, response times and repeat cases in one monthly view.
- Public reviews carry fewer surprises, because unhappy customers have a private route that answers them first.
Over the longer term
- Complaint data becomes an input to product, delivery and training decisions rather than a private worry.
- The process survives staff changes, because it is written down and not carried in one experienced person's head.
We control the design, the rules, the training and the reporting rhythm. Whether a particular customer stays is decided by your product, your commercial terms and how your team applies the process every day. We will not promise retention figures, and we will always show you what is being measured.
Who it is for
This is for businesses where an unhappy customer costs more than one order.
The businesses it suits
- Service, subscription and contract businesses where the same customer must buy again next month or next year.
- Manufacturers and distributors whose complaints arrive through dealers, sales staff and site engineers rather than a support desk.
- Healthcare, education and hospitality businesses where a single badly handled complaint becomes a public review.
- Companies of roughly fifteen to five hundred people, where support has grown by hiring rather than by design.
- Businesses that already have a helpdesk or CRM, but no rule for what counts as a complaint or when it rises.
- Owners and directors who are personally handling four or five customer problems every week.
What usually prompts the call
- A serious complaint reached you only after the customer had already posted about it publicly.
- A customer left, and the exit conversation described a problem your records never showed.
- You have appointed a service or support head and need to hand over cases with a rule, not with instinct.
- An audit, a large customer or a regulator has asked how complaints are recorded and escalated.
- Goodwill credits and free replacements have grown enough that finance has started asking about them.
What Gully Sales does
The work, component by component.
Complaint definition and case classification
We agree what counts as a complaint in your business, as opposed to a question, a request or a routine service call, and then sort complaints into a small number of categories and severity levels. Severity is set by the effect on the customer, the value at risk and the exposure it creates, not by how strongly the complaint was expressed.
- Why it matters:
- Without a shared definition, half your complaints are never recorded as complaints, and priority ends up being set by tone of voice.
- You receive:
- A written complaint definition, a category list and a three-level severity scale with worked examples from your own cases.
- Business value:
- Your team sorts a new case the same way every time, so the urgent ones surface within minutes rather than after a week of politeness.
Ownership and the complaint register
Every complaint gets one named owner from the moment it is logged, and one place where it lives. We set up the register in the tool you already use, define the fields that must be filled, and close the parallel routes where cases quietly disappear: personal inboxes, individual chat threads and verbal handovers in a corridor.
- Why it matters:
- A case with two owners has none, and a case that lives in a chat thread cannot be counted, reviewed or handed over.
- You receive:
- A configured complaint register with required fields, ownership rules, handover rules and a weekly open-case list.
- Business value:
- Nothing sits unowned, and anyone can answer the question of where a case has reached without ringing three people.
Response and resolution standards
We set the times your business will work to: how quickly a customer hears from a person, how quickly they are told what is happening, and by when each severity level should be resolved or given a firm date. Standards are set against what your team can deliver on a busy day, then published internally and, where useful, to customers.
- Why it matters:
- Most complaint anger comes from silence rather than from the fault itself, and silence is what happens when no time standard exists.
- You receive:
- A response and resolution standard per severity level, with acknowledgement templates and holding-update wording.
- Business value:
- Customers know when they will hear back, and your team is measured on something achievable rather than on doing it as soon as possible.
Escalation paths and the escalation matrix
We map who a case rises to, at what point, and what changes when it does. Triggers are written down: time elapsed without resolution, severity level, value at risk, repeat complaints from the same customer, safety or legal exposure, and public visibility. Each level has a named role, a response time of its own and a rule for telling the customer that the case has moved.
- Why it matters:
- When escalation depends on judgement alone, cases rise either too late or all at once, and leadership loses the ability to tell the two apart.
- You receive:
- An escalation matrix with levels, named roles, triggers, timeframes and the notification that goes to the customer at each step.
- Business value:
- Serious cases reach the right person early, and routine cases stop being pushed upward for safety.
Recovery limits and goodwill gestures
We agree what your team may offer to put a situation right, and at which level. A frontline person gets a small standing authority, a supervisor gets more, and anything beyond that becomes a decision rather than a reflex. We also write the wording, because how a gesture is offered matters as much as what it is worth.
- Why it matters:
- Compensation decided case by case is slow, inconsistent between customers, and invisible to finance until the year is over.
- You receive:
- A recovery authority table by role and severity, approved gesture options, wording for each, and a record of what was given and why.
- Business value:
- The customer receives a decision on the same call, and you can see for the first time what putting things right actually costs you.
Root-cause review and closure
Each complaint is closed with the customer, not only in the system, and then read for what caused it. Monthly, we group the causes, separate the one-off from the repeating, and take the repeating ones to whoever owns the process behind them, with an action, an owner and a date. Causes that stay open remain visible in the next review.
- Why it matters:
- A complaint you solved but never explained will arrive again from a different customer, and it will cost the same to solve the second time.
- You receive:
- A closure checklist, a monthly complaint review pack with cause analysis, and an action log carried between reviews.
- Business value:
- Complaint volume starts falling for reasons you can name, rather than moving up and down without explanation.
What you will have at the end.
- A written complaint definition, category list and three-level severity scale, with worked examples from your own recent cases.
- A complaint register configured in your existing helpdesk, CRM or spreadsheet, with required fields and ownership rules.
- An escalation matrix naming the role, trigger, timeframe and customer notification at each level, on a single page.
- Response and resolution standards per severity, with acknowledgement, holding-update and closure templates ready to use.
- A recovery authority table showing what each role may offer, with approved wording for each gesture.
- Channel intake rules covering phone, email, WhatsApp, website, dealers, field staff and public review sites.
- A closure checklist, so a case is closed with the customer and not only in the system.
- A monthly complaint review pack: volume, categories, causes, response times, escalations and open actions.
- A one-page handling guide for frontline staff, and a briefing session to walk your team through it.
- An anonymised sample register and sample review pack, so you can see the format before we build yours.
- A handover file with every template, rule and report, so the process continues without us.
How it runs
The engagement, step by step.
- 1
Read what already happened
We go through your last few months of complaints wherever they exist: helpdesk tickets, email threads, chat messages you are willing to share, call notes, review sites and the cases your directors handled personally. We are looking for volume, causes, channels, how long each one took and where it stalled.
- You provide:
- Access to existing records, review-site logins or exports, and permission to read a sample of real cases.
- We produce:
- A picture of current complaint volume, the channels they arrive on, the commonest causes and the delay before anyone escalated.
- Done when:
- You and we agree the baseline, including an honest note of what could not be counted.
- 2
Talk to the people who take the calls
We sit with the staff who actually receive complaints: support, service engineers, sales, reception, dealer coordinators. We ask what they do now, what they are allowed to decide, when they escalate and why they sometimes do not. Most of the design comes out of this conversation rather than out of a template.
- You provide:
- An hour each with four to eight frontline people, and the freedom for them to speak plainly.
- We produce:
- A written account of how complaints are handled today, including the informal routes that keep the business running.
- Done when:
- The current process is described in a way your team recognises as accurate.
- 3
Agree definitions, severity and standards
In a working session with you we settle the hard questions: what counts as a complaint, what makes one severe, how quickly each level must be acknowledged and resolved, and what your team may offer without asking. Every standard is tested against a busy week rather than a quiet one.
- You provide:
- Two to three hours from you and the people who will enforce the standards, plus your view on what is affordable.
- We produce:
- The complaint definition, category list, severity scale, response and resolution standards, and the recovery authority table.
- Done when:
- The standards are signed off by the person who will be held to them.
- 4
Design the escalation path
We map each level of escalation to a named role, a trigger and a time, then walk three or four real past cases through the new path to see where it would have caught them. Leadership involvement is agreed explicitly, including which cases you want to hear about on the same day.
- You provide:
- Agreement on who sits at each level, and confirmation of what you personally want visibility of.
- We produce:
- A one-page escalation matrix, the customer notification wording for each step, and the reasoning behind each trigger.
- Done when:
- Past cases run through the matrix produce the outcome your team says they should have had.
- 5
Build the register and the templates
We configure the register in the tool you already pay for, add the required fields, statuses and ownership rules, and write the templates your team will use: acknowledgement, holding update, resolution, closure and the internal escalation note. Where a channel bypasses the system, we set a rule that brings it back in.
- You provide:
- Administrator access to your helpdesk, CRM or shared sheet, and a decision on who administers it afterwards.
- We produce:
- A working complaint register, intake rules for every channel, and a template set your team can use unchanged.
- Done when:
- A test complaint travels from intake to closure without anyone improvising a step.
- 6
Train the team and run it live
We brief everyone who touches a complaint, using your own past cases as the examples, then run the process alongside your team for an agreed period. In that time we sit in on difficult cases, correct the classification when it drifts, and adjust anything that turns out to be unworkable in practice.
- You provide:
- Your team's time for a briefing session, and their live cases to review during the first weeks.
- We produce:
- A frontline handling guide, a briefing session, and weekly corrections during the settling-in period.
- Done when:
- New cases are classified, owned and escalated by your own team without prompting.
- 7
Review causes monthly, then hand over
Each month we produce the review pack, chair the review until your team can chair it, and carry the cause actions forward. When the rhythm holds without us, we hand over every template, rule and report, and agree who owns the process from then on.
- You provide:
- One hour a month from the people who can act on the causes, and a named internal owner for the process.
- We produce:
- A monthly review pack, an action log carried between reviews, and a complete handover file.
- Done when:
- Two consecutive monthly reviews are run by your team, with causes closed and actions carried.
Ways to work with us
You can start with a review of your complaints before changing anything.
Complaint handling review
A short engagement that reads your recent complaints, measures where they arrive and how long they take, and gives you a written view of the gaps. You receive the findings and a recommended severity scale, with no obligation to go further.
Design and build
We design the definitions, standards, escalation matrix and recovery limits, configure the register in your existing tool, write the templates and train your team. Delivered as a project, with a handover file at the end.
Run it with you for a settling period
After the build we stay alongside your team for an agreed period: sitting in on difficult cases, correcting classification, chairing the monthly review and adjusting anything that does not survive contact with a busy week.
Monthly complaint review only
For teams that already handle complaints reasonably well but never look at them together. We prepare the pack, chair the review, track causes to closure and report against the baseline each month.
One part of the business first
A narrow piece of work covering a single plant, branch, product line or large account, useful when you want to test the approach on real cases before applying it everywhere.
Why Gully Sales
What you are actually choosing when you choose us.
We design it around who actually answers your customers.
In most Indian SMBs a complaint reaches a service engineer, a dealer or the owner's phone long before it reaches a support desk. We build the process around those routes instead of pretending they do not exist, so the rules survive a normal week.
Sales, service and revenue are treated as one system.
Gully Sales works across marketing, sales, service and revenue operations, so we can follow a complaint back to the promise that caused it, whether that promise was made in a proposal, in an advertisement or in a delivery commitment.
We build inside the tools you already pay for.
The register goes into your existing helpdesk, CRM or shared sheet wherever it can. New software is a recommendation of last resort, and only when what you have genuinely cannot hold the process you need.
The process is written for handover, not for dependence.
Every rule, template and report is documented and taught to a named person inside your business. Our aim is that the monthly review keeps happening after the engagement ends, whether or not we are in the room.
We say plainly when the fault is not the process.
If your complaints are caused by the product, the delivery schedule or a commitment your sales team should not have made, a better escalation matrix will only route the same failure faster. We will tell you that before taking the work.
Where it applies
The same service, in different businesses.
Industrial equipment manufacturing
- The situation:
- Breakdown complaints reach the area sales manager, who calls a service engineer directly. Head office learns about a serious failure only when the customer withholds the next order.
- How it applies:
- Complaints are logged at intake by whoever receives them, severity is set by production downtime rather than tone, and any case involving a stoppage escalates to the service head the same day.
- Likely benefit:
- Leadership sees serious cases while they can still be influenced, and repeat faults reach the quality and design team with numbers attached.
Healthcare clinics and hospitals
- The situation:
- Patient complaints about waiting, billing or attitude are settled at the counter and rarely written down. The ones that were not settled well appear later as public reviews.
- How it applies:
- One register covers counter, phone and online complaints, severity separates clinical concerns from service concerns, and clinical cases escalate immediately to a named senior person.
- Likely benefit:
- Clinical risk is seen and acted on quickly, service causes are grouped monthly, and fewer complaints have to travel to a review site to get an answer.
Software and subscription businesses
- The situation:
- Support tickets are answered promptly, but a customer who is repeatedly dissatisfied looks the same in the system as one with a single question, until they cancel at renewal.
- How it applies:
- Repeat complaints from one account become a trigger in their own right, escalating to the account owner and the customer success lead well before the renewal conversation.
- Likely benefit:
- Accounts in trouble are identified while there is still time to repair the relationship, rather than in the cancellation email.
Building materials and hardware distribution
- The situation:
- Complaints about damage, shortage or delay arrive through dealers, who often absorb them and simply reduce their next order without saying why.
- How it applies:
- Dealers are given a defined intake route and a promised response time, and dealer complaints are classified and reported separately from end-customer ones.
- Likely benefit:
- You find out which dealers are quietly unhappy, and the causes behind their complaints reach the warehouse and transport teams every month.
Education and training institutions
- The situation:
- Parent and student complaints go to whichever staff member is nearest, and reach the principal or director only when someone has become very upset.
- How it applies:
- Categories separate academic, administrative and safety concerns, safety cases escalate immediately, and every case is closed with a recorded conversation rather than a verbal reassurance.
- Likely benefit:
- Serious matters are handled with the seriousness they need, and leadership stops absorbing routine cases that should have been settled at the desk.
Hospitality and facilities services
- The situation:
- A guest or client complaint is settled generously on the spot by whoever is on duty, and the value given away is never recorded or compared between shifts.
- How it applies:
- Each role is given a standing recovery authority with approved options and wording, and every gesture is recorded against the case and against its cause.
- Likely benefit:
- Guests still get a fast decision, and you can see for the first time what recovery costs each month and which cause is generating it.
Questions buyers ask
Before you enquire, the answers you will want.
Which situations require immediate escalation and executive visibility?
We usually set four automatic triggers: anything affecting safety, health or regulatory compliance; anything with legal or contractual exposure; anything already visible in public, such as a review or a social post; and any complaint from an account above an agreed revenue threshold. These skip the normal ladder and reach a named senior person on the same day. Everything else escalates on time elapsed and severity. You decide the thresholds, and we write them down so nobody has to judge in the moment.
How long does the engagement take?
The review takes two to three weeks, depending on how quickly we can read your existing records and speak to your frontline team. Design and build usually runs four to six weeks after that, including configuration, templates and training. Running the process alongside your team is a matter of months rather than weeks, because it only proves itself across a busy period. We agree the stages before starting and do not stretch the work to fill time.
What inputs are required from our side?
Access to your existing complaint records, in whatever form they take. An hour each with four to eight people who actually receive complaints. Two to three hours from you and your service or operations head for the working session where standards are agreed. Administrator access to the helpdesk, CRM or sheet where the register will live. After that, one hour a month for the review, and a named internal owner who will keep the process running.
How is success measured?
Against the baseline recorded before anything changed. The early measures are behavioural: how quickly customers hear back, how many cases breach the standard, how many escalate and how late. The middle measures are causal: whether repeat complaints from the same cause are falling, and whether cause actions actually close. Commercial measures come last, over your own reorder or renewal cycle, and we keep them separate rather than claiming credit for movements we cannot trace.
What is excluded from the scope of this work?
We do not staff your support desk or answer your customers for you. We do not build software, and we do not fix the underlying product, delivery or quality fault behind a complaint, though we will name it clearly and route it to whoever owns it. Legal advice, regulatory filings and consumer forum representation sit outside our scope. Wider service recovery campaigns and win-back programmes are a separate piece of work.
Is this different from setting up a helpdesk?
Yes. A helpdesk is where cases live; this is the set of rules about them. You can run a helpdesk for years without a definition of what counts as a complaint, a severity scale, a response standard or an escalation trigger, and many businesses do. We can work inside a helpdesk you already have, or alongside a shared sheet if that is genuinely all you need. Choosing and configuring the tool itself is a separate service.
Our complaints mostly come to the owner's WhatsApp. Can that be part of the process?
It usually has to be, at least at first. We do not try to switch that route off, because customers use it for a reason. Instead we give it an intake rule: the message is logged in the register within a stated time, given an owner who is not you, and answered through the normal path. Over time most customers move to the published route, because it answers them faster than waiting for your reply.
Will a formal process make our team slower with customers?
It should do the opposite. Most delay today comes from working out who owns a case and what may be offered to settle it. When both are written down, a frontline person can decide on the first call instead of promising to check and call back. The only added step is the record itself, which takes a minute when the register is designed around the fields your team can realistically fill.
4 more questions
How do you set response times without making promises we cannot keep?
We set them against your worst week, not your quietest one. In the working session we take the standards you would like, test them against real staffing, real travel time and a month with a festival week in it, then lower them until your service head is willing to be held to the number. A standard you meet consistently is worth far more to a customer than an ambitious one you miss.
Should we publish our complaint process and response times to customers?
Only once you have met them internally for a couple of months. Publishing a standard you cannot yet hold turns every miss into a second complaint. We usually run the process quietly first, prove the times, then decide what to publish and where. For businesses selling to large buyers or bidding for contracts, a written complaint and escalation procedure is often worth publishing early, because it is asked for.
Who should own complaints inside a small business?
One named person, and rarely the owner. In a business of fifteen to a hundred people it is usually the service or operations head; in larger ones a customer success or quality lead. That role does not have to handle every case, but it must own the register, chair the monthly review and have the standing to take a cause to another department. We help you place the role and write what it is accountable for.
What happens to the complaints already open when we start?
They come into the register as part of the build, which is often the first uncomfortable moment: a business that thought it had nine open cases finds thirty. We classify them, assign owners, and agree a plan for the oldest ones separately from the new process. Clearing that backlog honestly is usually the fastest visible improvement, and it gives your team confidence in the new rules.
Talk to us
Tell us about the last complaint that reached you personally.
Request a Customer Growth Assessment and we will look at how complaints reach you today, what happens to them and where they stall. It is a working conversation, not a pitch, and we will say plainly if your problem is the product rather than the process.
- No obligation and no sales script
- A reply from someone who does the work
- Your details are never sold or shared