Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › Service and Support

Setting Remedies and Goodwill Limits for Front-Line Staff

How to give support staff a written remedy for each common failure, a goodwill allowance, approval levels and a fast escalation route, reviewed from cases.
Tutorialintermediate11 min readUpdated

Why staff need written remedies, not case-by-case permission

The service recovery and complaints guide explains in its section on empowerment, escalation and limits why a recovery only works if the person handling the complaint can act. It names three things staff need: defined remedies for common failures, written down so every agent offers the same; discretion within a limit for goodwill; and a fast escalation route for anything beyond it. It also says amends should be proportionate, because over-compensating teaches customers that complaining pays and under-compensating reads as indifference. This tutorial turns those principles into two working documents: a remedy table and an authority matrix. The remedy table answers what is offered for each failure; the authority matrix answers who may offer how much.

Case-by-case permission fails in predictable ways. The customer waits while the agent asks. The manager who approves does so inconsistently, depending on how busy they are. Agents who are refused once stop asking and offer nothing. And the business has no record of what it gave, to whom, or why, so it cannot tell whether its remedies are too mean or too generous. Complaints that escalate while the customer waits for an approval are one of the causes worked through in the diagnosis for customer complaints increasing.

The remedy table sits beside the complaints procedure rather than inside it. The tutorial on writing a complaints procedure sets out how complaints are logged, answered and escalated; the remedy table says what the agent can offer at each point. Neither repeats the recovery sequence: the apology, the fix and the follow-up still come first, and a generous remedy does not replace them. Keeping the table and the procedure as two documents also means the complaints procedure can stay short and stable while remedies are adjusted each quarter.

Before you start

  • Have a complaint log. You need a record of complaints with their reasons and outcomes, ideally a quarter or more. If complaints are not yet logged in one place, write the complaints procedure first. If contacts are not tagged by reason, the tutorial on tagging support contacts by reason builds the list.
  • Collect what was given. Pull refunds, replacements, credits and other gestures from the last quarter, with the failure each one answered and who approved it.
  • Know your margins. You need the Contribution Margin on the products or services complaints concern, and a view of what customers are worth over time. For service businesses, the guide to unit economics for service businesses explains how to read margin per job from the business's own records.
  • Identify who can approve what today. Even informal habits count: who signs off refunds, who can waive a fee.
  • Find someone to check the rights side. Customers' entitlements depend on the business's sector and country. Arrange for someone qualified to review the rights column of the table before it is used.

