The Customer Assumes You Broke Something New: Decision Tree

Why this matters

"It was working fine until you touched it." You will hear it, and sometimes it is even true. A customer who believes you broke something new is angry, and angry customers leave reviews and withhold payment. But you also cannot cave and eat a repair for damage you did not cause. This tree keeps you from two mistakes at once: bullying past a legitimate complaint, and accepting blame for a coincidence. The order is establish safety, establish causation, then have the conversation.

Safety first

If the "new" problem the customer is pointing at is itself a hazard - a gas smell, a burning smell, sparking or a hot outlet, water pouring near electrical, or no heat with a hard freeze coming - handle the hazard before you handle the accusation. Shut off the gas or water, de-energize and verify dead, get people clear, call the utility if it is a gas leak. Sort out whose fault it is later. Never let a blame argument delay making a dangerous condition safe.

Start here: hear it fully before you defend

Do not interrupt to defend yourself. Let the customer lay out exactly what they think broke and when. You need the facts, and they need to feel heard before they will accept any answer.

• Get specific: what is not working now, and what were they doing when they noticed.
• Establish the timeline: was it confirmed working before your visit, or just assumed working because nobody had used it.

If the thing they blame was never verified working before you arrived - a spare bathroom faucet, a rarely-run second zone, a pool feature used once a season - the "you broke it" is an assumption, not an observation. Diagnose it as a pre-existing unknown, gently.

If it was demonstrably working and is now down, you owe a real causation check. Go on.

Could your work plausibly have caused it

Be honest with yourself here. Trace the physical connection between what you did and what failed.

• Shared path. Is the new fault on the same circuit, line, drain, or airflow you were in? Power restored to a branch can reveal a weak device; a drain you cleared can push a clog downstream; adding load can trip a marginal breaker. These trace to your visit.
• Physical disturbance. Did you move, bump, flex, or lean on something near the failure? A brittle fitting cracked, a wire nicked, a corroded connection knocked loose often fails a day or two after being disturbed. This is on you even though it was fragile.
• Restored operation unmasking a hidden fault. Your repair made the system run normally for the first time in a while, and the next-weakest part gave up. Present all along, not caused by you, but genuinely triggered by your fix.

If any of these fit, treat it as connected to your visit and handle it fairly, even if the part was already weak.

If your work truly is unrelated

Different system, no shared path, nothing you disturbed, and no unmasking - it is a coincidence of timing, which happens constantly on aging equipment where everything is the same age.

• Prove it with a reading or a trace the customer can see, do not just assert it. "This is on a completely separate circuit from what I worked on, and here is why" beats "that is not my fault."
• Show them the isolation result if you have one: the part you serviced is holding, the failure is elsewhere.

Evidence, not confidence, is what defuses a blame accusation.

Have the conversation based on what you found

Match your words to the causation finding, and never before it.

• You caused it or unmasked it: own it plainly and make it right per your callback policy. "I disturbed this getting to the other repair, that is on us."
• It is genuinely unrelated: be kind but clear. "I understand why the timing looks bad. Here is the proof it is separate, and here is what fixing it would take." A calm demonstration keeps the relationship even when the customer has to pay.
• You are not sure yet: say so instead of guessing. "I do not want to blame anything until I have tested it. Give me a few minutes." Honesty mid-diagnosis beats a wrong confident answer you have to walk back.

Ordered recap

1. If the new problem is a hazard, make it safe first.
2. Hear the full complaint and pin the real timeline.
3. Check shared path, disturbance, and unmasking for a link to your work.
4. If linked or unmasked, own it fairly; if truly separate, prove it with a visible reading.
5. Have the conversation only after causation is settled, and admit uncertainty rather than guessing.

References

• Trade-standard practice for damage causation and callback handling
• See related: Separating a Failed Repair From an Unrelated New Problem; The Conversation That Keeps a Comeback From Losing the Customer
• See related: Deciding What a Callback Should and Shouldn't Cost the Customer