Note
Reactive Calls: When a Maintenance Site Reports a Fault
A maintenance agreement covers planned visits. Then a factory site calls to report that an inverter is showing an error code. That is a reactive call: unplanned, unscheduled, and almost certainly not described clearly enough in the agreement for either side to know immediately whether it is covered.
How you handle the next few hours determines whether the call costs you money, a client relationship, or both.
What Does the Maintenance Agreement Actually Say About Reactive Calls?
Most Thai industrial electrical maintenance agreements describe the number and type of planned visits per year. Fewer define what a reactive call is, who bears the cost, or what response time is committed. That gap is where disputes start.
Before you can handle reactive calls cleanly, the maintenance agreement needs answers to three questions:
- What is an emergency? Define it by symptom, not by the caller’s sense of urgency. A system that has stopped entirely is an emergency. A fault indicator that appeared two days ago is not. A two-criteria test clients can apply themselves reduces calls that arrive as emergencies but are not: the system is non-functional, and the fault appeared within the last 24 hours.
- What is covered? Is any reactive call included in the annual fee, or do callouts beyond the planned visits generate an additional charge? If included: how many per year? If billable: at what rate and under what conditions?
- What is the committed response time? A factory client expects fast response. A realistic commitment protects both sides. “Within 48 hours for a non-emergency, within 4 hours for a confirmed production-stopping fault” is more useful than a vague commitment to best efforts.
If your current agreements do not have these definitions, the next reactive call is a practical moment to add them. A short written addendum before the next scheduled visit closes the gap.
How Do You Decide Whether to Dispatch Now or Later?
When a reactive call comes in, the decision process follows four steps.
Triage the fault first. Ask for the visible symptom: error code, which circuit or zone, what stopped. A 60-second triage call tells you whether production is halted (dispatch now), equipment is degraded but running (dispatch within 24 hours), or nothing operational is affected (address at the next planned visit). Avoid diagnosing over the phone; get just enough to classify the urgency.
Check the site record. Who is the current authorized contact? Is the equipment still within the manufacturer’s warranty period, which might make this a warranty call to the supplier rather than a field visit? Are there open items from the last planned visit that could be related?
Decide coverage before dispatch. If the fault is likely outside the covered scope, say so before sending anyone. “We will attend and assess. If the fault is outside scope, we will confirm the cost before starting.” Getting that in writing prevents the dispute that happens when a technician completes work the client assumed was free.
Adjust the schedule. If the technician you dispatch was assigned to planned work the same day, that work needs to be rescheduled. Note what was moved, update the affected site, and record the reason.
Worked example: a contractor holds maintenance agreements for eight factory sites. On Thursday morning, a site in Samut Prakan calls to report that two zones of LED lighting in a production hall have gone dark. Fault affects lighting but not production, and appeared overnight. Classification: non-urgent, dispatch within 24 hours. The technician scheduled for a planned visit Friday morning at a different site handles the reactive call in the morning and the planned visit in the afternoon. Both sites are informed. The reactive call falls within scope and is logged as an additional visit under the site’s maintenance file.
What Does the Job Record for a Reactive Call Need to Capture?
A reactive call that is not documented creates three problems: you cannot show the client what was done, you cannot track how often a site is generating unplanned work, and you cannot invoice if the call turned out to be billable.
Every reactive call needs a job record that captures:
- The date and time of the call, and the name of the person who reported it
- The fault as described by the client on the call
- The triage decision and whether it was classified as covered or potentially billable
- The technician dispatched and the time of arrival at site
- The fault found on site, which may differ from what was reported
- The corrective action taken
- Any parts used or ordered
- Client sign-off on the day or written confirmation by reply to a same-day summary
A reactive call handled without a job record is invisible to your own reporting. When you sit down before the renewal to understand what a site actually cost you over the year, you need to know how many reactive calls it generated and what each one required.
How Do Reactive Calls Shape the Next Agreement?
Reactive calls are data about the site. A site that generates three reactive calls in a year is different from one that generates none. That difference should inform your pricing at renewal.
If the maintenance agreement includes a fixed number of reactive callouts per year, track how close each site is to that limit during the year. A site that exhausts its included callouts in July will either generate unbilled work in the second half, or create a billing dispute when you start charging for what the client assumed was still included.
Two sites that look similar on paper, same system type and similar capacity, can have very different reactive call rates depending on equipment age, how the factory runs the system, and how complete the original commissioning documentation was. Sites with gaps in their installation records tend to generate more reactive calls in the first year of a maintenance agreement because faults that should have been caught at commissioning surface instead during operation.
Before a renewal conversation, pull the reactive call log for each site covering the full agreement term. A site with a high call rate needs either a different price, a different scope that addresses the underlying cause, or a direct conversation with the client about what is driving the faults.
FAQ
Can we decline a reactive call the client says is covered?
Ask for clarification before dispatching. If the fault does not clearly fall within scope, say so before sending anyone. “Based on what you have described, this may fall outside the covered scope. We can attend and assess. If it does, we will confirm the cost before starting.” That phrasing is accurate without being confrontational. An outright refusal without investigation creates more friction than the original ambiguity.
What if the reactive call reveals a larger fault needing more than one visit?
Document on the day: what was found, what was done, and what is outstanding. If remaining work falls outside the maintenance agreement, describe it as an identified fault requiring separate quotation and send a written summary the same day. Most clients prefer a clear picture of what is outstanding over a return visit they did not authorize.
How do we track reactive calls across all our maintenance sites?
A site register that records visit type alongside each closed job gives you this view. At the end of each agreement year you can read the reactive call count per site against the planned visit record. If a site has generated more reactive calls than planned visits, that ratio is the starting point for the renewal conversation on price and scope.
Tracking reactive calls separately from planned maintenance means you know the true cost of each site before the next renewal, not after. The Field Operation System records both types of visit under each site’s maintenance record, so the full picture is available when you need it. If you want to see how it handles reactive and planned work across a portfolio, visit the program page or book a short call.