How to Set Up an AI Phone Agent for After-Hours Calls

Log two weeks of after-hours calls, decide what the agent may do for each type, and pick a tool with schedule-based answering and live transfer (from roughly $30 to $150 a month). Then write the script and emergency rules, forward your number outside opening hours, set an on-call chain, and test 20 calls at night. Allow one to three days.

After-hours calls are different from daytime overflow. There's nobody in the office to take a transfer, the caller is often anxious, and a wrong decision at 2am costs more than one at 2pm: either an emergency waits until morning or an engineer gets woken for something that could have waited. So most of the setup is deciding who gets woken and when, and making everyone else feel properly dealt with until the morning. The technology is the easy part.

Follow me on Instagram@sagnikteaches

Stage 1: log two weeks of after-hours calls

Before choosing anything, find out what actually happens when you're closed. Your phone system or mobile call log shows missed calls by time; voicemails show what people wanted. For two weeks, note each one. An illustrative summary for a four-person electrical contractor, closed 6pm to 8am and at weekends:

Connect on LinkedInSagnik Bhattacharya

Two weeks gave 24 calls, so roughly 50 a month. Only 3 were real emergencies, but those are the ones that matter most, and 10 new enquiries were going to voicemail, where many callers don't leave a message. The log also tells you the language callers use ("burning smell", "tripping", "sparks"), which goes straight into the script in stage 4.

Subscribe on YouTube@codingliquids

Stage 2: decide what the agent may do with each type

For every call type, set three things: what the agent does, what it may promise, and what it must never say. Written down, this becomes the agent's instructions.

The "must never" column prevents most after-hours incidents. The worst is an agent reassuring a caller about something dangerous. Safety advice should be your exact approved wording, checked by someone qualified, not the AI's own words. For a deeper treatment of emergency routing, see setting up an AI answering service that never misses an emergency.

Stage 3: choose a tool that fits your volume

For after-hours use, the features that matter are a business-hours schedule, live or warm transfer to a mobile (with backup numbers), text messages to callers and staff, call summaries by email, and a clean fallback if the service fails. Some options, at list prices in September 2026:

For the electrician's 50 calls a month at around 2.5 minutes each, that's about 125 minutes. Rosie's Professional plan covers the minutes, but live transfers, which the emergency rule needs, start on Scale at $149. Jobber Receptionist would cost $29 plus 20 extra conversations at $0.79, about $45 a month, if the firm used Jobber. A build on a voice platform would cost roughly $10-$40 a month in usage, plus someone's time to create and maintain it. The firm chose Rosie Scale: the transfer feature was the requirement, and the price difference was small against a single missed emergency job. Wider cost comparisons are in what an AI receptionist costs.

Stage 4: write the after-hours script

Most tools let you write instructions in plain language plus a knowledge section. Keep it short and specific. A template, filled in for the electrician:

GREETING
"Thanks for calling [firm]. We're closed right now, and you're
through to our automated assistant. Calls may be recorded. Is this
an emergency, or can I take a message for the morning?"

EMERGENCY SIGNS (transfer immediately)
Burning smell or smoke from sockets, switches or the fuse box;
sparks; exposed or damaged live wires; total loss of power with
a vulnerable person in the home; water getting into electrics.
Before transferring, say exactly: "If you smell burning or see
smoke, leave the property and call the emergency services. If it's
safe, switch off at the main switch." Then transfer.

NOT AN EMERGENCY (message for 9am callback)
One circuit tripping; lights or sockets not working in one area;
outside lights; quotes; questions about existing jobs.

ALWAYS COLLECT
Name, phone number, address, what's happening, whether anyone
vulnerable is in the property, best time to call.

NEVER
Give prices except: "Call-outs start from [amount]; we confirm
the cost before starting any work." Promise an arrival time.
Diagnose a fault. Cancel or move bookings.

CLOSE
"Thanks, [name]. I've passed this to the team and you'll get a
text confirming it. We'll call you before 9am."

The greeting does three jobs at once: it says you're closed, it says the caller is talking to an automated assistant, and it mentions recording. If you serve customers in the EU, the EU AI Act's transparency duty, which has applied since 2 August 2026, expects people to be told they're dealing with an AI; this line covers it. Call-recording consent rules vary by place, so check yours. More on writing these instructions is in the tutorial on call scripts and escalation rules for an AI receptionist.

A first draft that went wrong, and the fix

Scripts rarely survive their first real calls unchanged. An illustrative removals firm set up its agent with a knowledge section listing tomorrow's jobs, so it could reassure callers. At 9.40pm a customer rang: "We're moving tomorrow, is the van definitely coming at eight?" The agent replied, "Yes, your move is confirmed for 8am tomorrow." It wasn't: the booking was provisional pending a deposit, and the office had been trying to reach the customer all afternoon.

The fix was a rule, not a better model: the agent may say what the diary shows only as "our records show a provisional time of 8am; the office will confirm first thing". It also takes the caller's number and flags the call "move tomorrow" at the top of the morning digest. The customer gets an honest answer and an early call, rather than a promise the firm might not keep.

