Offer a Comp or Not: Decision Tree

Why this matters

The moment a complaint lands, someone has to decide whether the business owes the customer something beyond an apology, and if so, what and how much. Comp every complaint and you train customers that pushing back gets a freebie, while quietly eating margin on jobs that were actually done correctly. Refuse every complaint and you lose customers over genuine misses that a small gesture would have saved. Neither instinct is a policy. This tree walks the decision in order, so the answer comes from the facts of the case rather than from how loud the customer got or how the person answering the phone happens to feel that day.

Start here: was the work actually deficient

Before anything else, establish what actually happened, separate from how upset anyone is about it.

• If you have not yet verified the work, do that first. Pull the job record, talk to the tech, inspect if you can. Deciding a comp before you know the facts means you are pricing the customer's mood, not the problem.
• If the work meets the standard you sold and the complaint is about something else (a preference, a price they now regret agreeing to, a result they misunderstood going in), move to the "not a comp situation" branch below.
• If the work genuinely fell short, continue to the next question.

If the work fell short: how big is the gap

Size the actual failure before sizing the response. A minor miss and a total failure are not the same conversation.

• Minor: the core job holds but something small was off, a mess left behind, a slightly late arrival, a callback for an easy adjustment. This rarely needs a financial comp at all, an apology plus prompt correction is usually enough.
• Moderate: the fix did not hold, a callback was needed for something that should have been caught the first time, or the customer lost real time or convenience because of your error. This is where a proportional comp, a fee waiver, a priority redo, or a small credit toward future service, typically belongs.
• Severe: the job failed outright, caused damage, or created a real safety or property problem. This is where a fuller remedy, a substantial credit, a comparable-value redo, or in the worst cases a refund, is usually warranted. See related: The Difference Between a Refund, a Redo, and a Discount.

Match the size of the gesture to the size of the actual gap. A severe failure answered with a token gesture reads as cheap. A minor miss answered with a large comp overpays and sets a precedent you did not need to set.

Weigh whose error it was

Fault changes the floor of what is owed, though not always the ceiling of what is worth offering.

• Confirmed team error: the comp conversation starts from "we owe you something," and the question becomes proportional to the severity branch above.
• Genuinely outside your control (a part defect, a pre-existing condition, something the customer changed after you left): you may owe far less or nothing under the letter of what was agreed, but a goodwill gesture can still be worth offering for a long-standing or high-value customer, weighed against the relationship, not the fault.
• Fault is unclear or shared: a partial or middle-ground remedy usually fits better than an all-or-nothing answer. Do not let ambiguity push you to either extreme.

Factor in the relationship, without letting it override the facts

Two customers with an identical complaint can reasonably get different treatment if their history is genuinely different, as long as you can explain why out loud.

• A long-standing customer in good standing is worth more latitude, a slightly larger gesture, a faster turnaround, because the value of keeping them exceeds the cost of the comp.
• A brand-new customer or one-off job gets the same fair, proportional remedy, but does not automatically earn the extra generosity a decade of loyalty has bought someone else.
• A customer with a pattern of manufactured complaints changes the calculation entirely. See related: The Repeat Complainer Pattern Decision Tree, where the answer may be to stop comping the pattern rather than the incident.

If it is not actually a comp situation

Not every unhappy customer is owed something material, and saying so clearly, without being defensive, is a legitimate outcome.

• The work was correct and matches what was agreed, but the customer wanted a different outcome than what was promised. Explain the facts plainly and hold the line, while still treating the person with respect.
• The complaint is being used as leverage rather than reflecting a real problem. See related: The Bad-Review Threat Decision Tree for handling that specific pressure without paying a ransom for work that was done right.

What to avoid regardless of the branch

• Do not decide the comp before verifying the work. The verification changes the answer more often than people expect.
• Do not let volume or tone set the price. The loudest customer and the quietest one with the identical failure should get the identical remedy.
• Do not comp in a way that requires a specific dollar figure spoken on the spot before whoever owns pricing has weighed in, unless you are the one who owns that call. Commit to "we'll make this right" and follow up with specifics once you have actually sized it.
• Do not treat every comp as a template for the next one. Document the reasoning each time, severity, fault, relationship, so the next decision is consistent in logic even if the outcome looks different.

References

• Trade-standard practice for service-recovery and complaint resolution.
• Small Business Administration guidance on customer-complaint handling and goodwill remediation.
• See related: The Difference Between a Refund, a Redo, and a Discount; What to Document the Moment a Job Goes Sideways.