The after-hours playbook for home-service contractors

Covering nights is not really a phone problem. It is a policy problem that shows up as a phone problem. Before you automate anything, you need answers to four questions — and most shops have never written them down.

1. What counts as an emergency?

If this is undefined, every after-hours call becomes a judgement call at 11pm by whoever is most tired. Write the list once and it stops being a debate.

A workable HVAC definition:

Dispatch tonight

• No heat, outdoor temperature below 40°F
• No cooling, outdoor temperature above 90°F
• Any occupant who is elderly, an infant, or medically vulnerable
• Burning smell, smoke, or a tripping breaker
• Water actively leaking onto finished space
• Gas smell → tell the caller to leave and call the utility first, then dispatch

Book for the morning

• No cooling in mild weather
• Intermittent faults, odd noises, weak airflow
• Thermostat and control questions
• Anything the customer says can wait

Not tonight, not tomorrow — quote it

• Replacement inquiries
• Duct work
• New construction

That list fits on an index card, and it is the single most valuable artefact in your after-hours operation. It is also exactly what an AI agent needs in order to triage correctly, which is why we ask for it on the onboarding call.

2. What is the fee, and when is it waived?

Vagueness here costs you twice: the customer argues on arrival, and your CSR hesitates on the phone.

The structure that causes the fewest arguments:

• A flat after-hours dispatch fee, stated before the truck rolls
• Waived if the customer proceeds with the repair
• Charged if they decline or nobody is home

Say the number out loud on the call, every time, and get a verbal yes. Roughly a fifth of callers will opt for a morning slot once they hear it — which is a good outcome, not a lost job. You just avoided a night call that was never going to convert.

Whatever you decide, it must be a rule and not a mood. An agent, human or AI, can only quote a policy that exists.

3. Who is on call, and how do they find out?

Three models, in ascending order of how long your techs stay with you:

Owner takes everything. Works for a year, then does not. The owner becomes the bottleneck and eventually stops answering, which puts you back where you started.

Weekly rotation. One tech per week, paid a standby stipend whether or not they get called. Predictable for scheduling, and the stipend matters more than the callout rate for morale.

Tiered escalation. Primary tech gets the text. No acknowledgement in five minutes, it goes to the secondary. Still nothing, it goes to the owner. This is the model that survives a real emergency, because it does not depend on one person’s phone being charged.

Whichever you pick, the handoff should be a text with the details already captured — name, address, equipment, symptom, whether the fee was accepted. A tech woken at 1am to a message saying “call this number” will take fifteen minutes to get moving. A tech woken to a complete job card is in the truck in five.

4. What happens to non-emergencies?

This is where most revenue leaks, and it is invisible because nothing appears to go wrong.

The 9pm caller with a rattling blower is not an emergency. If they get told “we open at seven,” they will call someone else at seven. If they get booked into a 9am slot with a confirmation text, they are yours.

The rule: never end an after-hours call without either a dispatch or a booked appointment. “Call us back tomorrow” is the same as hanging up.

Putting it together

A complete after-hours flow, in the order it should run:

1. Answer within two rings. Every call. No exceptions, no hold.
2. Identify and triage against the index card.
3. Emergency → quote the fee, get a yes, text the on-call tech with the full job card, tell the caller the ETA window.
4. Non-emergency → book the earliest slot that suits them, confirm by SMS.
5. Out of area or out of scope → say so honestly and quickly. A ten-second no is better than a wasted morning.
6. Log everything. By 7am the office should have a written list of what came in overnight and what it became.

None of that requires AI. It requires the policy to exist and something to be awake. The reason we built an agent around this flow is that the policy is the hard part and staying awake is the expensive part — and only one of those is a problem software can take off your desk.

Write the index card first. Then decide who reads it at 2am.

• after hours
• dispatch
• on-call