It's 9 PM in July. Your phone buzzes on the nightstand, and a restaurant manager's walk-in cooler is climbing with forty pounds of fish on the line. Two minutes later, another call: an office unit quit, but the building's empty until Monday. Both callers used the word emergency. Only one of them is.
That's the after-hours problem in one breath. Every caller swears it can't wait, your one on-call tech can't roll on all of them, and by morning you've got a full voicemail box, a couple of hang-ups, and three people who are angry you never called back. Nobody slept, and you still have to sort the pile before 7.
The fix isn't a bigger on-call crew. It's a simple flow that answers every after-hours call the same way, captures what you actually need, says the trip charge out loud, and sends the true emergencies to your tech while everything else lands on tomorrow's first-light list. You wake up to a sorted queue instead of a guessing game.
Decide what counts as a real emergency before the phone rings
You can't triage well at 9 PM if you've never written down what emergency means for your shop. Do it now, calm, at the kitchen table, not half-asleep with a caller pleading in your ear.
Here's a starting line most field-service outfits can live with. An after-hours call is a true emergency when it's one of these:
- No cooling with product on the line. A restaurant walk-in, a grocery case, a lab fridge. Fish and dairy don't wait for daylight.
- No cooling in a space people can't leave. An occupied building in a Houston heat index, a facility with elderly or medical occupants, a tenant with nowhere to go.
- No cooling at a site that runs around the clock. A server closet, a data room, a plant that can't go dark without losing a shift.
- A safety problem. Burning smell, water pouring, a breaker that won't hold, anything that reads as electrical.
Everything else is real to the caller, but it's a morning call. The empty office that won't cool until Monday, the comfort complaint, the unit that's making a noise. Be honest with yourself about that line, and your tech gets to sleep.
Write the greeting and the three questions once
An after-hours flow is just a recording that answers the phone, says a few lines, and collects a few answers. Some shops use an IVR (the automated phone menu that plays a message and takes input by keypad or voice). Others use a call service or an AI voice agent that asks questions and writes the answers into a message for you. The tool matters less than getting the same three things on every single call.
- The service address, read back to confirm. Half the after-hours confusion is a tech rolling to the wrong site or a strip center with five suites.
- The actual symptom in plain words. "Walk-in cooler reading 55 and climbing" tells you everything. "It's broken" tells you nothing. Prompt for it: what's not working, and what does it show?
- A callback number, spoken and confirmed, in case the line drops or the address is unclear.
Keep the greeting short. Nobody standing next to a warm cooler wants to hear a paragraph. Name the company, say you've got after-hours coverage, ask the three questions, done.
Say the trip charge out loud, before they commit
The dispute you never want is the one about money after the truck already rolled. The caller was panicking at 9 PM, agreed to anything, and by the time the invoice lands they've forgotten there was ever a charge for a midnight visit.
So put it in the flow, plainly, before they confirm. Something like: "Our after-hours trip charge is $X just to get a tech to your door tonight. Repairs are billed separately. If you want us to roll tonight, press 1 or say yes."
That one line does two jobs. It kills the 2 AM argument about the bill, because the caller heard the number and chose to proceed. And it quietly filters the list for you, because the person whose problem can genuinely wait until morning will usually decide it can wait once there's a dollar figure attached.
Split the calls: on-call tonight, or first-light tomorrow
Now the routing, which is the whole point. Once the flow has the address, the symptom, and a yes to the trip charge, it sends the call one of two ways.
- Matches your emergency list and agrees to the charge: push it straight to the on-call phone, with the address and symptom already captured so your tech isn't starting from a cold voicemail at midnight.
- Doesn't match, or the caller passes on the trip charge: log it to the first-light list, with a short note telling the caller you'll have someone reach out first thing and roughly when.
The first-light list is the quiet win here. Instead of a voicemail box you have to decode at 6:45 with coffee in one hand, you open your phone to a clean, timestamped queue: address, symptom, number, in the order they came in. Your dispatcher works it in a sensible route, not whoever yelled loudest. On a bad storm night when a dozen calls come in, that sorted queue is the difference between a rough morning and a wrecked one.
What this flow won't do for you
Be straight about the limits, because a flow that overpromises is worse than none. Automation sorts and captures. It does not have your judgment.
- It can misjudge a vague caller. A panicked manager might undersell a real emergency, or a calm one might oversell a nuisance. The flow goes on the words it hears, so build the emergency list to catch the clear cases and expect to eyeball the gray ones yourself.
- It shouldn't promise a time. Don't let the recording say "a tech will be there in an hour." It can't know your drive times across a service area that stretches from the Loop to the county line. Have it promise a callback, not an arrival.
- It still needs a human read in the morning. The first-light list saves you the sorting, not the deciding. Someone still looks at the queue and makes the calls.
If you'd rather not wire this up yourself, setting up this kind of flow for Houston field-service shops is the sort of thing we do, and it's a short job.
Worth setting up this week
You can stand most of this up in an afternoon. Start here:
- Write your emergency definition on one page. Four bullets, the ones that send a tech out tonight. Everything not on the page waits for morning.
- Script the greeting and the three questions: address, symptom, callback number. Keep it under thirty seconds of talking.
- Add the trip-charge line, with the real number, before the caller confirms.
- Decide the split and who holds the on-call phone, so a true emergency reaches a person and everything else drops onto the first-light list.
- Test it yourself from the truck before you trust it. Call the line from the parking lot, run through as an angry caller, and make sure the message that lands in your hand is one you could actually dispatch from.