Automating the on-call phone: 24/7 cover without burnout

The real problem: not the emergency, the false alarms

If you offer an on-call service, the genuine emergency is not your problem — that is what the on-call rota is for. What wears people down are the other calls: the appointment question at 11 at night, the customer who "just wants to give you a heads-up", the price question on a Sunday morning. Every one of them pulls you out of sleep, costs you concentration the next day — and was almost never worth it.

In many businesses that is exactly why nobody wants to take on-call duty any more. And hiring extra help is easier said than done: 36 % of companies cannot fill open positions, at least in part (DIHK skilled-labour report 2025/26). Spreading on-call duty across even fewer shoulders only makes the problem worse.

Filtering instead of ringing through: how the automated on-call service works

The basic idea is simple: at night the on-call phone no longer rings first — the assistant picks up instead, immediately, with no queue. It asks in a structured way what has happened and checks it against your emergency rule. Water running, heating completely down, power gone: if the request matches that rule, then, and only then, does it put the call through to the on-call number you have stored.

Everything else it takes down in full: the request, the name, the callback number — and it reads a dictated callback number back digit by digit. The caller has got the request off their chest and knows it has landed. The person on call sleeps on.

What matters in practice: what counts as an emergency is for you to define — as a rule in the assistant, for example: if the request is a burst pipe, a complete heating failure or a power cut, put it straight through to the person on call. The "Trades, plumbing & electrical" industry template already comes with a rule like this, "Pass on emergencies at once"; you adapt it to your trade. Anything that can wait, a dripping tap for instance, the assistant takes down as a message for a callback on the next working day. The more clearly you describe the emergency, the cleaner the filtering. And because the assistant answers only from the knowledge base and invents nothing, it will not promise callout times overnight that you cannot keep in the morning.

When a call is put through: what the person on call knows — and what not

The groundwork pays off in a real emergency too. Before the assistant puts a call through, it knows what the call is about, and it tells the caller it is putting them through. The person on call hears none of that beforehand, though: they have the caller straight on the line, and the transcript and summary reach the inbox only after the call. So a quick "What has happened, and where?" remains. And if the person on call does not pick up for once, nothing is lost: the assistant comes back on the line and takes down the request with a callback number, it sits in the inbox marked urgent, and after the call the notification arrives by email and, if a mobile number is stored, by SMS — saying that putting the call through failed.

The night log: up to speed in five minutes in the morning

Every night-time call lands in the shared team inbox with a transcript and a summary — nothing is recorded, there is only text. In the morning the office sees it at a glance: three calls last night, one put through, two callback requests with number and request. The callbacks can be planned rather than improvised, and a record builds up along the way — who reported what, and when, is there in black and white: the summary for 12 months by default, the transcript for 21 days; you choose the periods yourself.

Setup: not a technology project

The route is short and takes about 10 minutes with scoco.ai: choose the greeting and the voice, store the on-call number as the destination for putting calls through, set up a rule for genuine emergencies, and feed the knowledge base with the area you cover and "from" prices for an emergency call-out. Then switch on call forwarding — activate it in the evening and turn it off in the morning, or leave it running permanently as a delayed rule, so that during the day you still pick up yourself. Your number stays, and nothing on the phone system is rebuilt.

What all this looks like during the working day is described in "AI phone assistant for trades"; for the heating season specifically: "Heating emergency calls: ready for the first frost night".

What automation honestly does not solve

Someone still has to drive out — the assistant sorts calls, it does not fix faults. Nor does it make a technical judgement: it applies your rules, and whatever no rule clearly matches, it takes down as a message. If you would rather be woken in case of doubt, describe the emergency more broadly in the rule. Which means: occasionally a call that could have waited will still wake you — just far less often than today. And some callers would rather talk to a human at night; what matters is that the request is reliably taken down and that the callback really does come in the morning.

And it is not an emergency service. A fire or anyone in danger is a matter for 112. A caller who smells gas belongs outside the building and should only call the gas network operator's emergency line once outside, because they should not use a phone indoors (as, for example, Stadtwerke Kaiserslautern advises); if anyone is in danger, 112 applies here too. The trades template does not tell the caller this of its own accord. So this advice belongs wherever your emergency number appears, on your website for example.