Recovering from a failed installation
- 7 days ago
- 3 min read
Updated: 11 hours ago
Introduction
An installation does not perform as expected, or something is found to be wrong after handover. The customer has spent a substantial sum, is frightened they have wasted it, and has already told three neighbours.
The technical fault may be minor and entirely fixable. What determines the outcome is what happens in the following week, because a customer in this position is deciding whether they are dealing with a business that will put it right or one that will avoid them. Almost everything that follows depends on that judgement. The technical repair is usually the easy half of the problem.
1. Recovering from a failed installation begins with responding immediately
Speed is the whole message.
Attending quickly, even before you know the cause, communicates that this is being taken seriously. A customer left waiting a fortnight escalates, complains publicly, and involves the certification body, and none of that is recoverable.
2. Take ownership before establishing fault
Sequence matters.
Whether the cause is a component, the design or another trade is a question for afterwards. Telling the customer immediately that you will resolve it, and then determining the cause, prevents a defensive conversation that produces nothing.
3. Do not blame the manufacturer in front of the customer
It reads as evasion.
The customer bought from you, and hearing about a supplier's failings sounds like preparation for refusing to help. Handle the manufacturer relationship separately and privately, and tell the customer what you are doing rather than whose fault it is.
4. Explain what happened in plain terms
Understanding reduces anxiety.
What went wrong, why, what it means for their system and what the fix involves. Customers imagine worse outcomes than the reality, and technical vagueness feeds that rather than reassuring anybody.
5. Give a specific plan with dates
Uncertainty is what drives escalation.
What happens next, on which day, and when it will be resolved. A dated plan that is kept converts the situation into a process, and a customer with a plan generally stops telephoning other people about it.
6. Put it right properly rather than minimally
The economics favour the thorough fix.
A partial repair that fails again produces a customer who is now certain the business cannot be trusted. In a market where neighbours talk, the cost of doing it properly is nearly always lower than the cost of doing it twice. The second visit also arrives with a customer who has lost patience entirely.
7. Consider what compensation is appropriate
Sometimes the fix is not enough.
Lost savings during the period, inconvenience, additional energy costs. A reasonable offer made without being demanded changes the story a customer tells, and it is usually cheaper than the alternative.
8. Follow up after it is resolved
Where the recovery is completed.
A call a few weeks later confirming everything is working turns a resolved complaint into a demonstration of reliability. Customers who have been through a problem handled well are frequently your strongest advocates.
9. Learn from it systematically
The internal half.
What caused it, whether the design, the installation or the component was responsible, and what changes. A failure that produces no change is one you will repeat, and the second occurrence is far harder to explain.
Deal with the online account of it directly. Where a customer has posted publicly, a calm factual reply describing what was done, without disputing their experience, is read by everybody considering you afterwards, and it frequently does more good than the original complaint did harm.
Conclusion
Recognise that the response, not the fault, determines the outcome.
Attend immediately even before the cause is known, take ownership before establishing fault, keep manufacturer disputes away from the customer, explain plainly what happened, provide a dated plan and keep to it, fix it thoroughly rather than minimally, consider compensation before it is demanded, follow up weeks later to confirm it is working, learn systematically so it does not recur, and answer any public account of it calmly and factually.
.png)



Comments