Direct Answer (TL;DR)
Brilo AI Knowledge Prioritization is the runtime rule set the Brilo AI voice agent uses to choose which knowledge source to consult and which answer to present when multiple knowledge bases match a caller's request. It combines intent detection, contextual signals from the call (caller metadata and recent dialog), and answer ranking (confidence scoring) to select the best source and response. Administrators can configure source order, scope, and trust rules so Brilo AI routes queries to the most appropriate knowledge store and falls back safely when confidence is low. Knowledge Prioritization supports consistent caller triage, controlled answer extraction, and predictable routing behavior.
How does Brilo AI decide which knowledge base to use? — Brilo AI uses intent, context, and confidence to pick the highest-priority source and answer.
Does Brilo AI prefer internal documentation over CRM records? — Brilo AI follows configured source precedence; admins set whether CRM records, knowledge base articles, or operational systems are preferred.
What happens if no source has a high-confidence answer? — Brilo AI can be configured to escalate, offer a safe fallback response, or create a ticket.
Why This Question Comes Up (problem context)
Enterprises ask about Knowledge Prioritization because calls often touch multiple systems and teams. In regulated sectors like healthcare, banking, and insurance, the wrong data source or an outdated article can create compliance, privacy, or operational risk. Buyers need to know how Brilo AI voice agent capabilities choose, order, and limit knowledge sources so answers are accurate, auditable, and aligned with internal escalation rules.
How It Works (High-Level)
Brilo AI Knowledge Prioritization operates as a runtime decision layer inside the Brilo AI voice agent. At call time the agent:
Detects intent and extracts entities from the caller’s utterances.
Collects contextual signals such as caller attributes, recent dialog, and routing metadata.
Looks up candidate answers across configured knowledge sources (knowledge base, CRM, or other knowledge stores).
Scores and ranks candidates using confidence scoring and answer ranking rules.
Applies configured precedence and routing rules to select the final source and response.
A knowledge source is any configured repository the voice agent can query (for example, your knowledge base, CRM record store, or operational FAQ). For an example of how Brilo AI applies intent and urgency to route and triage incoming calls, see the Brilo AI customer support triage use case (Brilo AI customer support triage use case).
Guardrails & Boundaries
Brilo AI enforces guardrails so prioritization does not return unsafe or non-authoritative answers. Typical guardrails include:
Confidence thresholds: Brilo AI will not present answers below a configured confidence score and will instead use a fallback or escalate.
Source precedence: Administrators define which sources are authoritative for a topic; lower-priority sources are only used if higher-priority sources do not return a viable answer.
Redaction and access controls: The voice agent will avoid exposing sensitive fields unless the caller is authenticated and the policy permits it.
Read-only policies: For regulated workflows, Brilo AI can be restricted to read-only lookup and not write or change records.
A confidence score is the numeric measure the system uses to decide whether an answer is reliable enough to present automatically.
For guardrail examples and sector-specific behavior in insurance support workflows, see Brilo AI’s insurance support resource (Brilo AI insurance support resource).
Applied Examples
Healthcare: A patient calls about appointment rescheduling. Brilo AI first checks the appointment scheduling system (high precedence for clinical workflows), then the patient-facing FAQ knowledge base if scheduling metadata is absent. If caller authentication fails or the confidence score is low, Brilo AI offers to connect to a human scheduler.
Banking: A caller asks about an unexpected transaction. Brilo AI prioritizes transaction records in the bank’s CRM or ledger system, then applies a fraud-flag routing rule. If the answer requires account-sensitive data, Brilo AI requests caller verification and offers escalation to a live agent when required.
Insurance: For a claim-status question, Brilo AI favors the claim database as the authoritative source and falls back to general policy FAQ articles only when claim data is incomplete.
Human Handoff & Escalation
When configured, Brilo AI voice agent workflows escalate or hand off in these ways:
Warm transfer to an available agent when confidence is below threshold or the caller requests a human.
Create a ticket in your CRM and inform the caller of expected follow-up if no immediate answer is available.
Route to a specialized queue when the selected knowledge source indicates high urgency or regulatory sensitivity.
Hand-offs are driven by routing rules attached to prioritization outcomes: the voice agent evaluates the chosen source and the answer score, then follows the configured escalation path.
Setup Requirements
Define: Identify and list the knowledge sources you want Brilo AI to query (knowledge base, CRM, document store, webhook endpoints).
Map: Map topics or intents to authoritative sources and set source precedence for each intent.
Configure: Set confidence thresholds, fallback responses, and escalation routes in the Brilo AI console.
Connect: Provide access details for each source (API keys, read-only service accounts, or your webhook endpoint).
Test: Run sample calls and review logs to validate source ordering, answer ranking, and fallback behavior.
Iterate: Adjust precedence rules and thresholds based on call analytics and supervised review.
For conceptual background on conversational logic and setup considerations, see Brilo AI’s conversational AI overview (Brilo AI conversational AI overview).
Business Outcomes
When Brilo AI Knowledge Prioritization is applied correctly, organizations can expect:
More consistent caller outcomes by ensuring authoritative sources are preferred.
Reduced misroutes and fewer unnecessary live transfers through reliable triage and routing.
Better auditability because source selection and confidence scores are logged with each response.
These outcomes support operational scalability without overstating specific efficiency gains.
FAQs
How does Brilo AI handle conflicts between two knowledge sources?
Brilo AI follows configured source precedence and confidence scoring; the higher-precedence source wins unless its confidence score is below the configured threshold, in which case the agent will consider the next source or use a fallback.
Can Brilo AI prioritize CRM records over a public FAQ for the same question?
Yes. Administrators set source precedence so Brilo AI consults your CRM or record store first for account-specific queries and only uses public FAQ content as secondary context.
What happens if a knowledge source returns outdated information?
You control authoritative sources and refresh cadence. Brilo AI will follow source precedence, but you should maintain and version authoritative repositories; low-confidence or stale content should trigger a human review workflow.
Can prioritization be different by caller type (e.g., patient vs. provider)?
Yes. Brilo AI supports conditional prioritization based on caller metadata.
You can configure different precedence and escalation rules depending on caller identity or role.
Next Step
Review how Brilo AI applies triage and routing in production: Brilo AI customer support triage use case (Brilo AI customer support triage use case).
Read the Brilo AI guide on designing voice-agent knowledge workflows: Brilo AI best practices for AI voice agents (Brilo AI best practices for AI voice agents).
Learn core conversational principles that affect prioritization: Brilo AI conversational AI overview (Brilo AI conversational AI overview).