Direct Answer (TL;DR)
Brilo AI Restriction Layers let you combine multiple rule sets—such as topic allowlists, confidence thresholds, and operation-specific declines—so the voice agent enforces several restrictions at the same time. When multiple restrictions apply, Brilo AI evaluates them in a predictable order (for example: scope, confidence, then operation-level declines) and follows the first applicable escalation or fallback rule. This layered approach helps prevent the agent from attempting disallowed actions while still resolving safe, low-risk requests. You can configure layers to be cumulative or short-circuiting depending on the workflow and risk profile.
Can I stack restrictions in Brilo AI Restriction Layers? Yes — Brilo AI can be configured to evaluate and apply multiple restriction rules in sequence or priority order.
Can restrictions override each other? Yes — Brilo AI supports priority ordering so higher-priority restrictions can preempt lower-priority ones.
Will multiple restrictions cause the agent to always transfer to a human? No — when restrictions permit automated handling, Brilo AI continues; transfers occur only when rules or thresholds require escalation.
Why This Question Comes Up (problem context)
Enterprises ask about multiple restriction layers because regulated sectors require both broad and narrow controls. Healthcare, banking, and insurance teams often need organization-wide rules (for privacy and disclosures) plus case-level restrictions (for high-risk operations). Buyers need to know whether Brilo AI can enforce corporate policies, conversation-quality checks, and operation-specific declines at the same time without unpredictable behavior. Clear behavior and auditability matter for compliance teams and for operational routing logic.
How It Works (High-Level)
Brilo AI evaluates Restriction Layers as part of call processing and intent resolution. Typical evaluation order is:
apply scope and topic allowlists/blocklists
check signal-based thresholds (speech-to-text confidence and model confidence)
apply operation-level declines (sensitive or high-risk actions)
run any routing or escalation rules
Restriction Layers are a configurable set of ordered rules that the voice agent checks during runtime. Confidence thresholds are numeric or rule-based settings that determine when the agent should clarify or escalate. These layers can be configured to short-circuit (stop at the first matched rule) or to aggregate (require all checks to pass). For more detail on keeping answers grounded and using knowledge sources with restrictions, see the Brilo AI guide on preventing wrong or made-up answers (knowledge base grounding): Brilo AI knowledge-base grounding and answer-quality guidance.
Guardrails & Boundaries
Brilo AI Restriction Layers are meant to be conservative by default: they prioritize safety, auditability, and predictable handoffs. Typical guardrails include:
disallowing out-of-scope topics (scope guardrail)
forcing handoff when confidence is below thresholds
refusing or declining actions flagged as sensitive
capping clarification attempts to avoid conversational loops
A decline rule is a configured instruction that tells the voice agent to refuse certain requests and offer a fallback or transfer. For recommended escalation and fallback patterns (confidence thresholds and when to transfer), see the Brilo AI escalation and fallback guidance: Brilo AI handoff and escalation patterns.
Applied Examples
Healthcare: A Brilo AI voice agent can enforce a top-level policy that it will never provide diagnostic recommendations (topic block), while still answering appointment-scheduling questions. If the caller asks for a diagnosis or mentions specific symptoms, Restriction Layers trigger a decline rule and the agent offers to route to a nurse or schedule an appointment.
Banking: A banking IVR using Brilo AI can combine an allowlist for balance inquiries with an operation-level restriction that disallows fund transfers without multifactor human approval. If the agent detects low ASR confidence during account-number capture, the confidence threshold in the layer triggers a verification prompt or transfer.
Insurance: An insurance contact center can require mandatory disclosure language at call open (persona enforcement) and block policy-modification actions unless a human performs authentication. The layers ensure the agent reads the disclosure first and refuses policy changes unless the session has verified credentials.
Note: These examples describe workflow behavior; they do not imply certifications or legal suitability.
Human Handoff & Escalation
Brilo AI can hand off to a human agent or a supervised workflow when restriction layers require it. Typical handoff triggers include:
a matched decline rule for sensitive operations
confidence threshold breaches for ASR or intent detection
repeated clarification loops
detection of audit-sensitive keywords
Handoffs can be warm (bridge to a live agent with context) or cold (place on hold and create a ticket) depending on your routing settings. When configured, Brilo AI passes the relevant context and tags (which restriction fired, confidence score, last N utterances) to improve human efficiency and audit logs.
Setup Requirements
Define: Create a prioritized list of what the agent may and may not handle (allowlist and blocklist).
Configure: Set confidence thresholds for ASR and intent detection and map threshold outcomes to actions (clarify, retry, escalate).
Upload: Provide grounding sources such as your knowledge base or CRM records that the agent may use when permitted.
Map: Create decline rules for sensitive operations and assign priority levels.
Integrate: Connect your routing destination (your CRM, contact center, or webhook endpoint) for human handoff paths.
Test: Run staged test calls to validate that layered restrictions produce the expected escalations and refusals.
See these Brilo AI setup resources for implementation details:
Business Outcomes
Applying multiple Restriction Layers in Brilo AI yields practical outcomes: more predictable compliance behavior, fewer unauthorized or risky agent actions, and clearer routing to the right human when needed. Organizations see improved auditability because each escalation or decline is tagged with the triggering rule. These outcomes reduce policy exceptions and give compliance and ops teams confidence in automated call handling.
FAQs
Can multiple restriction layers conflict with each other?
Yes. If two rules conflict, Brilo AI follows the configured priority ordering. Set explicit priorities during setup to ensure predictable short-circuiting or aggregation behavior.
Will layered restrictions increase false transfers to humans?
They can if thresholds are set too conservatively. Tune confidence thresholds and clarification limits during pilot testing to balance automation versus escalations.
Can restriction layers reference external data like a customer’s risk profile?
Yes — when your knowledge base or CRM is integrated and permitted, restriction logic can use contextual signals (for example, account flags) to apply specific declines or escalation paths.
Are restriction evaluations logged for auditing?
Brilo AI records the rule that triggered any decline or handoff and includes relevant context in logs for audit and review, subject to your retention policies.
Can I change restriction priorities without redeploying the entire voice agent?
Yes — most restriction layer configurations are editable in the admin console and can be updated without a full agent redeploy, though testing is recommended before production rollouts.
Next Step