Direct Answer (TL;DR)
Brilo AI supports caller-initiated Manual Request so callers can ask for a human agent during a call. When Manual Request is enabled, the Brilo AI voice agent listens for explicit requests and predefined trigger phrases, evaluates intent and confidence scores, and follows configured escalation rules to perform a warm transfer or schedule a callback. Manual Request behavior is controllable in the agent’s escalation settings so administrators decide when transfers happen automatically and when the agent asks for confirmation. This lets Brilo AI balance deflection with agent availability and preserve call context for the human agent after transfer.
Can a caller ask to speak to a person? Yes — Brilo AI can be configured to accept Manual Request and escalate to a human agent when triggered.
Can callers say “agent” or “human” at any time? Brilo AI will detect those phrases when Manual Request triggers and the agent’s intent detection and confidence thresholds are met.
Will asking for a human always transfer immediately? That depends on your configured escalation rule — Brilo AI can do immediate warm transfers or offer a callback option when agents are unavailable.
Why This Question Comes Up (problem context)
Enterprises ask about Manual Request because callers expect a predictable path to a human during complex, emotional, or regulated conversations. Contact center planners need to know how Brilo AI balances automated handling with agent load, call routing rules, and context preservation. Security, auditability, and customer experience are all affected by when and how Brilo AI honors manual escalation requests.
How It Works (High-Level)
When Manual Request is enabled, the Brilo AI voice agent continuously evaluates caller speech for escalation triggers using intent detection and confidence scoring. If a caller issues a Manual Request and the confidence threshold is met, Brilo AI follows the escalation rule you configured: a warm transfer to a live agent, a queued callback, or routing to a specialist workflow. Brilo AI passes call context — recent utterances, detected intent, and key metadata — to the receiving agent to avoid repetition.
Manual Request is a configured feature that lets callers explicitly request a human agent during an active call. Call context is the bundle of recent prompts, inferred intent, and metadata the voice agent passes to the human agent at handoff.
See Brilo AI’s explanation of call transfer workflows for more on routing and context-aware transfers: Brilo AI AI Phone & Voice Agents for Call Transfer.
Technical terms used: manual request, human handoff, warm transfer, callback handoff, intent detection, confidence score, call context.
Guardrails & Boundaries
Brilo AI enforces guardrails so Manual Request does not create unsafe or confusing behavior. Common guardrails include confidence thresholds, required confirmation prompts, agent-availability checks, and rules to block escalation on sensitive topics unless explicitly allowed. Brilo AI also logs the trigger phrase, confidence score, and routing decision for audit and quality review.
An escalation rule is a configured policy that defines when and how the agent escalates to a human (for example, immediate transfer vs. offer callback). Brilo AI will not escalate if the escalation rule or agent-availability checks block a transfer; it will instead offer next-best actions such as a callback or scheduling an agent call-back. For guardrail configuration and quality controls, see guidance on naturalness, escalation, and when to escalate: Brilo AI help article on AI behavior and escalation.
Applied Examples
Healthcare: A patient calls to clarify medication instructions and asks to speak to a nurse. If Manual Request is enabled, the Brilo AI voice agent detects the request, confirms intent, and escalates to the on-call triage nurse or schedules a callback if clinical staff are unavailable. Brilo AI passes visit context and recent utterances to minimize repeated intake questions.
Banking: A customer asks to speak with a fraud specialist after noticing an unfamiliar charge. Brilo AI’s Manual Request triggers an immediate warm transfer to the fraud team when available, and it populates the specialist with the suspected transaction details and the caller’s verified account metadata.
Insurance: A claimant requests to speak to an adjuster about a complex claim. Brilo AI detects the escalation phrase, evaluates confidence, and follows your escalation rule to route to the correct claims team or to schedule a secure callback.
Human Handoff & Escalation
Brilo AI supports multiple handoff modes when handling a Manual Request:
Warm transfer: Brilo AI places the caller on a brief hold and joins a short bridge while passing call context to the human agent.
Cold transfer + context push: The caller is routed and a structured context packet is sent to the agent desktop or CRM.
Callback scheduling: If agents are unavailable, Brilo AI offers a callback window and records caller preferences.
When configured, Brilo AI includes the last n minutes of transcript, detected intent, confidence scores, and any captured authentication or verification tokens in the handoff payload so the human agent can resume without re-asking primary questions.
Setup Requirements
Enable Manual Request: Open the Brilo AI console and toggle Manual Request or escalation handling for the target voice agent.
Define trigger phrases: Specify the phrases and synonyms your team wants Brilo AI to accept as Manual Request triggers.
Set confidence thresholds: Configure the confidence score threshold that must be met before escalation proceeds.
Configure escalation rules: Choose warm transfer, callback, or specialist routing and set agent-availability rules.
Connect routing destinations: Provide your target agent queue, webhook endpoint, or CRM integration for context delivery.
Test and deploy: Run live calls and tune prompts, confirmation flows, and guardrails before full deployment.
For design patterns on reducing unnecessary transfers and tuning deflection, review Brilo AI’s call deflection guidance: Brilo AI How Brilo Uses AI Call Deflection.
Business Outcomes
Enabling Manual Request with thoughtful escalation rules helps Brilo AI reduce repeated questioning, lower caller frustration, and ensure complex calls reach the right human quickly. Organizations typically see improved first-contact resolution on escalated calls and better agent readiness because Brilo AI supplies concise context at handoff. These outcomes are operational and depend on agent staffing and configured routing policies rather than being guaranteed performance claims.
FAQs
Can a caller request a human at any time during the call?
Yes — if Manual Request is enabled for the Brilo AI voice agent and the trigger phrase meets the configured confidence threshold. Administrators can require confirmation prompts or additional verification before transfer.
What phrases should I enable for Manual Request?
Common phrases include “I want to speak to a person,” “agent,” or “representative,” plus synonyms specific to your business. Balance inclusivity with precision to avoid accidental escalations.
Will Brilo AI pass personal or sensitive data during the transfer?
Brilo AI can pass structured call context and recent transcript snippets to the receiving agent as configured. You control what fields and metadata are included in the handoff payload based on your privacy and data-handling policies.
What happens if no agents are available when a Manual Request occurs?
Brilo AI follows your escalation rule: it can offer to schedule a callback, place the caller in a queue, or route to an overflow destination. The agent-availability check you configure determines the exact behavior.
Next Step