EmpfangoThe short answer
A night-shift no-show can be covered without a private phone once three things are fixed: a number that always answers, an escalation chain with timings in seconds, and a fallback that does not leave the guard alone.
Today that chain hangs on one person in many companies: the dispatcher on call. This article shows how to separate answering the call from making the decision. Empfango answers the call, captures the no-show in a structured way and forwards it to the on-call contact. Who steps in is still decided by your team.
Why the night call ends up on a private phone
In job ads for dispatchers in the security industry, on-call duty and absence management are part of the standard profile, often with at least one week of on-call duty per month.
Three ads from October 2026 spell it out: “organise cover for absences”, “handle short-notice staff shortages”, “on-call duty at least 1 week per month” and “at least 40 % of working time on site with the client” (Sicherheit Nord, Contact Sicherheit, BOB Security, retrieved 14 Oct 2026).
The pattern: the dispatcher is out on sites during the day and at night is the only number a guard knows. A call at 11:50 pm therefore does not reach the company, it reaches a person in bed. If they do not pick up, there is no second place that even registers the no-show.
The industry is large enough for this pattern to repeat thousands of times: 4,517 security companies with around 291,000 employees, plus 5,478 open positions in February 2026 (BDSW, 12 Mar 2026, as of 10/2026). Where positions stay vacant, there is no second dispatcher for the night either.
What happens when nobody picks up
If the only night guard drops out and nobody steps in, the colleague on site cannot leave the property; one shift becomes two, and the Working Hours Act (ArbZG) is breached.
This is exactly the case described in secplaner's shift-planning guide: the relief is missing, the guard stays for a second eight-hour shift, and changes that are “organised only by phone or chat” lead to breaches of the ArbZG (secplaner.de, snippet, retrieved 14 Oct 2026). Section 3 ArbZG allows eight hours per working day, ten at most with compensation. Sixteen hours in a row are not covered, and the exceptions in Section 14 ArbZG are narrow.
For the client something else counts: between the no-show and the relief, the property was either unstaffed or staffed by an exhausted guard. Both end up in the guard book and come up at the next contract review.
The real problem is not that no-shows happen. It is that the first minute depends on chance: does the dispatcher hear the phone, do they have signal, are they even on duty? A chain that takes this first minute off the private phone is the lever.
The escalation chain: who, after how many seconds, with which fallback
A robust escalation chain defines for each stage who is called, after how many seconds the next stage kicks in, and what happens if nobody can be reached.
The table shows a chain as security companies set it up with Empfango. The ring timeout for call transfer is around 25 seconds. The timings for callback and relief are suggestions; they belong in your on-call plan, not in the software.
The difference from today's chain sits in stage 0 and stage 2: the call is answered and documented before any human is awake, and two people instead of one know about it.
| Stage | Who | After how many seconds | Fallback |
|---|---|---|---|
| 0 – Answer | Empfango | 0 s, even at 11:50 pm | None needed: the call is always answered; name, site, shift and callback number are captured |
| 1 – Transfer | On-call dispatcher (stored number) | Immediately after capture, ring timeout around 25 s | Not answered: Empfango promises the caller a callback and triggers stage 2 |
| 2 – Notification | On-call contact and deputy (operations lead) | Immediately after the timeout, via WhatsApp, Telegram, email or webhook | Both see summary and transcript in the dashboard; whoever reacts first takes over |
| 3 – Callback | Human from stage 2 | Target from the on-call plan, for example 10 minutes | No reaction: webhook to an alerting tool of your choice or a further number, as configured by you |
| 4 – Site | Guard on site | Until the relief arrives | Stays on site as instructed; times go into the guard book, compensation planned under the ArbZG |
What Empfango does – and what it does not
Empfango handles answering, structured capture, transfer with ring timeout and notification; the decision about who steps in and the rescheduling of the shift stay with your operations lead.
More on the flow and configuration is on the solution page on-call and escalation. How security companies use Empfango overall, from the night call to client enquiries, is on the page AI phone assistant for security services.
- Answering around the clock: the guard calls the company number, not a private phone. Empfango opens with a fixed announcement that an AI is speaking.
- Structured capture: name, site, affected shift, reason in keywords, callback number. No diagnosis, no questions about the illness.
- Transfer: Empfango connects to the stored on-call number. If nobody picks up after around 25 seconds, the caller is not left hanging on the line but is promised a callback.
- Notification: the summary goes via WhatsApp, Telegram, email or webhook to the on-call contact and the deputy. Transcript and summary are in the dashboard.
- Not included: Empfango does not reschedule shifts, does not request replacement staff and does not write into any dispatch software without a webhook. That remains the job of the control room or operations lead.
How to set up the chain
Setup takes an afternoon: store the on-call numbers, define the capture questions, choose the notification channels and test the chain once at night.
What on-call duty means in employment law and where the line to standby duty runs is explained in the glossary entry on-call duty. For comparison, the cost of a human 24/7 phone service: Die Telefonhelden, the only phone service with its own security-industry page, list from 199 € per month plus 0.99 € per minute (rates, retrieved 14 Oct 2026). Empfango costs from 99 € per month, fixed price with no top-ups, see pricing.
- Check the on-call plan: which number applies in which week, who is the deputy? Both must be stored in the assistant, otherwise the call rings into the void.
- Define the capture questions: site, shift start, callback number. Keep the list short; the caller is ill or has an emergency.
- Choose the notification: for the night, a combination has proven useful, such as WhatsApp to the on-call contact plus email to the deputy.
- Inform staff: the company number replaces the private phone. Explain that an AI answers and what the announcement sounds like.
- Test call at 11 pm: run through it yourself once, measure timeout and callback, and put the timings into the on-call plan.
Frequently asked questions
No. Empfango replaces the private phone as the first point of contact, not the on-call duty. The dispatcher is still reached, but via the company number, with the details captured first and with a deputy who is informed automatically if they do not pick up.
Then the stage you have defined kicks in: a webhook to an alerting tool, an email to management or a further number. In every case Empfango documents when the call came in and who was notified.
Yes, as long as it only captures what the employer may know anyway: that and for how long someone is absent, not why. The assessment of Art. 9 GDPR and the announcement is in the article sick calls by phone and GDPR.
Yes. The control room stays responsible for alarms. Empfango intercepts routine calls such as no-shows, shift questions and enquiries and forwards only what the control room really needs.
Conclusion
A night-shift no-show is not an exception in the security business, it is part of operations. The question is whether the first minute hangs on a private phone or on a chain that always answers, captures, transfers and informs two people. The decision about who steps in stays with you. Everything before that can run without anyone having to be awake.