A customer you disappoint should not become a customer you lose.
When an order is late, a promise is missed or a job is done badly, most businesses improvise. Gully Sales gives you a defined way to acknowledge the failure, put it right, close the loop and stop it repeating.
- Every service failure gets an owner, a deadline and a written outcome.
- Your team knows what it may offer to put things right, and who approves it.
- The same failure stops arriving from a different customer each month.
Gully Sales Private Limited helps service, subscription and relationship-led businesses across India keep the customers they have already won.
In one paragraph
What is Service Recovery Programmes?
A service recovery programme decides what your business does in the hours after it has let a customer down, whether or not that customer complains. Gully Sales writes the recovery itself: who reaches them, how fast, what your frontline may put right without asking permission, what the customer hears afterwards, and what changes so the same failure does not return.
The problem
Something goes wrong, and every recovery is improvised from scratch.
Failures happen in every business. A delivery slips. A technician does not arrive. An invoice is wrong. A report is late. What separates the businesses that keep the customer from those that lose them is rarely the failure itself. It is what happens in the next few hours. In most Indian SMBs that response is improvised. A senior person hears about it, does something generous or does nothing, and nobody records what was decided. The next similar failure starts from zero again.
You will recognise it as
- When a customer is let down, your team waits for the owner to decide what to do.
- Two customers with the same problem get very different treatment, and both eventually find out.
- Discounts and free replacements are given to calm people, with nobody tracking what they cost.
- You hear about serious failures days late, usually from the customer rather than from your team.
- The same complaint keeps returning, because fixing the customer never became fixing the cause.
- Customers who quietly stop ordering are never asked what went wrong.
What it costs the business
- Customers who would have stayed after a decent recovery leave instead, and they tell others in the same trade why.
- Your senior people spend the week inside individual complaints instead of running the business.
- The cost of putting things right is invisible, so nobody can tell whether the goodwill was worth the money.
- Frontline staff stop raising problems early, because raising them creates trouble rather than support.
Why it persists. It persists because recovery feels like a judgement question rather than a process question. Owners believe each case is unique and needs their instinct. Teams are given neither the authority nor the budget to settle anything, so they escalate or they hide. And nothing is written down once the case closes, so the business never accumulates any knowledge about how it fails or what actually repairs a relationship.
If it stays unresolved. Churn stays unexplained. You keep replacing customers you did not have to lose, your team stays nervous about bad news, and the same avoidable failures keep reaching customers who have already forgiven you once.
What changes
What changes once recovery has a defined path.
In the first weeks
- Every failure is classified the day it is reported, not debated.
- The customer hears from a named person within an agreed time.
In how the work runs
- Your team knows what it can settle on its own and what must go up.
- Recovery gestures come from an agreed list, with approval levels attached.
- Serious cases reach leadership while they can still be repaired.
In sales and marketing
- Fewer accounts leave over incidents you could have recovered.
- Money spent on goodwill becomes visible, budgeted and reviewed.
In what management can see
- You can see each month how your business fails and how often it recovers.
Over the longer term
- Repeat failures reduce, because a case ends in a corrected cause and not only an apology.
- Staff raise problems early, because raising them is now the expected behaviour.
Gully Sales controls the design and the discipline: the classification, the standards, the escalation path, the remedy rules and the monthly review. Whether a particular customer chooses to stay depends on the severity, the relationship and how well your team follows through.
Who it is for
This suits businesses where one bad week can cost a whole account.
The businesses it suits
- Service businesses where delivery is a promise made in advance and kept later.
- Subscription and contract businesses where a bad quarter decides the renewal.
- Manufacturers and distributors whose customers feel every delay down the line.
- Healthcare, hospitality and education, where one poor experience is spoken about publicly.
- Businesses where the owner is still the escalation point for every serious complaint.
- Teams that already log complaints but have no agreed way to make amends.
What usually prompts the call
- A large customer has just left over something you believe was recoverable.
- An incident reached a public review or a WhatsApp group before it reached you.
- Your team asks the owner for permission on every refund, replacement or waiver.
- Support volumes are rising and the same categories keep coming back.
- A renewal conversation opened with a list of past failures nobody had closed.
What Gully Sales does
The work, component by component.
Failure and case classification
We list the ways your business actually lets customers down, from a late delivery to a wrong invoice to a rude interaction, and group them into severity bands. Each band carries a definition anyone in the team can apply without asking, along with worked examples taken from your own recent months.
- Why it matters:
- Without a shared definition of serious, everything is either an emergency or nothing, and the response depends on who happened to pick up the phone.
- You receive:
- A failure taxonomy with severity bands, definitions and worked examples from your own cases.
- Business value:
- Two people looking at the same incident reach the same conclusion about how urgent it is.
Ownership and case handling
We name who owns a recovery case at each severity, what they are accountable for, and what happens when they are on leave. Ownership stays with one person from acknowledgement to closure, even when the fix needs three departments to move.
- Why it matters:
- Cases stall between departments because everybody has touched them and nobody owns them.
- You receive:
- An ownership map, a handover rule and a case record format your team fills in every time.
- Business value:
- The customer always has one name to speak to, and you always know who is answerable.
Response and resolution standards
We agree how quickly a customer hears back, how quickly a fix is committed, and how often they are updated while it is being worked. Standards differ by severity and by channel, and are written for the people and hours you actually have rather than for an ideal support team.
- Why it matters:
- Most of the anger in a service failure comes from the silence afterwards, not from the original mistake.
- You receive:
- Written response, update and closure standards for each severity band and channel.
- Business value:
- Customers stop chasing you for news, and your team stops guessing what fast enough means.
Escalation paths and executive visibility
We define what must rise, how fast, and to whom, including the short list of situations a director should hear about the same day: safety, legal exposure, a public review, a strategic account, or a failure that has now happened twice to the same customer. The path names roles, not individuals.
- Why it matters:
- Leadership usually learns about the dangerous cases too late to influence how they end.
- You receive:
- An escalation matrix with triggers, timelines, named roles and a same-day alert list.
- Business value:
- Serious situations reach the people who can settle them while the relationship is still open.
Recovery gestures and remedies
We set out what your team may offer to put things right, whether that is a redo, a credit, an expedited replacement, a site visit or a waiver, with approval levels and limits attached to each. We also write the words: how to acknowledge, how to apologise plainly, and what nobody should promise.
- Why it matters:
- Staff either give away too much to end the conversation, or nothing at all because no one told them they were allowed to.
- You receive:
- A remedy menu with approval levels and limits, plus acknowledgement and apology scripts.
- Business value:
- Goodwill is spent deliberately and consistently instead of being negotiated case by case.
Root-cause learning and prevention
Every closed case ends with a cause, an owner for the correction and a date. We run a short monthly review of what failed, what it cost and what has been changed, so recovery stops being a treadmill. Repeat causes are pushed back into the process that produced them.
- Why it matters:
- A business that recovers well but never learns simply pays for the same failure again next quarter.
- You receive:
- A closure and root-cause format, a repeat-failure register and a monthly review agenda.
- Business value:
- The volume of avoidable failures falls, which is far cheaper than recovering each one well.
What you will have at the end.
- A failure taxonomy with severity bands, definitions and examples drawn from your own cases.
- An ownership map naming who runs a recovery case at each severity level.
- Written response, update and closure standards for each severity band and channel.
- An escalation matrix with triggers, timelines and a same-day leadership alert list.
- A remedy menu with approval levels and spending limits for each type of gesture.
- Acknowledgement, apology and closure templates for phone, email and WhatsApp.
- A case record format that captures cause, remedy, cost and outcome.
- A repeat-failure register and a monthly recovery review agenda.
- A one-page recovery playbook your frontline can keep beside them.
- A training session for the team who will run it, worked through your own past cases.
- A reporting definition listing what to measure and where each number comes from.
How it runs
The engagement, step by step.
- 1
Failure review
We read your recent complaints, escalations, credit notes and lost accounts, and sit with the people who handled them. The aim is to see how your business actually fails and what your team currently does about it, before anything is designed.
- You provide:
- Access to complaint records, credit notes, support messages and the staff who handled the cases.
- We produce:
- A findings note listing your real failure types, how often each occurs and how each was handled.
- Done when:
- You recognise your own business in the failure list.
- 2
Classification and standards design
We turn those findings into severity bands, ownership rules and response standards, sized to the team you have. Every rule is tested against a real past case: would this have produced a better result on that day, with those people?
- You provide:
- A working session with your service, sales and operations leads to agree severity and timings.
- We produce:
- A draft severity model, ownership map and response standard for your review.
- Done when:
- Your leads agree the definitions and can apply them to last month's cases.
- 3
Escalation and remedy authority
We agree what rises to whom and how fast, and what your team may offer without asking. Owners usually find this the hardest step, because it means giving up some control in exchange for speed.
- You provide:
- Decisions on limits, approval levels and which situations directors must hear about the same day.
- We produce:
- An escalation matrix and a remedy menu with limits, approvals and exclusions.
- Done when:
- A frontline person can settle a routine failure without calling the owner.
- 4
Playbook and scripts
We write the operating documents: the case record, the closure format, and the words your team uses to acknowledge, apologise, commit and close. Scripts are written in the language your customers are actually spoken to in.
- You provide:
- Tone guidance, product and warranty facts, and any legal wording you are required to include.
- We produce:
- The recovery playbook, the message templates and the case record format.
- Done when:
- The playbook answers a live case your team brings to it, without further explanation.
- 5
Rollout and live cases
We train the people who will run it, using your own past cases as practice. Then we work alongside your team on live cases for an agreed period, correcting the parts of the design that do not survive contact with real customers.
- You provide:
- Team time for training and a nominated internal owner for the programme.
- We produce:
- A training session, worked case practice and a corrected version of the playbook.
- Done when:
- Live cases are being handled through the playbook rather than around it.
- 6
Review and root-cause discipline
Each month we review what failed, what it cost, what was recovered and what has been permanently corrected. Repeat causes are pushed back to the process that created them, with an owner and a date against each.
- You provide:
- Attendance at the monthly review and decisions on the corrections it raises.
- We produce:
- A monthly recovery report, an updated repeat-failure register and an agreed fix list.
- Done when:
- A cause corrected in one month stops appearing in the next.
Ways to work with us
Four ways to bring this into your business.
Recovery diagnostic
A review of how your business handles failure today, using your own recent cases, ending in a findings note and a prioritised list of what to change first.
Programme design
The full design: classification, ownership, standards, escalation matrix, remedy menu, playbook and templates, handed over to your internal owner with training.
Design and run alongside your team
We design the programme, then work with your team through live cases for an agreed period, chairing the review until the routine runs without us in the room.
Monthly review retainer
Your team runs the programme. We chair the monthly review, maintain the repeat-failure register and keep the standards current as the business changes.
Why Gully Sales
What you are actually choosing when you choose us.
We design for the team you have.
Your standards are written against your actual headcount, shifts and channels. A programme that assumes a dedicated service desk will be abandoned in the first busy week, and then nobody trusts the next one.
We use your cases, not a template.
Every severity band, script and remedy is tested against failures your business has already had. Your team recognises the situations, which is why they use the rules instead of working around them.
We put a number against authority.
Most recovery programmes fail because nobody said what the frontline may spend or decide. We push you to set limits, and we write them where the team can see them.
We join service back to revenue.
Because we also work on sales and revenue operations, we design the handover between service and the account team, so a recovered failure is known about at the renewal instead of resurfacing there.
We stay until it survives a bad month.
Anyone can write a playbook. We work alongside your team through live cases and correct the parts that break under real pressure, before handing the routine over.
We say what recovery cannot fix.
If the failures come from a broken process upstream, we will point the work there instead of teaching your team to apologise more efficiently for the same thing every week.
Where it applies
The same service, in different businesses.
Industrial equipment and after-sales service
- The situation:
- Breakdowns at customer sites are attended late, and each delay is negotiated separately with an angry plant manager.
- How it applies:
- Severity bands tied to production impact, a same-day escalation rule for line-stopping faults, and standing authority for the service head to commit a replacement unit.
- Likely benefit:
- Customers get a predictable response during a breakdown, which is exactly when they decide whether to buy from you again.
Healthcare and clinics
- The situation:
- A complaint about waiting, billing or staff conduct reaches the administrator informally and is settled differently every time.
- How it applies:
- A classification separating clinical concerns from service concerns, a defined escalation to the medical lead, and a recorded closure conversation with the patient.
- Likely benefit:
- Concerns are handled consistently and documented, and fewer of them appear first as a public review.
Hospitality
- The situation:
- A guest has a poor stay, says nothing at the desk, and posts a detailed review two days after checking out.
- How it applies:
- In-stay checks that invite the problem early, a front-desk remedy list staff may use without calling a manager, and a follow-up before departure.
- Likely benefit:
- Problems are recovered while the guest is still on the property, when a gesture still means something.
IT services and software
- The situation:
- A missed deadline or an outage damages a renewal conversation months later, because nothing was ever formally closed with the client.
- How it applies:
- A case record that ends in a written closure to the client, a root-cause note attached to the account, and a standing item in the account review.
- Likely benefit:
- The account manager enters the renewal with a documented record of how each problem was handled.
Logistics and distribution
- The situation:
- Damaged or short deliveries are argued between the driver, the branch and the customer until somebody gives up.
- How it applies:
- One owner per claim, a fixed acknowledgement window, evidence rules for photographs and proof of delivery, and credit authority held at branch level.
- Likely benefit:
- Claims close in days instead of drifting, and repeat damage causes become visible by route and by handler.
Education and training institutions
- The situation:
- Parents and learners raise the same complaints each term, and the response depends on which coordinator hears it first.
- How it applies:
- One complaint classification shared across branches, a defined escalation to the head, and a termly review of the causes that repeat.
- Likely benefit:
- Families see a consistent response, and recurring problems get corrected between terms rather than repeated.
Questions buyers ask
Before you enquire, the answers you will want.
Which situations require immediate escalation and executive visibility?
We agree a same-day list with you, and it is deliberately short so that it stays credible. It normally covers anything involving safety, a legal or regulatory exposure, a public review or social media post, a strategic account, a failure that has now happened twice to the same customer, and any case where a customer has said they intend to leave. Everything else follows the normal matrix by severity band.
How long does the engagement take?
It depends on how many failure types, teams and channels you have, so we do not quote a schedule before we have looked at your cases. What we can describe is the sequence: a failure review, then classification and standards, then escalation and remedy authority, then the playbook and scripts, then rollout with live cases. After the assessment you get a staged plan showing the order of work and what each stage needs from you.
What inputs are required from our side?
Access to your recent complaints, escalations, credit notes and support messages, and time with the people who handled them. Then the decisions only you can make: spending limits, approval levels and the same-day escalation list. Finally, a nominated internal owner for the programme and team time for training. Without an internal owner, the playbook becomes a document instead of a routine, and nothing changes on the floor.
How is success measured?
Against the baseline we record before anything changes. The early measures are operational: time to first response, time to resolution, the share of cases closed to standard, and how many cases are logged at all. The later measures are commercial: churn and renewal rate among accounts that experienced a failure, expansion from recovered accounts, and the cost of goodwill spent. We report monthly with the baseline beside every number.
What is excluded from the scope of this work?
We do not run your support desk day to day, and we do not take responsibility for the underlying product or delivery fault itself. Building a helpdesk or contact centre, designing the wider customer journey and running your renewal motion are separate pieces of work. This programme covers what happens after a failure: classification, ownership, standards, escalation, remedies, closure and root-cause learning.
How is this different from complaint and escalation management?
Complaint and escalation management is about the path a complaint travels: intake, routing, ownership and how it moves upward. Service recovery starts where that path arrives. It covers repairing the relationship after the failure: what you offer, who may approve it, how you close the loop with the customer in writing, and how the cause is corrected so the same customer is not let down twice. Many businesses need both.
Will giving our frontline spending authority cost us more?
Usually it costs less, and for the first time it becomes visible. Today most goodwill is given late, by a senior person, under pressure, to end an argument that has already damaged the relationship. A written remedy menu sets what may be offered, at what level and up to what limit, and every gesture is recorded. You then see the total in the monthly review and can adjust the limits with evidence in front of you.
Our customers rarely complain. Do we still need this?
Silence is not satisfaction. Many unhappy customers say nothing at all. They quietly reduce their orders and go elsewhere, and you learn about it a quarter later. Part of this work is finding the failures nobody reported, through delivery data, repeat tickets, missed service dates and direct outreach to accounts whose ordering pattern has changed. A programme that only reacts to complaints works with a fraction of the picture.
4 more questions
Who inside our business should own the programme?
Someone close to the frontline with the standing to make decisions: a service head, an operations manager or a customer success lead. In a smaller business it is often the person who already receives most escalations. It should not be the owner, because the whole point of the design is to take the owner out of routine cases while keeping them informed about the serious ones on the same day.
Do we need a helpdesk or CRM system before we start?
No. The design comes first and the tool follows it. A workable programme can run on a shared inbox, a WhatsApp number and a simple case register. If you already use a helpdesk or CRM, we design the classification, ownership and closure fields so your team can configure them there. If you do not have one, we will tell you when your case volume justifies buying one, and what it must do.
How do we apologise without accepting legal liability?
We write acknowledgement and apology wording with you, and where your business carries contractual or regulatory exposure we recommend your legal advisor reviews it before use. The working principle is simple: acknowledge the customer's experience and say what you will do next, state only facts you have verified, and avoid speculating about cause before the investigation is finished. Your advisor has the final word on wording.
What if the same failure keeps coming from another department?
That is exactly what the root-cause register is for. Each closed case names a cause and an owner for the correction, and repeat causes are raised in the monthly review with leadership present. Recovery on its own becomes expensive when the cause is never corrected, so we push the fix back to the process that produced it, whether that is production, dispatch, billing or a sales promise made too freely.
Talk to us
Find out what happens in your business after something goes wrong.
Request a Customer Growth Assessment. It is a working conversation about your recent failures and how they were handled, not a sales presentation.
- No obligation and no sales script
- A reply from someone who does the work
- Your details are never sold or shared