Escalation Matrix

A set of rules that determine when and how an AI-managed conversation should be transferred to a human agent, based on triggers like topic, sentiment, or customer tier.

Technical definition

An escalation matrix defines trigger conditions (keyword match, sentiment score threshold, topic classification, customer attribute, explicit request), routing rules (which team or individual receives the escalation), priority assignment (based on customer tier or issue severity), and notification channels (email, Slack, PagerDuty). The matrix is evaluated on every message in real time.

How Verabase uses Escalation Matrix

Verabase's escalation matrix is configured in Agent Settings → Escalation Rules. You define rules like: 'If the customer mentions billing dispute AND their plan is Enterprise, escalate to the Billing team with High priority.' Rules can also trigger on sentiment (if the customer sounds frustrated), on AI Critic blocks (if the AI can't give a verified answer), or on explicit customer requests ('I want to speak to a human'). Escalated conversations appear in the Live Inbox with full context.

Why it matters for support teams

Not all escalations are equal. A frustrated enterprise customer asking about billing needs immediate attention from a senior agent, while a free-tier user asking a product question can wait. A well-configured escalation matrix ensures the right conversations reach the right people at the right time, maximizing both customer satisfaction and team efficiency.

Related terms

How Verabase Handles Self-Healing Knowledge

The standard industry approach relies on support agents manually flagging stale content and technical writers updating documentation weeks later. Verabase completely upends this model through an autonomous AI platform that identifies knowledge gaps the moment an AI agent encounters a question it cannot answer.

Rather than requiring manual intervention, our visual RAG engine drafts a proposed fix. It analyzes the context of the user's question, reviews your existing knowledge base for conflicts, and creates a clear, structured article or snippet. All you need to do is click 'Approve'. This ensures your AI agents continually get smarter over time without adding to your support team's workload.

Security First Architecture

Many legacy platforms bolt AI onto their existing infrastructure, creating potential data leaks between tenants or exposing sensitive internal documents to end-users. Verabase is built from the ground up with a Bring Your Own Key (BYOK) architecture, enterprise-grade access controls, and strict semantic boundaries. This means your private engineering documents never accidentally leak into customer-facing agent responses.