A Customer Demands More Than What's Reasonable: Decision Tree

Why this matters

Somewhere in every recovery, a customer asks for more than the failure actually warrants. A full refund on a job that mostly went fine. A free year of service over a single missed appointment. A brand-new installation because one small part failed. Give in every time and you train your best and worst customers alike that escalation is the fastest path to a windfall. Refuse reflexively every time and you lose customers who had a legitimately oversized ask because of a real, unaddressed problem underneath it. The skill is telling the difference fast and responding to each differently, without getting defensive or caving out of discomfort.

Start here: is the demand attached to a real, unresolved problem

Before judging the size of the ask, check whether it is riding on top of a legitimate grievance that has not actually been fixed yet.

• If the underlying problem is still unresolved, the size of the demand is a symptom, not the disease. A customer asking for everything back because the unit still does not work right is not being unreasonable, they are asking you to finish the job you have not finished. Fix the actual problem first. The demand often shrinks or disappears once the real issue is solved.
• If the underlying problem has been genuinely fixed and the demand persists anyway, continue down the tree. This is now about calibrating an ask that has outgrown its cause.

Step 1: Separate what they are asking for from what they actually need

Listen for the real want underneath the stated demand. People often over-ask because they do not trust that a smaller offer will actually happen, not because they truly expect the maximum.

• If the demand is really about trust ("how do I know this won't happen again") a bigger comp does not solve it, a demonstration does. See related: The Make-Good That Costs Little But Means a Lot.
• If the demand is really about feeling disrespected ("nobody called me back for three days") the fix is acknowledgment and process change, not necessarily money.
• If the demand is genuinely about being made financially whole, it is a sizing question, move to Step 2.

Step 2: Compare the ask to the actual harm

Lay the demand next to the proportionality frame you would use for any recovery. Ask plainly, would this size of gesture be what you would offer proactively if the customer had not asked at all. If yes, the ask is reasonable even if it came forcefully. If the ask is clearly larger than the failure, that gap is the thing to name.

• If the ask roughly matches the harm, grant it. Do not haggle down a reasonable request just because it arrived as a demand rather than a polite ask. Tone should not change the math.
• If the ask is meaningfully larger than the harm, move to Step 3.

Step 3: Decide whether to hold, flex, or add value instead of cash

When a demand outsizes the failure, you have three honest paths, not just yes or no.

• Hold the line with a clear explanation. State plainly what you are offering and why, tied to what actually happened. "I understand the frustration, and here's what we're doing to make this right: [specific gesture]. That reflects what went wrong on our end." A calm, specific hold often lands better than either caving or arguing, because it shows you have actually thought it through rather than just refusing.
• Flex partway if there is a real gray area. If fault is genuinely mixed or ambiguous, a modest move toward the customer's ask, explained honestly as a goodwill step rather than an admission you owe the full amount, can close the gap without setting a precedent you regret.
• Add value instead of increasing cash or credit. A customer fixated on a number can sometimes be satisfied by a non-cash addition, priority scheduling, an extended check-in period, a small extra service, that costs you less and addresses the underlying want (being taken care of) better than simply inflating the comp.

Step 4: Watch for the repeat-demander pattern

If the same customer has escalated demands beyond what the facts support more than once, this stops being about a single recovery and becomes a customer-relationship decision. A pattern of manufactured or exaggerated grievances used to extract free work is different from a one-time frustrated overreach, and deserves a different response, including declining future work if it continues. See related: When a Customer Cannot Be Won Back and That's Okay.

Step 5: Know when to escalate rather than decide alone

Any demand large enough to feel uncomfortable making unilaterally, or any interaction where the customer threatens legal action, a public campaign, or repeated contact with no resolution in sight, is a signal to loop in whoever owns recovery decisions rather than negotiating it to conclusion yourself. See related: Escalating a Recovery to the Owner: When to Step In.

Quick recap

1. Fix any real, unresolved problem first, the oversized demand often shrinks once the actual issue is gone.
2. Listen for the real want (trust, respect, money) underneath the stated ask.
3. Compare the ask to the actual harm, honestly, before deciding.
4. If it is oversized, hold with a clear explanation, flex partway on genuine gray areas, or add non-cash value.
5. Watch for a repeat pattern, that is a relationship decision, not a recovery decision.
6. Escalate anything that feels too large, too threatening, or too ambiguous to decide alone.

References

• Trade-standard practice for proportional complaint resolution and customer-demand triage.
• See related: The Make-Good That Costs Little But Means a Lot
• See related: Escalating a Recovery to the Owner: When to Step In
• See related: When a Customer Cannot Be Won Back and That's Okay