Escalation
Escalation is the process of moving a call to a person, specialist, or higher-authority workflow when the current agent cannot safely, appropriately, or completely handle the request.
An escalation policy defines the conditions that trigger that move. Common categories include an explicit request for a person, a task outside the agent's permitted scope, an exception that requires judgment, repeated failure to understand the caller, unavailable information or systems, and a safety or compliance concern. The specific triggers should reflect the organization's own services and obligations.
Escalation does not always mean an immediate live transfer. Depending on urgency and availability, the next step may be a warm transfer, a cold transfer, a route to a specialist queue, or a documented follow-up. What matters is that the caller moves to a path with the authority or capability to address the unresolved need.
For an AI phone agent, escalation rules are part of the core call flow. The agent should recognize the trigger, avoid continuing an action it is not allowed to complete, collect only the information needed for the handoff, and tell the caller what will happen next. A loop of repeated questions is not a substitute for escalation.
The receiving person also needs usable context. A brief can include the caller's stated goal, relevant details already collected, actions attempted, and the reason for escalation. The amount of context should match the recipient's role and the organization's data-handling rules. If a live transfer is unavailable, the flow should set an accurate expectation instead of implying that someone will answer.
Teams should review escalation rate by reason and outcome. A rise may indicate a new caller need, a broken integration, an unclear prompt, or a sensible response to a higher-risk call mix. A low rate is not inherently better if the agent is attempting work that should go to a person. The useful question is whether the right calls escalated at the right time and reached a workable next step.
In practice on ThunderPhone
ThunderPhone supports cold and attended warm transfers. In warm mode, the caller waits on hold while the agent privately briefs the recipient and connects the call after acceptance. If the recipient declines, does not answer, or reaches voicemail, the agent returns to the caller with the outcome.