The steps

  1. List the failures from your complaint log

    Group the complaints by what went wrong from the customer's side: late delivery, damaged on arrival, wrong item, a missed appointment, a service that did not work, a billing error. Use the failure, not the cause, because the agent offering a remedy sees the failure; the cause goes to the monthly review. Rank the failures by how often they occur in your log. The most frequent ones get standard remedies first. Rare or unusual failures go to the escalation route rather than into the table. A single failure that reaches many customers at once, such as an outage or a cancelled date, is decided for the whole group by one named owner, as the guide to deciding a remedy when one failure affects many customers explains.

  2. Separate rights from goodwill

    For each failure, split the remedy into two parts. The first is what puts the failure right and may be something the customer is entitled to. The recovery guide states from the Competition and Markets Authority's guidance for businesses, as general direction, that customers are entitled to goods and services that match what was promised, that remedies such as repair, replacement or refund apply when they do not, and that a business must not mislead customers about those rights. The second part is goodwill on top: a credit, a refunded charge or a gesture that recognises the trouble caused. Keep them in separate columns, so staff never present an entitlement as a favour or withhold it as a bargaining chip. Have the rights column checked by someone qualified for your sector and country; this page states no periods or conditions.

  3. Set the standard remedy for each failure

    Write what the agent offers by default for each failure: the fix, any goodwill, and how it is delivered. Be specific enough that two agents would offer the same thing: "replace with priority delivery and refund the delivery charge" is a remedy, "make it right" is not. Where customers reasonably want different outcomes, list the options the agent can offer, such as a replacement or a refund. For failures where a delivery promise broke, align the remedy with what the delivery promises guide tells customers about their options; for returns, keep the remedy consistent with the returns policy and returns experience guide, which offers its policy on top of customers' rights.

  4. Cost each remedy against the customer's value

    Work out what each standard remedy costs the business, from your own margins rather than list prices, and set it against what keeping the customer is worth. A customer with a high LTV who leaves after a poorly handled failure costs far more than the remedy would have. The point is not to price every customer separately at the moment of the complaint; it is to check that the standard remedies are sensible across the customers who usually experience each failure. Where a remedy costs more than the margin it protects for most customers, look again at the remedy or, more often, at the failure.

  5. Set a goodwill allowance agents can use without asking

    Give agents an allowance for goodwill they can use at their own discretion, without approval, when the standard remedy does not quite fit the situation: a customer who has been let down twice, a failure that cost them a day off work, an occasion that was spoiled. One-way and two-way door thinking sets the boundary. Gestures that are small and easy to correct if they turn out to be wrong are two-way doors and belong with the agent. Remedies that are large, set a precedent or cannot be taken back are one-way doors and go up. The size of the allowance comes from your margins and your log, not from another business's figure.

  6. Set approval levels for anything larger

    Above the allowance, name who can approve what: a team lead up to one level, a manager above it, the owner or a director for anything exceptional. Keep the levels few. List the cases that go to a senior level regardless of amount, such as safety issues, legal threats, customers in vulnerable circumstances and repeat failures, which the recovery guide also names. Where an AI assistant or AI-drafted reply promised something, the guide to handling an AI mistake that reached customers involves whoever owns commercial and legal decisions, and the AI in customer service guide keeps refunds and exceptions with people rather than assistants.

  7. Write the escalation route and its response time

    For each approval level, write how the agent reaches the approver, what they send with the request (the case, the customer's history, what they propose and why) and how quickly the approver promises to answer. Set that promise from what the approver can keep, and tell the customer when they will hear. An approval route that takes days defeats the purpose of the table, because the customer still waits. Name cover for absences, so the route does not close when one person is away. A business with several sites keeps one table, one allowance and one set of approval levels for all of them, as the guide to running customer service across several sites explains.

  8. Record every remedy given

    Every remedy, standard, discretionary or approved, is recorded against the complaint: what was offered, what was accepted, its cost, who decided and whether it came from the table, the allowance or an approval. The complaint log from the procedure is the natural home. The record lets the business check consistency, spot customers receiving repeated goodwill and see which failures cost most. Treat the share of complaints resolved without escalation as a KPI only alongside how satisfied complainants are afterwards, as the recovery guide suggests, so speed is never bought by giving too much or too little.

  9. Review the table from the cases that did not fit

    Each quarter, read the remedy records with the agents and approvers. Look for failures where most cases were escalated and approved anyway, which means the allowance or the standard remedy is too low; failures where agents rarely use the standard remedy, which means it does not fit; and gestures that went repeatedly to the same customers. Read the cases agents flagged as awkward. Change the table, record why, and tell the team. Send the costliest failures to the people who can remove their causes, because the cheapest remedy is the failure that stops happening.

The remedy table: an example layout

FailureRights side (check with an adviser)Standard remedyGoodwill the agent can addAbove the allowanceOwner of the cause
Late deliveryWhatever applies where the order did not arrive as promisedNew date, with the option to cancelRefund of the delivery chargeTeam leadDelivery operations
Damaged on arrivalRepair, replacement or refund where goods do not match what was promisedReplacement collected and delivered, or refundSmall credit for the troubleTeam leadPacking and carrier
Wrong item sentAs aboveCorrect item sent, wrong item collected at no costCredit or priority deliveryTeam leadWarehouse
Missed appointmentWhatever applies to a service not provided as agreedRebooked at the customer's preferred timeCharge waived or creditManagerScheduling
Billing errorAs advisedCorrected bill and explanationCredit if the customer was charged twiceManagerFinance
Anything involving safety, legal threats or vulnerabilityAs advisedEscalateNone without approvalSenior levelNamed senior owner

The rights column is deliberately general: what the customer is entitled to depends on the sector, the country and how the sale was made, and only someone qualified can fill it in for your business. The other columns are the business's own decisions.

A sofa retailer writes its remedy table (illustrative)

Illustrative example — not a real result

Quexibar Sofas writes a remedy table and adjusts it after a quarter

Quexibar Sofas, an invented online sofa retailer, reads 3 months of its complaint log: 212 complaints, of which 74 concern late delivery, 51 damage on arrival and 29 the wrong fabric being made up. Until now every refund or credit needed the customer service manager's approval, and the average case waited 2 working days for it.

The team writes a standard remedy for each of the 3 failures. Late delivery: a new date, the option to cancel for a full refund, and the delivery charge refunded. Damage on arrival: a replacement part or sofa, or a refund, with the damaged item collected. Wrong fabric: the right fabric made and delivered, and the wrong sofa collected. The rights side of each is checked with the retailer's legal adviser. Agents get a goodwill allowance of £40 per complaint they can give without asking; a team lead can approve up to £150; anything larger, and any wrong-fabric case where the customer has a deadline, goes to the manager, who promises an answer the same working day.

After a quarter, the records show 38 escalations for damage on arrival, of which 35 were approved: most asked for a little more than £40 because the customer had taken time off work for the delivery. The team raises the allowance for damage on arrival to £75, leaves the others unchanged, and sends the damage records to the warehouse with photos.

Verify it worked

  • Take your most frequent failures. Check each has a row with a rights column, a standard remedy and a goodwill column, all filled in.
  • Give two agents the same failure without help. They should offer the same remedy.
  • Find the cost of each standard remedy. It should come from your own margins, not list prices.
  • Check the allowance, the approval levels, the approver's response promise and the cover for absences are written in one place.
  • Open recent remedy records. Each should show what was offered, its cost, who decided and whether it came from the table, the allowance or an approval.

If it goes wrong

  • Agents still ask before every gesture. The allowance is unclear, or agents are criticised for using it. Restate it and remove the criticism.
  • Two agents offer different remedies for one failure. The remedy is too vague. Rewrite it as the fix, the goodwill and how it is delivered.
  • Customers still wait for approval. The route is slow, or nobody covers an absence. Check the approver's response promise and name cover.
  • Most escalations for one failure are approved anyway. The allowance or standard remedy is too low. Raise it for that failure and record why.
  • Staff present a refund as a favour. Rights and goodwill share a column. Split them and have someone qualified check the rights column.

Next steps

Common mistakes

  • Presenting rights as goodwill. A refund the customer is entitled to is not a favour, and describing it as one can mislead them about their rights.
  • Remedies too vague to apply. "Use your judgement" produces as many remedies as there are agents.
  • An allowance nobody dares to use. If agents are criticised for using it, the allowance does not exist.
  • Approval routes slower than the customer's patience. A table with a two-day approval step still makes customers wait.
  • Copying another business's amounts. Remedies and limits come from your own margins and customers.
  • Not recording what was given. Without records the table cannot be reviewed, and repeat claims go unnoticed.
  • Remedy instead of recovery. Money does not replace the acknowledgement, apology and follow-up the recovery sequence sets out; the service and support hub places remedies within that wider work.
  • Paying for the same failure forever. Remedy costs are a reason to fix the cause, not a budget line to accept.

Frequently asked questions

What is the difference between a remedy and a goodwill gesture?

In this tutorial a remedy is what puts the failure right, and part of it may be something the customer is entitled to rather than something the business chooses to give, such as a repair, replacement or refund when goods or services do not match what was promised. A goodwill gesture is extra: a credit, a refunded delivery charge or a small gift that recognises the customer's trouble. Keeping the two apart stops staff presenting a customer's rights as a favour.

How large should a goodwill allowance be?

There is no general answer. Set it from your own margins and the value of the customers involved, large enough that agents can resolve most common failures without asking, and small enough that a mistake costs little. Then review it from the cases: if most escalations for one failure are approved anyway, the allowance for that failure is too low.

Will customers learn that complaining pays if staff can give goodwill freely?

Written remedies reduce that risk rather than increase it, because every customer with the same failure is offered the same thing. The risk comes from undefined discretion, where the most persistent customers get the most. Recording every remedy given lets the business see whether goodwill is going to repeated claims from the same customers.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Competition and Markets Authority — GOV.UK

Related