After-hours phone answering with an AI agent: a playbook
The phone does not know you are closed. It rings at ten at night with a burst pipe, at seven in the morning with a cancellation, and on Sunday with someone who wants to book for Monday. For years the choice was voicemail, an answering service, or your own mobile on the bedside table. A voice agent is a fourth option: it picks up, says it is an AI, handles what can be handled, and wakes a person only when a person is needed. This playbook sets one up in five steps.
Step 1: decide what a night call is for
Before writing anything, sort your after-hours calls into three kinds. Emergencies, which need a person now. Bookings and questions, which need an answer but not tonight. And callers who just want to be heard: they will not be seen tonight, but they want to know that someone will call them tomorrow. Count yours for a fortnight before you decide which group is biggest.
The agent's night job is smaller than its day job, and that is a feature. At night it does not need to sell, explain your full price list, or hold a long conversation. It needs to recognise an emergency, book what can be booked, and take a good message. Write those three jobs at the top of its instructions and resist adding more.
Step 2: write the evening greeting
The greeting sets the caller's expectations in the first ten seconds. It should say the business name, say it is an AI, say that the office is closed and when it opens, and offer the three doors. Something like: "Hello, you have reached (business name). I am an AI assistant. The office is closed until eight tomorrow morning. If this is urgent, tell me and I will get you a person. Otherwise I can book an appointment or take a message. What can I do for you?"
Notice that the greeting names the reopening time. Callers relax when they know how long the wait is. The simplest way to keep the greeting right for the hour is to make the night agent its own agent, with its own opening line and its own number, and send calls to it only outside opening hours. For the wording of everything after the greeting, Writing instructions for a phone agent is the place to start.
Step 3: escalation rules that hold at 3 a.m.
An escalation rule written at a desk at noon will be tested by a stressed caller and a sleepy colleague at three in the morning. Keep it plain.
- What counts as urgent, in the caller's words: water where it should not be, no heating in winter, pain that cannot wait, a tenant locked out. Write your own list.
- Who is on call, per weekday. The agent warm-transfers to that number, briefing the colleague privately before connecting, so the caller does not repeat the story.
- If nobody answers: the agent returns to the caller, says so honestly, takes a message, and sends the caller a text confirming that someone will ring back, and when.
- What it must not promise: an arrival time, a price, or that a person is on the way, unless a person has actually said yes.
- A second fallback: another on-call number, or the instruction to tell the caller which emergency service to ring if there is danger.
The transfer step is the one that separates a real product from a demo. How a warm transfer works shows what happens when the on-call phone turns out to be a voicemail.
Step 4: forwarding, overflow and the morning handover
Calls reach the agent through a forwarding rule at your phone provider or in your phone system: forward when nobody picks up, when the line is busy, or outside opening hours. That last rule is the night setup. The first two are overflow, and the same idea covers lunchtime peaks during the day with a day agent that has the full day job. Overflow answering describes that setup.
In the morning, the day team needs one list, not a voicemail queue. Every night call ends with a transcript, a summary and an outcome: booked, message taken, transferred, or unsure. Read the list with coffee, ring the callbacks first, and check the ones marked unsure. If you want the list in your own system, a webhook fires when each call completes, so the messages can land in your CRM or ticket queue before anyone arrives. Calls shows what is written down.
Step 5: measure the first month
You will not know whether the night agent is working until you count. For the first month, note four things each week: how many calls came in after hours, how many the agent escalated to a person, how many it booked, and how many messages were rung back before ten the next morning. Then listen to a handful of calls, especially any marked unsure or transferred, and fix the instruction that caused each wobble. If escalations are high, tighten the urgent list. If messages pile up, the morning routine is the problem, not the agent. Compare the four numbers with the tally you kept before, using the method in What a missed call really costs.
Where NordTell fits
NordTell gives you the pieces this playbook needs: an opening line per agent, a number per agent, warm transfer to an on-call number with a private briefing, a text to the caller, and a summary and outcome for every call. It answers in thirteen languages with safety nets and always keeps a way to a person. Calls are handled on servers in the EU, and the product is built in Copenhagen.