Free operating guide
After-hours enquiry handoff checklist
A practical five-event map for Phoenix HVAC, plumbing, and electrical teams that want every after-hours call or web enquiry to reach a recorded next step and an accepted owner.
Start with the boundary
This is a handoff checklist, not an emergency-response script.
The purpose is narrow: make the journey from an inbound enquiry to an accepted owner and a recorded outcome visible. It does not decide whether a situation is safe, diagnose technical work, or replace the company's published emergency route.
First document the current route and capture a baseline. If the team cannot agree who owns an enquiry today, faster messages will not create accountable ownership tomorrow.
The handoff record
Record these five events for every relevant enquiry.
One row per enquiry is enough for a first baseline. Use observed timestamps and evidence from the systems the business already owns; do not backfill a convenient story when a value is missing.
Arrival recorded
Capture the exact time, source, contact route, service category, and whether the enquiry arrived inside or outside the published coverage period.
Minimum record: timestamp, source, route, coverage period.Acknowledgement recorded
Record when the customer received the first approved response. Acknowledgement is not the same as dispatch acceptance or a booked appointment.
Minimum record: response time, channel, approved message version.Classification recorded
Separate routine, urgent, out-of-area, duplicate, and unclear enquiries using rules approved by the business. Do not let automation invent safety or emergency advice.
Minimum record: category, rule used, unresolved exception flag.Ownership accepted
Name the person or queue responsible for the next action, then record acceptance. An alert sent to a group inbox is not proof that anyone owns the enquiry.
Minimum record: assigned owner, acceptance time, fallback owner.Outcome recorded
Close the loop with a plain outcome such as booked, declined, outside scope, duplicate, unreachable, or unresolved. Keep unknown outcomes unknown.
Minimum record: outcome, outcome time, source of evidence.A defensible recovery measure
Calculate recovery time from arrival to accepted ownership.
For each recovered enquiry, subtract its arrival timestamp from the time a named owner accepted the handoff or a documented final disposition closed the record. Add those elapsed minutes, then divide by the number of recovered enquiries. An automatic acknowledgement does not stop the clock.
- Use the original arrival timestamp for every included enquiry.
- Stop only at accepted ownership or a documented final disposition.
- Add the elapsed recovery minutes for records that reached a valid stop event.
- Divide by recovered enquiries and report unresolved enquiries separately.
Do not assign a convenient recovery time to an open record, and do not silently remove it from the baseline. Report the observed mean beside the unresolved count or share so the average cannot hide unfinished handoffs.
Use the free after-hours lead recovery calculator to apply the formula and test one economic scenario with your own inputs.
Before activation
Test the normal route and the uncomfortable routes.
A happy-path test does not prove the handoff works. Run the five scenarios below with approved internal test records—not with unsolicited calls or messages to customers.
| Scenario | What happens | Passing evidence |
|---|---|---|
| Routine | A non-urgent request arrives after the office closes. | Approved acknowledgement, next-business-period owner, visible due time. |
| Urgent | The customer describes a time-sensitive service issue. | Approved urgency language, human escalation, no unsupervised technical advice. |
| Outside scope | The location or service type is not covered. | Clear decline or alternate next step; no silent queue entry. |
| Duplicate | The same customer calls and submits a form. | One owner, linked records, no competing follow-ups. |
| Failure | The primary inbox, calendar, or routing step is unavailable. | Fallback owner alerted and the failure remains visible until resolved. |
Measure before changing
Run a 14-day baseline without inventing a revenue estimate.
Two weeks is long enough to expose weekday, weekend, and exception patterns for a pilot, while remaining short enough to review manually. The baseline is descriptive: it establishes what happened, not what a future workflow will earn.
- Time from arrival to first approved acknowledgement
- Time from arrival to accepted human or queue ownership
- Enquiries still unresolved at the next published business period
- Duplicate records or competing owners for the same enquiry
- Outcomes by source and coverage period, including unknown outcomes
Booking rate, job value, close rate, labour cost, and attribution should enter a business case only after the company supplies reliable source data and approves the causal assumptions.
Approval checklist
Do not switch on a recovery workflow until these controls have owners.
Published hours, service area, and escalation contacts are current.
Routine, urgent, outside-scope, duplicate, and failure rules have named owners.
Every customer-facing acknowledgement is approved by the business.
Emergency and safety language routes to a human and gives no invented advice.
Consent, messaging, recording, and retention requirements are reviewed for the actual channels and jurisdictions used.
The client owns the phone, messaging, calendar, CRM, and reporting accounts.
A fallback route is tested before the primary route is treated as live.
Outcome reporting separates observed facts from assumptions and unknowns.
Free first step
Get the public path mapped for your company.
Send only your business name and website. We'll return a concise public-path review that separates visible facts from the operating questions that require your data.
No phone call, system access, test call, or invented loss estimate is required.