Handle overflow. Follow up on missed calls.
There are two different moments to address: route an active call before it goes unanswered, or respond after a call has already been missed. The right workflow depends on your call setup and follow-up channels.
Two paths for two different situations
Prevention handles a call that is happening now. Recovery starts after the call has ended without an answer.
Prevention: active overflow
When a team is busy or unavailable, a configured route may send the active call to another team or an AI Voice Agent before it rings out.
Prevention: after-hours
An agreed time-based call flow can direct selected after-hours calls to an available destination, subject to service coverage and configuration.
Recovery: notification or callback
After a call is recorded as missed, a supported notification or callback workflow can prompt a team member to respond.
Recovery: configured follow-up
Where the required channel and integration are available, ACE can support an approved follow-up workflow and help route an interested lead to the team.
A practical follow-up sequence
The workflow should reflect the channels, consent, team capacity and business rules available in your setup.
Detect
Identify a call outcome recorded as missed using the configured call reporting or notification.
Respond
Prompt an appropriate callback or permitted message through a supported channel.
Qualify
When contact is made, establish what the caller needs and capture relevant details.
Handover
Send the engaged enquiry to the right team or agreed next step; a booking requires a supported calendar workflow.
No guaranteed bookings or recovered leads
A missed-call alert or follow-up can create an opportunity to reconnect, but it cannot guarantee that a caller will answer, remain interested or book. Message channels, timing, consent rules and system connections must be agreed for the workflow.
See AI Voice Agents for configured answering and overflow, and ACE for lead follow-up and revival.