Stage 5: set the on-call chain and its timeouts

A transfer is only as good as the person at the other end. Decide the order, how long each phone rings, and what happens if nobody answers:

1. On-call engineer (rota changes weekly): rings for 25 seconds.
2. Second engineer: 25 seconds.
3. Owner: 25 seconds.
4. If nobody answers: the agent tells the caller the safety wording again, promises a call back within 15 minutes, and texts all three people with the caller's details and "EMERGENCY - NO ANSWER".

Keep the rota in one place the tool reads, or update the first number every Friday as a calendar task. A realistic failure: an electrician's on-call phone was on silent because of a do-not-disturb schedule that allowed only favourite contacts through at night. The agent's transfer number wasn't a favourite. The fix took a minute: add the agent's outgoing number to the phone's allowed contacts, then test it at 11pm, which is exactly what stage 8 is for.

Storm nights need a thought of their own. Picture a roofing contractor after high winds: 30 calls between 10pm and 2am, all saying "tiles have come off". Transferring every one would bury the on-call roofer. The script therefore separates "water is coming inside the property now" (transfer) from "tiles or flashing are missing but it's dry inside" (morning call, with advice to move valuables away from the affected room). Check that your tool can answer several calls at once; Rosie, for instance, says it handles multiple calls simultaneously. A single-line voicemail can't.

Stage 6: route calls to the agent by schedule

How you send calls to the agent depends on your phone setup:

• Cloud phone system: set a time-based rule: office hours ring your team; outside them, forward to the agent's number. Add public holidays to the schedule.
• Mobile as the business number: most networks offer forwarding when unanswered, busy or unreachable, but not by time of day. Either forward "when unanswered" permanently (the agent also catches daytime missed calls) or switch forwarding on and off each evening. A separate business number on a cloud phone system is cleaner.
• Porting your number to the tool: some tools offer it. It simplifies routing but ties your number to the vendor; I'd forward rather than port until you're sure.

A realistic slip: a removals firm set its schedule in winter and forgot that its phone system's clock used a fixed time offset. When the clocks changed, calls went to the agent from 5pm instead of 6pm for a week before anyone noticed from the call summaries. Check the schedule the week after every clock change and before every public holiday.

Stage 7: design the morning handover

The agent is only half the system; the other half is what happens at 8am. Ask for one summary email per call, or better, a single digest at 7.30am, and put it where the first person in will see it. An illustrative digest entry and what to fix:

Call 3 of 9   Tue 21:47   2 min 40 s   Type: Urgent (not emergency)
Caller: [name], [phone]   Address: [address]
Summary: Kitchen circuit trips when kettle and toaster are both
on. Rest of house fine. No burning smell. Elderly mother lives
with caller. Prefers call after 10am.
Promised: callback before 9am.
Action needed: CALL BACK BEFORE 9AM

Spot the conflict: the agent promised a callback before 9am, but the caller asked for after 10am. Fix the script so it asks for the best time first and promises that, and flag "vulnerable person in property" at the top of the entry, because it changes the priority. If you keep a CRM, have the summaries logged there automatically, as covered in logging AI call summaries in your CRM. Then assign a named person to clear the digest by 9am, every day, including Mondays after a weekend.

Stage 8: test 20 calls at night

Test at the times real calls come, from phones that aren't in the tool's contacts, with people who haven't read the script. A test list:

1. A clear emergency in plain words.
2. An emergency described vaguely ("there's a funny smell near the fuse box").
3. A non-emergency described dramatically ("my outside light is completely dead!").
4. A caller who asks "am I talking to a robot?"
5. A caller with a strong accent, and one on a bad mobile line.
6. Background noise: a crying baby, a busy road.
7. Silence for 15 seconds after the greeting.
8. An angry existing customer whose engineer didn't turn up.
9. Someone asking for a price for a rewire.
10. Someone trying to get the agent to cancel tomorrow's booking.
11. A sales call.
12. An emergency when the on-call engineer deliberately doesn't answer, to test the chain.

Run each a couple of times (about 20 calls in all) and score them: right category, right action, nothing promised that shouldn't be, summary accurate. If more than one in ten goes wrong on the emergency tests, don't go live until it's fixed. Call 2 is the one that most often fails first time; add the vague phrases callers use to the emergency list.

Tell your team and your customers before go-live

Engineers need to know what an agent transfer sounds like, or they'll reject it as a spam call. Show them the number it rings from, and ask the tool to brief them before connecting (a warm transfer): "Emergency call from [name] at [address], burning smell from fuse box, caller has switched off at the main." They should also know the chain, so the second engineer isn't surprised at 1am.

For customers, update your website contact page, your voicemail greeting and your email signature. Wording I'd use:

Our office is open 8am-6pm, Monday to Friday. Outside those hours,
calls are answered by our automated assistant, which takes messages
and passes genuine emergencies to our on-call engineer. We return
all other calls the next working morning.

