Unavailable-line coverage
- Explain that the normal team is unavailable or at capacity.
- Collect the caller’s identity, reason and preferred follow-up channel.
01 · Concrete applications

Cover a published line when the team is unavailable.
Capture who called, why and how urgently they need a response.
Share a limited approved message or opening-time information.
Create a callback task or reach the authorised on-call person.
02 · Operating model
03 · Call journey
Explain that the regular team is unavailable or at capacity.
Collect the caller’s reason, contact details and timing.
Check the on-call, priority and callback rules.
Share the permitted message and create a follow-up task.
Transfer urgent or explicitly covered situations to the on-call person.
04 · Connected tools
06 · Questions
Reception is the normal entry point; an answering service covers missed, overflow or after-hours periods. Its scope is usually narrower and governed by explicit continuity and on-call rules.
It can apply defined indicators and routing rules, but it should not improvise urgency. Uncertain, safety-related or out-of-scope situations go to the configured human or emergency channel.
Only the fields required by the callback workflow should be collected. The organisation determines identity checks, access, retention and which team receives the task.
A second fallback can provide an approved message, try another authorised destination or keep a monitored task. The agent should not claim that contact was made when it was not.
Banana Navy · Voice AI
We map the journey, permitted actions, integrations and human handover before choosing the architecture.