Problems raised after the job is finished decide the relationship

4 days ago
3 min read

Updated: 2 days ago

Introduction

A call three weeks after completion saying something is not right is an unwelcome thing to receive. The work is done, the invoice is settled, the schedule has moved on, and the natural reaction is defensive. That reaction is where most of the damage occurs.

The customer has already decided that raising it is worth the awkwardness, which means it matters to them. How the next ten minutes go determines whether this becomes a story about a business that stands behind its work, or one that disappears when there is a problem. Both stories get repeated.

The evidence on this is consistent: a problem handled well produces stronger loyalty than no problem at all.

1. Problems raised after the job is finished deserve a fast response

The first rule.

Speed of acknowledgement matters more than speed of resolution. A reply the same day converts most of the anxiety into confidence. Delay confirms the fear that prompted the call. Acknowledge even when you have no answer yet.

2. Listen before assessing

The second rule.

Explaining why it is not your fault, before understanding the complaint, guarantees escalation. Let them finish. The facts can be established afterwards. Most people say the important part last.

3. Go and look

The investigation.

Assessing a problem remotely is unreliable and reads as reluctance. Attending in person resolves a substantial proportion immediately. It also signals that the matter is being taken seriously. Photographs are a poor substitute for both sides.

4. Separate the fault from the response

The framing.

Whether you caused it and how you respond are different questions, and the second matters more to the outcome. Deal with the response first. Attribution can follow. Customers judge the second question far more harshly.

5. Fix small things without arguing

The economics.

The cost of resolving a minor issue is almost always less than the cost of the dispute, the reputation and the lost repeat business. Draw the line generously. Save the argument for the genuinely large. Set the threshold in advance so nobody has to decide under pressure.

6. Say clearly what you will and will not do

The boundary.

Where something falls outside what you supplied, explain that plainly and offer whatever help is reasonable. Ambiguity produces repeated calls. A clear no is better received than a vague maybe. Say who could help if you cannot.

7. Confirm the resolution in writing

The closure.

A short note recording what was found and what was done prevents the matter reopening later. It also protects both sides. Two or three lines. Send it the same day it is resolved.

8. Look for the cause, not just the fix

The improvement.

Post-completion problems usually indicate something in the process rather than a one-off. Ask what allowed it. The same complaint arriving twice is a process fault. Record it so the pattern is visible.

9. Follow up afterwards

The recovery.

A message a week later confirming everything is now satisfactory completes the recovery and is rarely done. This is the point at which a resolved complaint becomes goodwill. It takes one message.

Be careful about resolving everything by discount. Money returned instead of a problem fixed leaves the customer with the original difficulty and a sense that you preferred to pay than to attend, which is not the impression a recovery is meant to leave.

Conclusion

Treat a problem raised after completion as an opportunity rather than an imposition.

Acknowledge it the same day, listen fully before assessing anything, go and look rather than judging remotely, deal with your response before the question of fault, resolve small things generously without argument, state plainly what falls outside your work while offering reasonable help, confirm the outcome in writing, look for the process cause behind the individual fault, and follow up a week later to confirm it is settled.