Direct Answer (TL;DR)
Brilo AI Escalation Notification tells human agents when a call will be escalated to them and includes the transfer mode and a short context summary so the agent can prepare before joining the call. Notifications can be sent during a warm transfer (agent alerted first) or omitted for a cold transfer (call is dialed directly), depending on routing rules and telephony capabilities. Brilo AI sends session context such as recent transcript snippets, detected intent, and key entities when configured to do so. You can control notifications with escalation settings, confidence thresholds, and availability rules.
Will I get an alert before a transferred call? — Yes: Brilo AI can notify agents ahead of a warm transfer if warm transfers are enabled and routing rules allow it.
Do agents always receive context before escalation? — Not always: context delivery depends on your configured handoff mode and data-sharing settings.
Can I require agent acknowledgement before connecting? — Yes: when warm transfer with confirmation is enabled, Brilo AI waits for the agent to accept before joining the call.
Why This Question Comes Up (problem context)
Enterprise teams ask about Escalation Notification because human agents need time and information to serve regulated customers correctly. In healthcare and financial services, callers may present sensitive or complex needs that require a prepared agent. Buyers worry about caller experience, operational routing (warm vs cold transfer), and whether agents will have transcript or intent data to avoid repeating questions. Understanding notification behavior helps staffing, SLA planning, and compliance workflows.
How It Works (High-Level)
When escalation criteria are met, Brilo AI evaluates routing rules and the configured transfer mode to decide whether to notify a human agent. If a warm transfer is selected and an available agent is identified, Brilo AI sends a notification with a short context package (recent utterances, detected intent, and extracted entities) and waits for agent acceptance if configured. If a cold transfer is selected or no agent is available, Brilo AI will dial the target endpoint directly.
In Brilo AI, Escalation Notification is the configured behavior that alerts a target agent or system before the AI voice agent transfers an active call.
In Brilo AI, session context is the structured data (transcript snippet, intent label, entity values, timestamps) that Brilo AI attaches to handoffs so agents can continue the conversation without repeating information.
For details on intent detection and how Brilo AI decides when to escalate, see the Brilo AI article about how the AI understands caller intent: How does the AI understand what the caller wants?
Guardrails & Boundaries
Brilo AI follows configured guardrails to protect caller experience and safety. Escalation Notification will not bypass availability rules or send protected data unless your account and routing rules permit it. Brilo AI will not notify agents for escalations that occur outside configured paths (for example, when the escalation is a backend callback) and will not include unpermitted PHI or account numbers unless you have explicitly enabled those fields to be passed in handoffs.
In Brilo AI, confidence threshold is the numeric setting that triggers automatic escalation when intent detection confidence falls below the threshold.
Escalation Notification does not change the underlying call transfer mode: a warm transfer still depends on telephony provider capabilities and agent acceptance.
For recommended handoff modes and interruption handling (which affect when notifications occur), see: Can the AI handle interruptions during a call?
Applied Examples
Healthcare example:
A patient calls a clinic and requests medication authorization. Brilo AI detects a regulated subject line and falls below the configured confidence threshold; Escalation Notification sends a warm transfer alert to the triage nurse with the recent transcript and extracted medication name so the nurse can accept the transfer and review context.
Banking / Financial services example:
A retail bank caller asks about a disputed transaction. Brilo AI marks the intent as “dispute” and, per routing rules, notifies a fraud analyst via Escalation Notification and includes the last two transcript lines and transaction ID (if allowed by your data-sharing settings) before the warm transfer.
Insurance example:
A claimant asks to speak to an agent about an ongoing claim. Brilo AI triggers a callback handoff and notifies the claims rep through your webhook with intent and claimant ID so the rep can prepare before the outbound agent-to-caller connection.
Human Handoff & Escalation
Warm transfer: Brilo AI notifies the human agent with session context and waits for acceptance (agent confirmation required). Notification channels are configurable (telephony alert, CRM task, webhook).
Cold transfer: Brilo AI dials the target endpoint directly without prior in-app acceptance; notifications may be sent to downstream systems but the agent receives no in-call acceptance prompt.
Callback handoff: Brilo AI schedules or triggers an outbound call to a human agent or a callback workflow; notifications are included with the callback event.
When configured, Brilo AI passes context (transcript snippet, intent label, entities, timestamps) and optionally call recording metadata to the receiving agent. Handoffs respect your routing rules (availability, skill-based routing, and on-call schedules) and will fall back to voicemail or queueing when no agent accepts.
Setup Requirements
Configure escalation rules in the Brilo AI console to define conditions that trigger Escalation Notification (confidence thresholds, intent matches, or explicit “request human” intents).
Connect your target endpoints by updating agent routing: provide phone endpoints, your CRM integration, or your webhook endpoint for non-telephony notifications.
Enable warm transfer behavior and set whether Brilo AI should wait for agent acceptance or proceed with a cold transfer.
Define the session context fields that Brilo AI may include in notifications (transcript snippet, intent label, extracted entities).
Test the workflow with a live number and a staging agent to confirm notifications, acceptance flow, and context payloads.
Review and adjust the confidence threshold and routing rules based on test results.
For setup tips and admin requirements, consult the Brilo AI articles: Does the AI sound natural or robotic? (setup requirements) and How fast does the AI respond during a call? (performance & settings)
Business Outcomes
Improved first-contact resolution because agents receive context and can act immediately.
Reduced handle time and caller frustration through warm transfers with pre-populated context.
Better compliance posture in regulated sectors when notifications and context controls are audited and limited by policy.
More predictable staffing and SLAs because Escalation Notification clarifies when an agent will be required to accept a live transfer.
FAQs
Will Escalation Notification include sensitive patient data?
Brilo AI only includes fields you explicitly enable in the handoff configuration. Do not enable PHI or sensitive account information in notifications unless your internal policies and data handling controls permit it.
Can I force an agent to accept every escalated call?
You can require agent acceptance for warm transfers in Brilo AI, but enforcement depends on the receiving system’s integration and telephony capabilities; if the endpoint cannot support an accept/decline prompt, Brilo AI will follow the configured fallback behavior.
What happens if no agent accepts the notified transfer?
Brilo AI follows your fallback routing rules: it can queue the call, route to another team, place the caller in voicemail, or perform a cold transfer to a fallback endpoint, depending on your escalation settings.
Can notifications be sent to our CRM or ticketing system?
Yes. Brilo AI can deliver handoff notifications to your CRM or webhook endpoint when configured; ensure the receiving system can parse the context payload and that data-sharing policies are followed.
Does Brilo AI notify agents for callback handoffs?
Brilo AI includes the same context package in callback events when configured; the notification arrives as an outbound task or webhook event rather than an in-call accept prompt.
Next Step
Review your routing and handoff configuration in Brilo AI and confirm Escalation Notification settings in the console by following the intent and escalation guidance in: How does the AI understand what the caller wants?
Test warm and cold transfer flows in a staging environment; use the Brilo AI performance and setup guidance here: How fast does the AI respond during a call? and validate interruption and transfer behavior with: Can the AI handle interruptions during a call?
If you need to validate scalability or call-quality fallbacks, consult these implementation guides: Can the AI handle multiple callers at the same time? and Can the AI handle poor call quality?