Why a remedy for many is a different decision from a remedy for one
The remedies and goodwill tutorial is built for a failure that reaches agents one customer at a time: a remedy table for the common failures, an allowance agents may spend on their own judgement, levels of sign-off beyond that, and a record of every remedy given. A remedy tableThe written list of standard remedies for common failures, keeping rights apart from goodwill, with an allowance staff use unasked and approval levels above. settles each case as it arrives, and that is the assumption a failure across a whole group breaks. The guide to proactive service messages tells an affected group about a disruption before they ask, keeps that notice free of offers, and treats any gesture to acknowledge the trouble caused as a remedy for the affected customers, to be decided and explained as one. Between them, the two pages set up the group decision. Neither makes it.
A remedy for many differs from a remedy for one in five ways. The cost multiplies: a gesture that is small for one customer becomes a sum across the group that no agent allowance was meant to cover. The decision can be visible: affected customers can compare notes with each other and in public, so differences between what each was given can be seen. It sets a precedent, because whatever the business gives this time is what customers will look for next time. It arrives under pressure, while the failure is still running and agents are already being asked. And it reaches customers who would never have complained, which a remedy decided case by case does not.
That makes the group remedy a decision for one named person, not the sum of what each agent happened to give. The incident management playbook, written for marketing errors, leaves the decision on what customers who acted on an error receive with a commercial owner, and gives the customer service lead the facts before customers start asking. The same split serves a service failure: whoever runs the incident fixes it, a named owner decides the remedy, and support hears first. Public statements and press questions are a separate job that this guide does not cover.
| Question | Where the answer comes from | Who decides |
|---|---|---|
| What are affected customers owed? | A qualified adviser for the sector and country | The remedy owner, on that advice |
| Is goodwill due on top, and how much in total? | The failure's cost to customers, margins and customer value | The remedy owner, at the senior approval level |
| Who was affected, and who qualifies for what? | The records that hold the commitment, checked against another source where possible | The remedy owner, with a written rule for edge cases |
| Automatic or on request? | Whether the records show who lost what, and whether customers must choose | The remedy owner, with the operations lead |
| What happens to earlier gestures? | The remedy record for the failure so far | The remedy owner, applied by the support lead |
| What does the message say? | The decision, in plain words | The owner of service messages |
| What was decided and why? | Everything above | Recorded by the remedy owner, read again on a set date |
Rights first, then goodwill
The remedies tutorial splits every remedy into two parts and keeps them in separate columns: what puts the failure right, which the customer may have a right to, and goodwill on top. A group remedy needs the same split, decided in that order. The recovery and complaints guide states, as general direction drawn from what the Competition and Markets Authority publishes for businesses, that customers are owed goods and services that live up to what they were promised; that where these fall short, remedies such as a repair, a replacement or a refund apply; and that a business may not mislead customers about what they are entitled to. It also notes that regulated sectors have complaint rules of their own.
So the first question after a failure is what each affected customer is owed, and the answer comes from someone qualified to advise for the business's sector and country and the way the sale took place. This guide states no refund periods, no compensation schemes, nothing about travel or passenger rules and nothing about insurance, tax or accounting. What it does say is that the owed part is not the business's to bargain with. Presenting an entitlement as a favour, such as calling a refund that is owed "a gesture of goodwill", can mislead customers about their rights, and the remedies tutorial lists it among its mistakes.
Only then comes the question of goodwill: is anything due beyond what customers are owed? The recovery guide asks for amends that are proportionate, since generous amends for a minor failure teach customers that complaining pays and thin amends for a serious one, above all one that cost customers time or money, read as indifference. Ask what the failure cost customers beyond the price they paid: a wasted journey, a day taken off work, an occasion spoiled, something else they had arranged around the promise. Where the owed remedy covers the whole loss, goodwill may be small or none, and a sincere apology may matter more. Where the failure cost customers far more than the price, the owed remedy alone can look like the business doing the minimum. Either way, a remedy is one part of the recovery sequence the recovery guide sets out, and it does not replace the acknowledgement, the apology, the fix or the follow-up.
Who is affected and who qualifies
The proactive messages guide starts from the system that holds the commitment, such as orders for a delivery problem, bookings for appointments and trips, or account records for a service, and draws the group's edges from the facts of what went wrong. It checks the list against a second source where it can and keeps it. That list is also the base for the remedy, so build it once and use it for the message, the remedy and the measurement.
Then write who qualifies for what, in terms the records can check. Some customers lost the whole service and some lost part of it. Some found a workaround and some could not. Some bought after the failure was announced, knowing about it. Some had already cancelled. Each distinction can justify a different remedy, provided it rests on a fact in the records rather than on how loudly a customer complains. Keep the tiers few, because every extra tier is another rule for agents to apply and another difference for customers to compare.
Some customers will say they were affected and will not be on the list. Give them a route to ask, and check their case against the business's own records rather than asking them to prove what the business already holds. Name one person who decides the cases the rule does not fit, and record each decision so the rule can be corrected if the same case keeps arriving.
Customers in difficult circumstances need a person. The guide to supporting customers in vulnerable circumstances names people agents can pass a case to and lets agents adapt the usual process inside limits agreed in advance. A standard group remedy may not fit: an extension is worth nothing to someone who cannot come back, and a credit is worth little to someone whose circumstances have changed. Let those cases go to the named people, with the authority to offer a different form of remedy.
Choosing the remedy and what it costs
The form of the remedy follows the loss. A service that was not delivered points to a refund, a rebooking or time added back. A product that failed points to a repair, a replacement or a refund. Wasted time or travel points to goodwill such as a credit or a refunded charge. A remedy that matches the loss reads as fair; one that does not, such as a discount on a future purchase for customers who lost something they had already paid for, can read as the business using the failure to sell.
Then cost it across the group. The remedies tutorial costs each remedy from the business's own margins rather than list prices and weighs it against the value of keeping the customer, their LTVTotal value a customer brings over time.. For a group, multiply each tier's remedy by the number of customers in it, from the business's own records, and set the total against two things: what the affected customers are worth to the business over time, and what an unclear or mean remedy would cost in contacts, complaints and disputes. The point is not to price each customer separately. It is to check that the remedy is sensible across the whole group before it is announced.
A remedy paid in credit or points is a debt. The loyalty programmes guide treats rewards issued but not yet redeemed as a liability the business owes its members, and notes that consumer protection law, as it describes it, expects terms to be fair and transparent, which covers how rewards and their expiry are described. A credit given as a remedy is the same kind of obligation. Write its terms before it is issued, including what it can be used for and whether it expires, state them in the message, and make sure whoever looks after the business's finances knows the total.
A group remedy is above any agent's allowance, and the remedies tutorial sends anything large or precedent-setting to a senior level. Thinking in one-way and two-way doors gives the reason to take care: the framework sorts decisions by how easily and cheaply they could be undone, and a remedy announced to everyone is hard to take back without causing a second failure. Adding to a remedy later is easier than cutting it. The framework earns its keep when it turns one large commitment into smaller steps that can be reversed, so commit at once to what customers are owed, keep the goodwill simple enough to extend if the failure runs on, and decide the final shape when the extent of the failure is known.
Automatic or on request
The customer effort guide asks whether a step the customer has to take could be done for them instead: finding the order itself instead of asking the customer for its number, or arranging a collection instead of sending instructions. Applied to a remedy, the question is whether customers should have to claim at all. If the business holds the list of affected customers and the means to pay them, applying the remedy automatically removes the claim entirely and reaches every affected customer, including the ones who would never have asked.
A remedy given only on request reaches only the customers who ask. The persistent end up with more than the patient, contacts rise at the moment the team can least absorb them, and the remedy becomes inconsistent in exactly the way a group decision was meant to prevent. Asking makes sense in two cases: where the customer has to choose between options, such as a refund or a rebooking, and where the records cannot show what each customer lost. In both, make the request one short step, say what happens if the customer does nothing, and set a date after which that default applies.
Slow or unclear remedies have a cost that arrives later. A customer who hears nothing, or who is told to fill in a claim, may dispute the payment with their card issuer instead of waiting: a ChargebackA sale reversed by the customer's card issuer, which can arrive after other checks have closed and should not stay in payment or attribution figures.. The site's entry on the term reads a cluster of chargebacks following an offer, a trial or a subscription that is hard to cancel as a sign of a misunderstanding, pointing at the promise and not only at the payment. Read the same way, disputes arriving from customers on the affected list suggest that the remedy was not clear or not fast enough.
Customers who already complained, and customers who will
By the time the group decision is made, some customers have complained and some agents have already given something within their allowance. Three rules keep that fair. Do not take back anything already given, because withdrawing a promise in the middle of a failure is a second failure. Bring every earlier complainant onto the same terms as everyone else, so nobody who complained early ends up with less. And decide whether each earlier gesture answered the same loss as the group remedy or a different one: where it answered the same loss, the customer keeps it and it counts towards any goodwill in the group terms, never towards what they are owed; where it answered a different loss, such as a customer who travelled to a closed site before any notice went out, it stands on top. Tell those customers how the two fit together before the general message reaches them.
Customers will keep getting in touch after the decision, and agents need the same facts as the message. Add a saved reply for the failure to the library of saved replies, owned and dated for review, covering what happened, who qualifies, what each tier receives and when, what agents may add from their own allowance and where the cases the rule does not fit should go.
A group remedy does not replace the complaints process. A customer who is still unhappy can complain and escalate under the complaints procedure, and the complaint is logged like any other, so the failure's full cost shows in one place.
Count what the failure produces. Agents tag each contact about it under a reason in the customer's own words, such as a question about the refund, and add the failure itself as the cause in the separate field the contact reason tutorial keeps for causes an agent already knows, so contacts about the failure and its remedy can be counted apart from everything else. Watch repeat contactsA customer contacting the business again about the same problem, the clearest sign that the first answer did not end the customer's work. on that reason in particular: customers coming back about the same remedy show that the message, the remedy or the way it was paid did not work.
Explaining the remedy in the service message
The remedy is explained in a service message, and it stays one. The comparison of promotional and transactional email sums up the UK regulator's direct marketing guidance as drawing a line between messages customers need and marketing, settled by what a message contains and the reason it is sent. The proactive messages guide applies that to disruption: the notice carries no offers, and any recognition of the trouble caused is a remedy, explained as such. A message about a remedy is a Transactional EmailAn email triggered by a person's own action or account, such as a receipt, password reset or shipping notice, rather than a marketing send. in that sense, sent because something happened to the customer's order, booking or account.
The message says what happened in one plain sentence and apologises for it. It says exactly what this customer receives, in terms of their own order or booking rather than the group's, whether they need to do anything, when the remedy will arrive and how to reach a person. It gives the terms of any credit. It does not describe an entitlement as goodwill, and it carries no codes for new purchases, no invitation to come back and spend and no newsletter sign-up.
Timing follows the decision. If the remedy is not settled when the first notice goes out, say that a remedy is being decided and when customers will hear, rather than promising one before the rights advice is in. Put the same facts on the help page and in the saved reply on the same day, so a customer who calls hears what the message said.
Recording the decision so the next failure starts from it
The reasons behind a remedy decided under pressure fade, and the next failure then starts from a blank page. A Decision LogA running record, one row per decision, of what changed and why, what was expected, who decided and when the result will be checked. keeps it. The decision log template gives each decision a row holding the evidence behind it, the effect expected and when that effect is to be checked, with what actually happened filled in at the check. For a group remedy, record the failure and its dates, how the affected customers were found, the advice on what they were owed and who gave it, each tier and its remedy, the total cost, why goodwill was or was not given, who decided, what the business expects to see, such as contacts about the failure falling away and no disputes arriving from the affected list, and the date to check.
Then make the decision reusable. Add a row for this kind of failure to the remedy table, with the reasoning, so the next owner starts from it. Send the cause to whoever can remove it, because a remedy that has to be paid again for the same failure is a reason to fix the failure.
Record the reasons as carefully as the remedy. The expectation-disconfirmation model holds that customers judge an experience by comparing it with what they expected, and part of what customers expect from a failure is what the business did last time. A generous remedy now becomes the expectation the next failure is judged against, and a remedy that differed between customers teaches them that the outcome depends on how hard they push. Writing down why this remedy was chosen lets the next owner give the same answer for the same reasons, or a different one knowingly.
An ice rink decides what to give after a week of closures (illustrative)
Yovashket Ice Rink decides one remedy for every skater the closure affected
Yovashket Ice Rink, an invented ice rink, closes for 6 days in February when its ice plant fails. The general manager takes the remedy decision away from the front desk on the second day. By then 41 customers have complained in person or by email, and the desk has offered 29 of them a £10 voucher.
The manager asks the rink's adviser to confirm what booked customers and season pass holders are owed, and on that advice the rink settles on refunds for every session and lesson it could not provide. The booking system lists 1,180 booked public session places, 214 lesson bookings and 362 season pass holders in the 6 days; a check against the till records adds 23 bookings made by phone.
The rink refunds every booked session and lesson automatically to the card used, with no claim needed. The adviser confirms that pass holders are owed nothing for the lost days under their terms, so season passes are extended by the 6 days lost as goodwill, also automatically. The 41 earlier complainants get the same terms as everyone else. For the 17 of them who had travelled to the rink before the first closure notice went out, the voucher stands on top, because it answered a wasted journey; the other 12 voucher holders keep theirs too, and their refunds are paid in full because they are owed.
The closure update on day 3 explains the remedy in 4 sentences with an apology, says refunds will arrive within 5 working days, and carries no offer. The front desk gets a saved reply with the same facts, and the decision goes into the rink's log with a check date 4 weeks later: total cost £14,600, expected contacts on the closure to fall within a week, and no disputes expected from the affected list.
At the check, contacts carrying the closure as their cause fell from 96 in the first week to 7 in the second, 3 customers came back about a refund that had gone to an expired card, and none of the refunds turned into a chargeback.
Common mistakes
- Deciding case by case for a whole group. Each agent gives something different, and customers who compare notes see it.
- Calling an entitlement goodwill. Labelling an owed refund as generosity can mislead customers about what they could have insisted on.
- Goodwill before the rights advice. A generous gesture announced first can turn out to be less than customers were owed.
- Qualifying by complaint volume. Remedies that follow who shouted loudest reward the persistent and teach the patient to shout next time.
- Making customers claim what the business could apply itself. Every claim form is effort for the customer and a contact for the team.
- Taking back what agents already gave. Withdrawing a promise during a failure creates a second one.
- An offer inside the remedy message. A code for a new purchase turns a service message into marketing and reads as selling off the back of a failure.
- Credit with unwritten terms. A remedy paid in credit is a debt, and terms decided later look like a way of shrinking it.
- No record of why. The next failure starts from a blank page, and customers judge it against a remedy nobody can explain.
The service and support hub places group remedies beside the complaints, recovery and proactive messages they depend on.
