After Hours Only, Overflow Only, or Every Call: How to Scope It, and How to Write the On-Call Escalation Rule
Start with after hours plus busy or no answer. Do not start with every call. That scope catches the two places calls actually die (nights, weekends and holidays, and the daytime moments when your CSR is already on the line) without changing your front desk during business hours. Then write the escalation rule, so the only thing reaching your on-call tech at 2 AM is a call that meets a defined emergency condition and a caller who has confirmed, out loud, that they want a truck tonight at the after-hours rate.
Still deciding whether the category fits your shop? Start with the overview of an AI receptionist for contractors. This page assumes you are past that.
What are the three forwarding scopes, and what does each one catch?
| Scope | Forwards when | Best fit | Blind spot |
|---|---|---|---|
| Busy or no answer (overflow) | Your line is busy, or nobody picks up after a set ring count | Shops with a CSR covering the day | Everything after close, unless you add after hours |
| After hours only | Outside posted hours, plus weekends and holidays | Shops with a covered day desk whose nights roll to voicemail | Daytime calls lost while your CSR is on another line |
| All calls | Every inbound call, from the first ring | Owner-operators, shops with no CSR, accounts buying calls | Nothing, but it changes the first voice every customer hears |
All three are settings in your phone system, not a rewiring job. Busy or no answer is a conditional forward: your line rings first, and the call rolls only if it is engaged or unanswered past the ring count you set. Regulars still get your CSR, and simultaneous callers stop hitting voicemail. That is the scope that carries a demand spike, when three days of calls land in one morning, as in an HVAC heat wave call surge. All calls is where owner-operators land, and anyone buying calls: a paid call nobody answers costs you more than the lost job, because responsiveness feeds back into the channel. See missed calls and Local Services Ads ranking.
Which scope should you pick? Here is the decision rule.
Pull the last 30 days of call detail records from your phone system. Split every call by hour of day and by disposition (answered, abandoned, sent to voicemail).
- Most unanswered calls inside posted hours: you have an overflow problem. Start with busy or no answer.
- Most after 5 PM, before 8 AM, or on a weekend: you have an after-hours problem. Start with after hours only.
- Both buckets ugly, or you are the one carrying the phone: go all calls.
Do the count before you buy anything. A vendor guessing at your call pattern is still guessing.
What is actually riding on the after-hours line?
Two vendor-reported figures are worth putting in front of you here, and you should read them as vendor-reported.
Cactus reports that a plumbing and HVAC company in Utah booked about $150,000 in confirmed revenue in four months, and that about 58 percent of those captured leads came in after hours. Cactus reports that a roofing company in North Carolina collected about $299,000 in ten weeks.
Read the 58 percent carefully, because it is the figure most likely to get misused. It is the after-hours share of captured leads at one company, in one trade, in one market. It is not the after-hours share of that company's total call volume, and it is not an average across Cactus customers or across the trades. A shop with a staffed day desk can show a low after-hours share of total calls and still show a high after-hours share of leads, because daytime volume includes every hours question, every callback and every check on an existing job, while the night calls skew toward people with a problem right now.
The number that decides this for you is your own. Here is the worksheet:
Monthly after-hours calls (counted from your own call records) x your booking rate x your average ticket = the revenue currently riding on your voicemail greeting.
Booking rate and average ticket are your inputs, not ours. Use your actuals from last season rather than a number a vendor hands you. Then set that figure against Cactus list price, $999 per month, which covers every call, day and night, not only the after-hours slice. To run the comparison on a per job basis instead, see cost per booked job.
How do you keep the on-call tech from being woken for a Tuesday problem?
Here is the arrangement this replaces. At close, the phones roll to an answering service. The service pages the on-call tech when something sounds bad to whoever is on the headset. Everything else gets recapped with him the next work day. Two things break there. The service has no basis for judging whether a call is an emergency, so in practice it pages everything or it pages nothing. And the recap happens after the caller has already phoned somebody else.
The fix is not a better answering service. It is a written escalation rule with three buckets, applied on the call, before anyone's phone lights up.
Wake him. Active water with no shutoff, sewage backing up into the house, gas odor (911 or the utility first, then you), no heat below your defined outdoor temperature threshold, no cooling with an infant or medically vulnerable occupant, roof leaking during rainfall, total power loss at a commercial account under contract.
Book it first thing. Unit short cycling but running, one room off, a drip caught in a bucket, thermostat questions, a noise, an estimate request, a warranty question, anything the caller describes in the past tense.
Handle it and log it. Hours, pricing ranges, service area, rescheduling, "was it you who came out Tuesday", callbacks on an existing job.
Then add the rule that does the most filtering: state the after-hours dispatch fee on the call and get an explicit yes before you page anybody. Once they hear the rate and that the first morning slot is 7 AM, callers whose problem can wait will often take the morning. They are not lost. They are booked, and your tech sleeps. How that judgment gets made in the moment is broken down in how AI answering triages emergency calls.
Whatever tool you use, require a logged reason on every after-hours call. If you cannot audit why the system woke someone, you cannot tune it, and within a month you are back to paging everything. That same log is what you check your invoice against, which matters more than it sounds like it should. See answering service billing and spam calls.
Every caller you do not escalate should still hang up with a named arrival window and a confirmation text, not a voicemail beep. Cactus creates the job in Jobber or Housecall Pro during the call, so a 2 AM booking is on the board before your dispatcher opens the app in the morning. The mechanics are in AI receptionist Jobber and Housecall Pro booking. That difference is most of the after-hours capture, and it costs your tech no sleep.
FAQ
Should I put AI on after-hours calls only or on all my calls? Start with after hours plus busy or no answer. That covers nights, weekends, holidays and daytime overflow while leaving your front desk intact. Move to all calls if your own 30-day records show heavy daytime abandonment, or if you have no CSR.
How many calls actually come in after hours? It depends on your trade, your posted hours and your ad mix, so pull 30 days of call detail records and split them by hour. For one reference point, Cactus reports that at a plumbing and HVAC company in Utah, about 58 percent of captured leads came in after hours. That is one company's share of captured leads, not a share of total calls, and not an industry average.
Will this stop my on-call technician from being woken up unnecessarily? Only if you write the escalation rule. Define which conditions justify a page, quote the after-hours dispatch fee on the call, require the caller to confirm they want a truck tonight, and book everything else into the first morning slot.
Does after hours mean just nights? No. Nights, weekends, holidays, and any block when the office goes dark, including lunch. Weekends are usually the largest piece.
Next step
Bring your last 30 days of call records. In a 20 minute demo we will split them by hour and disposition, show you which scope your data calls for, and write the escalation rule for your on-call rotation. Book a demo at go.oncactus.com/book-a-demo.