It's 12:40 on a Tuesday in January. Your phone lights up on the nightstand. A furnace quit somewhere across town, the house is sliding past 55 degrees, and there's a newborn in the back bedroom. You're half asleep and hunting for a pen.
Multiply that by every cold snap. The calls stack up between 9 PM and 6 AM, they all sound like emergencies, and some of them actually are. Sorting the real no-heat from the 'it feels a little chilly in here' at that hour is a job by itself.
You can't clone yourself. But you can put a system between the phone and your sleep that catches the call, asks the right questions, tells the customer the truth about price, and wakes up only the person who's on tonight. Here's how the pieces fit together.
Triage the call before you pick up
An AI intake line is a phone number that answers in your voice, day or night, and walks the caller through a short script. No heat? Any smell of gas? Water leaking anywhere? Is anyone in the house at real risk, an infant or someone elderly? It writes the answers into a ticket and texts you the summary.
The point isn't to replace you. It's to collect the five facts you'd ask for anyway, so that when your phone buzzes you're reading a tidy summary instead of interviewing a scared homeowner at 1 AM.
Build the script so danger jumps the line. A possible gas smell or carbon monoxide worry rings you immediately, no waiting. A thermostat that might just have dead batteries can hold for a morning callback, and the system can say that politely without you lifting a finger.
- Is there heat at all, or is it just weak?
- Any gas smell, burning smell, or alarm going off?
- Water leaking near the unit?
- Anyone in the home medically vulnerable to the cold?
- Address, callback number, and gate or parking notes.
Say the after-hours price out loud
Emergency work costs more. You know it, and most customers know it too. What burns people is learning the number at the door, half asleep, in their slippers. So put it in front of them before you ever roll the truck.
Have the intake agent state it plainly: 'Our after-hours emergency rate is a trip charge plus labor, and a typical no-heat visit usually runs in this range.' Then it asks them to confirm they still want a truck tonight. That one exchange kills the 2 AM argument on the porch before it starts.
You're not hiding anything, and you're not apologizing for charging what the hour is worth. A price they agreed to over text is worth a lot more than a handshake nobody remembers by morning.
Wake the right person, not the whole crew
If you run more than one tech, you've got a rotation. The trouble is the rotation lives in your head or on a whiteboard back at the shop, and at midnight nobody's looking at the whiteboard.
Load the schedule into the system instead. It knows Mike's on this week and Dave's up next. When a real emergency lands, it texts Mike first with the full ticket. No answer in ten minutes? It bumps to the backup and lets you know it did.
That buys you two things. Mike sleeps on his off weeks, which is how you keep him from quitting in February. And you stop being the human switchboard who gets woken up for every call whether you're on the hook that night or not.
The paperwork you skipped at 2 AM
Here's where the money quietly leaks. You fixed the furnace at 3 AM, snapped a photo of the cracked igniter, drove home, and crashed. The invoice never got written. Three weeks later you half remember the job and undercharge for it.
Set the system to build the morning-after packet on its own. It pulls the ticket, the after-hours rate they already agreed to, and the notes you thumbed in on site, then drops a draft invoice in front of you with your coffee.
- Draft invoice with the trip charge and hours already filled in.
- The photos and notes attached to the right job.
- A short customer recap of what you found and what you did.
- A flag if the fix was a patch, not a permanent repair.
Same goes for the follow-up. A no-heat call in the dead of winter is often a bandage, not a cure. The system can queue a text a few days out: 'How's the heat holding up? Want us to quote replacing that unit before the spring rush?' That's a real job you'd otherwise forget to chase.
What this won't do
AI can't diagnose your furnace, and it can't call a true emergency with perfect accuracy. It's a screener, not a technician. Set the danger questions conservatively so it errs toward waking you, never toward sitting on a real problem.
It also won't calm a panicking customer the way your actual voice will. For the truly scared ones, the best setup hands off fast: grab the basics, then connect a person or promise a callback in a set number of minutes, and then keep that promise.
And it won't fix a rotation that's already broken on paper. If your on-call schedule is a mess, automating it just sends the confusion out faster. Sort the human part first, then let the software carry it.
Worth doing this week
None of this needs a big software project. Start with the parts that stop the bleeding tonight.
- Write your five triage questions on one sheet, danger first, and read them out loud to see if they flow.
- Decide your after-hours number and the exact sentence that says it to a customer.
- Get your on-call rotation out of your head and into something a system can read.
- Pick one thing to automate first: the intake call or the morning-after invoice. Just one.
If wiring these pieces together sounds like one more thing you don't have time for, that's exactly the kind of setup we build for Massachusetts trades at Mass AI Agency.