Skip to content
FinnleyAI

The after-hours call playbook for home services companies

By FinnleyAI Team · Builders of FinnleyAI

For a home services company, after-hours calls split into two piles with almost nothing in between: genuine emergencies where minutes matter, and everything else. The whole game is telling the piles apart quickly, handling the first one flawlessly, and not losing the second one to a competitor whose phone got answered. Here’s the playbook, in five steps.

Step 1: Write down what counts as an emergency

The most expensive words in after-hours coverage are “use your judgment.” Whoever answers your phone at 2 AM — an employee, a service, or software — will make triage decisions, and unwritten rules mean inconsistent decisions. Write yours down, by trade. A starting point:

  • Dispatch now: active water intrusion, no heat in freezing temperatures, no cooling during a heat emergency for vulnerable occupants, sewage backup, storm damage exposing the structure, any electrical burning smell.
  • Emergency services first, then dispatch: gas smell, sparking panels, active fire or flooding that threatens safety — the caller is told to call 911 or the utility before your tech is involved.
  • Books for business hours: everything else — a slow drip, a unit “acting weird,” a quote request, a maintenance-plan question.

Your list will differ. What matters is that it exists, in writing, so triage is a rule that fires rather than a judgment call made by whoever is groggiest.

Step 2: Decide who gets woken up, and how

An emergency rule is only useful if it ends with a named, reachable person. That means a real on-call rotation — not “call the owner” forever — and an escalation path with the details attached: who’s on call tonight, how they’re contacted, how long before an unanswered page rolls to the backup. The goal is that the tech who wakes up already knows the address, the problem, and what the caller was told, before they return the call.

Step 3: Capture enough to dispatch without a callback

The difference between a five-minute dispatch and a forty-minute one is usually one missing detail — the gate code, the unit’s location, whether anyone is home. Whoever answers should capture: verified caller and address, the problem in the caller’s words, the equipment involved if known, access instructions, and anything the caller already tried. There’s a field-by-field guide to complete intake if you want the full anatomy; the test is always the same — can the tech act on the record alone?

Here’s the shape of a good one (a hand-crafted example, not customer data):

Example — inbound call, 1:52 AM Sunday Caller: Dana A. — matched to existing customer recordRequest (caller’s words): “The water heater is leaking through the garage ceiling and it’s spreading.” Severity: Emergency — rule: active water intrusion Context: Water heater in attic above garage; caller is home; supply valve location known Actions taken: Job created with address and equipment; caller walked through closing the supply valve; on-call tech paged with summary Disposition: On-call tech confirmed dispatch, 1:56 AM

Step 4: Handle the non-emergency like revenue, because it is

The 9 PM caller with a struggling AC doesn’t need a truck tonight — but they will book with whoever answers. If your after-hours experience is voicemail, the pile of “everything else” calls quietly becomes your competitor’s schedule. The playbook here is simple: answer, reassure, and book a real appointment slot on the spot. “Someone will call you back tomorrow” loses to “you’re booked for tomorrow between 10 and noon” every time.

Step 5: Log everything for the morning

The morning dispatcher should start the day with a clean list: what came in overnight, what was dispatched and why, what got booked, and what needs a decision. Every call — including the ones that didn’t become work — should exist as a record with a transcript. That’s how you catch the near-misses, tune your emergency rules, and settle any dispute about what was said at 2 AM.

Who should actually answer the phone?

Any of the classic three can run this playbook — a night-shift employee, an answering service, or an AI receptionist — and we’ve written an honest comparison of all three. The short version: humans bring judgment but are expensive to keep awake and consistent; answering services take messages but usually can’t verify callers, apply your dispatch rules, or book jobs; software applies your rules identically on every call but must escalate cleanly when a call falls outside them.

If you want to hear the playbook run live — your trades, your dispatch rules, your edge cases — see how Finnley handles home services calls or book a 15-minute demo.

Hear Finnley handle your calls.

Book a 15-minute demo and we’ll run your scenarios — your rules, your edge cases — live.