Breakdowns do not wait for office hours. A lift stops with someone inside at 11 pm. A cold room fails on a Sunday. A fire alarm panel shows a fault during a holiday. A hospital's generator does not start during a power cut. For many service companies, how they handle these moments defines their reputation — and, for contract customers, often their contractual obligations. Emergency and after-hours call management needs a clear system, not just a phone number someone hopes will be answered.
Define what an emergency is
Without a definition, every call becomes urgent. Agree with customers what qualifies, for example:
- Risk to people's safety — trapped passengers, gas leaks, electrical hazards, fire system failures.
- Complete loss of a critical service — power, cooling for medicines or food, water, security systems.
- Situations causing serious damage — leaks, flooding, equipment overheating.
- Major business loss — production stopped, a store unable to trade.
Write this into contracts and into the call-taking script. Calls that do not qualify are logged and scheduled for the next working day, with a clear explanation to the customer.
On-call rosters
Maintain a roster of on-call technicians and supervisors by area and skill, visible to everyone and updated when swaps happen. Distribute on-call duty fairly and compensate it clearly — fatigue and resentment from unfair rosters lead to slow responses and staff turnover. Each on-call technician should have a stocked vehicle, tools and access to key parts.
How calls come in
After-hours requests may arrive by phone, WhatsApp, a customer portal or automatic alarms from monitored equipment. Route them to one place: an on-call coordinator, an answering service following your script, or the system itself, which creates a job and notifies the on-call technician by app and phone call. Every call should be logged with time received, caller, site, equipment and description — even if it is resolved by phone.
Acknowledgement and escalation
A notification that nobody sees is the worst failure. The on-call technician must acknowledge the job within a set time. If they do not, the system escalates automatically to the backup technician, then to the supervisor. The customer should receive confirmation that someone is on the way, with an expected arrival time.
Response targets
Contracts often specify response times for emergencies — for example, attendance within two or four hours depending on location and contract level. Record the time of call, acknowledgement, departure, arrival and restoration, so performance against targets is measured automatically, not argued over later.
Remote diagnosis first
Some emergencies can be resolved or made safe by phone or remote access: guiding the customer to reset a breaker, switching to standby equipment, isolating a leak, or checking a remotely monitored system. A quick triage call by an experienced technician can avoid unnecessary night visits and make sure the right person with the right parts goes when a visit is needed.
Parts and access
Emergency repairs often fail because a part is locked in a closed warehouse. Keep critical spares in on-call vans or an accessible store, with stock recorded so the technician knows what is available. Record site access arrangements — keys, security contacts, permits — in the customer's site details, so the technician does not wait at the gate.
Technician safety
Night and weekend work often means working alone in plant rooms, basements, rooftops and empty buildings. Basic safeguards:
- Check-in on arrival and check-out on departure through the app.
- Automatic alerts if a technician has not checked out within an expected time.
- A simple way to raise an alarm.
- Rules for tasks that require two people or must wait until normal hours.
- Permits and isolation procedures followed, even under pressure.
Charges
Be clear in advance: call-out charges, after-hours labour rates, minimum charges, and what contract customers get included. The technician app can show whether a call is covered and record customer acknowledgement of charges before work starts. Invoicing emergency jobs promptly, with times and work details, avoids disputes.
Customer communication
In an emergency, silence feels like neglect. Confirm receipt, share the technician's name and expected arrival, update if delayed, and send a service report once the situation is resolved — including any follow-up work needed during normal hours. A short follow-up call the next working day shows care and often generates repair work.
Reviewing performance
- Emergency calls by customer, site and equipment.
- Response and restoration times against targets.
- Share of calls that were not genuine emergencies.
- Calls resolved remotely versus by visit.
- On-call workload per technician.
- Repeat emergencies on the same equipment.
Repeat emergencies are a signal: the equipment may need overhaul, or preventive maintenance may be missing something. Raising this with the customer turns emergency data into planned work.
Example
A refrigeration service company supporting supermarkets and pharmacies relied on a single on-call mobile number passed between technicians. Calls were missed when the phone was out of coverage, and response times were unknown. A roster in the service system, automatic job creation from calls and alarms, app notifications with escalation to a backup and a supervisor, and check-in and check-out times were introduced. Missed calls stopped, emergency response times became measurable and reportable to customers, and repeat alarms on certain cold rooms led to several planned refurbishment projects.
Summary
Handle emergencies with a system: define what qualifies, maintain fair on-call rosters, route every call to one place, require acknowledgement with automatic escalation, measure response times, triage remotely, keep critical parts accessible, protect lone workers, be clear about charges and communicate with customers throughout. Then use the data to prevent the next emergency.
Frequently asked questions
What counts as an emergency?
Define it with customers in advance — typically a risk to safety, a complete loss of a critical service, or a situation causing major damage or business loss. Everything else is scheduled for the next working day.
How should after-hours calls reach technicians?
Calls or online requests go to the on-call coordinator or straight to the on-call technician according to a roster, with automatic escalation if nobody acknowledges within a set time.
Should after-hours visits be chargeable?
Usually yes, unless the contract includes them. Clear call-out charges and rates, agreed in advance, prevent disputes. Contract customers may get a number of included emergency calls.
How do we keep lone technicians safe at night?
Use check-in and check-out on the app, scheduled safety check calls, a way to raise an alarm, and rules about work that must not be done alone.
What should we measure?
Response time to emergencies, time to restore service, number of calls that were not genuine emergencies, on-call workload per technician and customer feedback.
