Human Handover

The process of transferring an AI-managed conversation to a human support agent when the AI can't resolve the issue or the customer requests a real person.

Technical definition

Human handover is triggered by escalation rules (safety triggers, low confidence, explicit customer request) and involves transferring the full conversation context — message history, customer profile, CRM data, and AI analysis — to a human agent's queue. The transition should be seamless to the customer, with no loss of context and no repeated information.

How Verabase uses Human Handover

In Verabase, human handover happens through the Live Inbox. When a conversation escalates — either because the AI Critic blocks a response, the customer asks for a human, or a custom safety rule fires — the chat moves to the Unassigned queue. A human agent clicks Take Over, sees the full conversation history plus the customer's CRM profile in a side panel, and can write private internal notes before responding. The customer sees a smooth transition with no gap in the conversation.

Why it matters for support teams

AI can handle 60–80% of support queries, but the remaining 20–40% require human judgment, empathy, or authority. A poor handover — where the customer has to repeat their issue — is worse than no AI at all. Seamless handover with full context ensures that AI augments your team rather than frustrating your customers.

Related terms

See also

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.