Budget for the costs beyond the subscription too: whatever you pay engineers for being on call, the 15-30 minutes a morning to clear the digest, and any charges your mobile network makes for forwarded calls, which some do. None of these is large, but they belong in the monthly figure you compare with the jobs the agent brings in.

Stage 9: review every week for the first month

Track a few numbers from the tool's reports and your own records each week:

• After-hours calls answered, and how many callers hung up during the greeting.
• Emergencies transferred, and any that should have been but weren't (check the summaries).
• Transfers that weren't emergencies, which is the number your engineers will care about.
• Callbacks made by the promised time.
• New enquiries captured, and how many turned into booked jobs.

For the electrician, a first month might look like: 52 calls answered, 4 emergencies transferred correctly, 1 false transfer (a tripping circuit described as "sparks"), 21 new enquiries captured with 8 booked jobs. If the average job is worth a few hundred dollars in margin, two or three extra booked jobs a month pay for the tool several times over, and that is the number to watch. The 90-day version of this review is in measuring an AI receptionist's return.

After-hours phone agent questions

Do I have to tell callers they're speaking to an AI?

It's the honest thing to do and it avoids complaints. If you serve customers in the EU, the EU AI Act's transparency duty has applied since 2 August 2026, requiring people to be told they are interacting with an AI system unless it's obvious. A short opening line such as 'You're through to our automated assistant' covers it, and callers who hate bots can ask for a message to be taken instead.

Can the AI agent record and transcribe calls?

Most tools record and transcribe by default, which makes the morning handover much easier. Recording rules differ between places: some require every party's consent, others one party's. Mention recording in the greeting, check the rules where you and your callers are, and set a retention period in the tool so recordings don't pile up indefinitely.

What if the AI agent goes down in the middle of the night?

Ask the vendor what happens to calls if its service fails. Good setups fall back to voicemail or forward to a backup number. Test it by pausing the agent during a trial and calling in. Also keep a normal voicemail greeting on your phone system as the last step, so a caller never hears a dead line.

Will an AI agent work with my mobile number?

Usually, through call forwarding: calls to your mobile forward to the agent's number when you don't answer, or at set times. Mobile forwarding is often 'when unanswered' rather than time-based, so some owners use a separate business number on a cloud phone system, which can route by schedule. Check what your network or phone system allows.

Further reads

• How to Set Up an AI Receptionist Without Losing Callers — The daytime version: setting up an AI receptionist without losing callers.
• AI Receptionist for Tradespeople: What It Costs and When It Pays — What an AI receptionist costs a trades business and when it pays.
• Can AI Triage Emergency Plumbing Calls Out of Hours? — How emergency triage works for plumbing calls specifically.
• AI Receptionist or Answering Service for a Booking-Based Business? — Whether a human answering service suits you better.
• How to Review AI Call Transcripts for Quality and Compliance — Reviewing call transcripts for quality once you're live.
• What Is the Cheapest Way to Handle Enquiries Out of Hours? — Cheaper options if a phone agent is more than you need.
• How a One-Person Travel Agency Can Reply to Enquiries Instantly — A two-speed reply system for solo travel agents: a useful answer within a minute, then an AI-drafted personal reply you check and send the same day.
• How Campsites and Glamping Sites Use AI to Answer Guests — A site facts sheet, the questions guests ask at each stage, where the AI should answer, and the rules it must never bend on a campsite.
• What Is an AI Receptionist and How Does It Handle Bookings? — A plain-English look at what happens inside an AI receptionist during a booking call, and the three very different things vendors mean by 'handles bookings'.
• Can AI Answer Calls and Qualify Leads for an Insurance Agency? — How an AI voice agent should route, qualify and score insurance calls, the phrases it must never say, a 20-call test plan and what it costs to run.
• A Worked AI Implementation Plan for a Small Medical Practice — One small medical practice's 12-week AI plan, from time audit to scribe rollout and phone overflow, with the costs, the numbers at day 90 and the lessons.
• AI for Veterinary Practice Owners: Costs, Tools, and First Steps — What AI costs a vet practice in 2026, which tools do which jobs, budgets for one-, three- and five-vet practices, and a six-week plan to start safely.
• AI vs Human Answering Service for HVAC Firms — When an HVAC firm should let AI answer the phone, when a person should, and why most end up with a hybrid that escalates emergencies.
• Cutting Parcel-Tracking Calls With AI Delivery Updates — How a small courier firm can find why customers ring, send updates at the moments that matter, and let AI handle exceptions and leftover questions.
• How Independent Pharmacies Use AI to Shorten Phone Queues — Count the calls, then cut them: ready-to-collect texts, a phone menu that listens, a voice assistant with firm limits, and callbacks instead of hold music.
• How to Set Up Missed Call Text Back for a Service Business — Turn unanswered calls into text conversations: the three ways to set it up, five ready-to-edit messages, AI-drafted replies and a test script.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Rosie, Smith.ai and Retell AI pricing pages; facts sheet for Jobber Receptionist pricing and EU AI Act Article 50 dates. Business figures are illustrative. Checked September 2026.