Use case · After hours

It's 5 p.m. Someone still calls the plumber.

Your AI receptionist picks up on the number already on the truck. It answers questions, books appointments, and takes notes. Emergencies go live to on-call. Everything else is waiting when the shop opens.

An illustrative scenario for home service shops — plumbing, HVAC, electrical, and the trades that live on the phone. Not a named client case study.

After 5 p.m.

The call still comes in

A plumbing shop closes the desk. The phone does not. Here is what the voice receptionist does before anyone on your team is back on the board.

  1. 01

    5:12 p.m.

    Homeowner dials the shop

    The desk is closed. They still call the number on the truck — the same line they would have used at noon.

  2. 02

    Ring 2

    AI receptionist answers

    Overflow and after-hours coverage on the number you already have. Humans first when they can pick up; the agent when they cannot.

  3. 03

    First minute

    Answers the questions that matter

    Hours, service area, and whether you handle the trade. Listens for the real problem — not a phone tree.

  4. 04

    Triage

    Emergency vs bookable slot

    Runs against your rules: what counts as emergency, who gets the live transfer, and what stays a morning appointment.

Same call, two paths

Book the slot — or get a human now

Emergency language and routine work need different outcomes. Your rules decide the branch. The agent does not invent them.

  1. Call after 5 p.m.
  2. AI answers
  3. Questions
  4. Emergency?
Routine path

Qualify, capture, book

No emergency match. The agent captures the job the way a good dispatcher would, then holds a real calendar window — or a morning callback if the board cannot take it yet.

  1. Capture name, address, phone, problem, and access notes
  2. Offer a real slot on the calendar you already run
  3. If no slot exists: note plus a defined morning callback SLA
  4. Transcript logged so Tuesday is reconstructable

Morning outcome

Plumber opens a job ready to run — or a brief that asks them to confirm the appointment or call the homeowner back.

Emergency path

Live transfer to on-call

The caller matches your emergency criteria — active leak, no water, or whatever you define with us. The agent does not diagnose safety. It gets a human on the line.

  1. Match language against your approved emergency rules
  2. Hot-transfer to the named on-call plumber or queue
  3. High-stakes promises wait for staff — fees and ETAs stay bounded
  4. If transfer fails: capture plus priority callback, not silence

Live outcome

The plumber handles the call directly. The AI was the bridge — not a voicemail that waits until morning while water hits the floor.

Next morning

What the plumber wakes up to

For non-emergency calls, the night did not disappear into a callback list nobody works. The handoff includes the fields a human would have entered — plus a transcript.

Call back

A clean brief: who called, what they need, how to reach them. No scavenger hunt through voicemail.

Confirm the appointment

Slot is on the calendar. Review the notes, confirm with the homeowner if your process requires it, and keep the board honest.

Job ready to run

Best case: problem, address, access notes, and a booked window. Show up and do the work.

In the handoff

  • Caller name and phone
  • Service address and access notes
  • Problem description in their words
  • Booked window or callback SLA
  • Emergency vs routine classification
  • Full transcript of what the agent said and did

Guardrails

What the voice is for — and what it is not

Front desks and call centers miss a large share of inbound even on fully staffed days — lunch, overflow, after 5 p.m., Saturday storm jobs. We do not replace your people. We cover the gaps: FAQs, emergency vs. booked-slot triage, capture, and calendar booking with a clean handoff when the caller needs a human. Authority stays bounded. High-stakes promises wait for staff.

Good jobs for the agent

  • Hours, service area, and whether you handle their trade
  • Emergency versus bookable-slot triage against your rules
  • Capturing name, address, phone, problem, access notes
  • Offering real calendar windows — not fictional callbacks
  • Transferring when the caller asks, or when the situation is out of bounds

Bad jobs for the agent

  • Pricing a replacement from a two-minute story
  • Telling someone a gas or carbon monoxide situation is fine
  • Committing a tech to a window your capacity rules cannot hit
  • Arguing about a previous invoice
  • Replacing the front desk on a fully staffed day — this covers gaps

Callers should know they may be speaking with an automated assistant. We log what was said. Authority stays bounded until transcripts and booking accuracy earn more. Read the full essay →

One system among six

This is one use case we install

The after-hours receptionist sits under Respond — capture, nurture, reviews, ads, and coaching complete the operating layer. Perpetual Quest maps where revenue leaks and builds the workflows that close the gap.

Find your revenue leaks

After-hours voice is one leak we close. 30-minute Revenue Systems Audit. We map your lead flow, name where revenue is leaking, and show the first workflows we'd automate. No generic AI presentation.

Bring a missed-call report if you have one — that conversation goes faster.

Map My Lead Flow