Handoff template
On-call technician handoff template
The on-call technician is usually reading this on a phone, possibly woken up. The message has to be complete, short, and in the same order every time.
| Who receives it | The technician on your after-hours rotation |
|---|---|
| When it is used | After hours, when your written rules make a call urgent |
| Used by these call types | No-heat call intake checklist, No-cooling (AC not cooling) call checklist, Safety-sensitive call escalation checklist |
Why this handoff matters
An after-hours handoff fails in two ways: it arrives incomplete, so the technician has to call the customer and start the interview over; or it arrives and nobody confirms it was seen. Both leave a customer waiting who was told someone would call.
Vendors describe routing urgent after-hours calls to the on-call technician — Avoca's HVAC pages show emergencies 'routed to tech' and Goodcall's HVAC buyer article mentions escalating after-hours emergencies to the on-call technician. The routing is the easy part. The contents of the message and the acknowledgement loop are what the office has to design.
The acknowledgement problem is familiar across trades. A Smith.ai post on virtual receptionists for HVAC businesses quotes a customer (a remediation company) describing a 'call blast' set up so that a member of staff was guaranteed to receive each message. Whatever the mechanism, the office needs to know that a person has the call, not just that a message was sent.
What the handoff must contain
| Field | Why the receiver needs it |
|---|---|
| Why this is urgent (which rule applied) | Tells the technician the call met your policy, not a guess. |
| Customer name and confirmed callback number | First thing the technician needs. |
| Full address with unit and access notes | Can decide travel immediately. |
| Problem in the caller's words and when it started | No re-interview. |
| Equipment as described | Preparation. |
| Safety question answer | Always present, even when 'no'. |
| Plan status and any fee disclosed | Avoids arguments on arrival. |
| What the customer was told about timing | Technician knows the promise to keep. |
Example format
An illustrative layout with placeholder details. Adapt the labels to your own system; keep the order consistent so the receiver always knows where to look.
URGENT (rule: no heat, after hours, plan member) CUSTOMER: Name · (555) 010-0000 (confirmed) ADDRESS: Street, unit · gate code / dog in yard ISSUE (caller's words): "…" since about … EQUIPMENT (as described): furnace / heat pump / not sure SAFETY Q: no gas odor, no CO alarm, no burning smell reported PLAN: member (verified) · after-hours fee disclosed: yes TOLD CUSTOMER: technician will call within [your window] REPLY 1 = I've got it · REPLY 2 = can't take it (goes to backup)
Delivery channels
- Text message or app notification with the summary
- A phone call for anything your policy marks as safety-sensitive
- A copy to the dispatch board or morning log so day staff see it
Closing the loop
- The technician acknowledges within your set time.
- If not, the backup on your rotation is notified automatically or by the person answering.
- The outcome (called back, visiting, rescheduled) is logged for the morning.
Where this handoff breaks
| Failure | Prevention |
|---|---|
| Message missing the address or number | Required fields; do not send without them. |
| No acknowledgement, customer waits all night | Timed backup escalation. |
| Technician wakes up for a non-urgent call | State which rule made it urgent; review misroutes weekly. |
| Day staff unaware of the night's calls | Copy every handoff to the morning log. |
How the HVAC Reception concept would use it
Proposed · not available
The proposed HVAC Reception design would send the on-call technician a message in this order, only when your configured rules say the call is urgent, ask for acknowledgement, and escalate to your named backup when none arrives. It is a proposal; there is no working product.
Frequently asked questions
Text or call the on-call technician?
Many offices text the summary and call for anything safety-sensitive or unacknowledged. The important parts are a consistent format and a timed backup if the technician does not respond.
How long should we wait for acknowledgement?
Set a specific time in your policy and apply it every time. The right number depends on your rotation and customer commitments; what matters is that it exists and triggers a backup.
Should the customer be told the technician's name?
That is a company preference. Many offices say 'our on-call technician' and give a callback window rather than a name, so the message stays accurate if the backup takes the job.
What if the technician decides it can wait until morning?
The technician calls the customer and says so, and the outcome is logged. The office then reviews whether the urgency rule needs adjusting.