AI escalation and human handoff best practices

A useful handoff does two things: it moves the right conversation to a person, and it captures enough context for that person to continue without asking the customer to start over.

Start with a small rule set

Begin with high-value scenarios:

A specific team task, such as preparing an invoice
A serious business or safety issue
A payment, charge, or refund dispute
An order, appointment, or account change the agent cannot complete

Add narrower rules only after reviewing real conversations. Too many broad rules can create unnecessary handoffs.

Configure a scenario

Open Handoff Rules

Go to Configuration → Handoff Rules and confirm Enable automatic handoff rules is on.

Add a scenario

Select Add scenario and give it a name an operator will understand.

Describe the trigger

State what should trigger the handoff and, when helpful, what should not.

Choose business scope

Use selected businesses when the workflow or responsible team differs by location.

Request essential fields

Collect only information the operator needs to take the next action.

Save and test

Test one message that should trigger the rule and one similar message that should not.

Where handoff rules apply

Handoffs use a separate workflow. Their clarification and acknowledgment do not load the normal Knowledge Base context or Custom Instructions. Configure scenario triggers and required fields here rather than in a knowledge document or personalization rule. Required fields are prerequisites for the matched scenario. If a field is missing, Visito asks for it before creating that scenario’s handoff. Only require information that can safely delay escalation. This setting does not mean “ask optionally while escalating immediately.” An explicit request to speak with a person has its own handoff route. Do not assume that creating a scenario named “Customer requests a person” makes its required fields apply to that route or to every handoff. Test explicit requests separately from configured scenarios. For immediate escalation, do not add contact details as required prerequisites. Asking for optional contact details while preserving immediate escalation is not provided by the required-field setting. Prechat contact fields are a separate webchat setting that applies before the conversation, not only at handoff. Open Handoff Rules in your active workspace.

Copy-ready scenarios

Invoice request

Name: Invoice request

Trigger:
The customer asks the team to prepare an invoice for an existing purchase.
Do not trigger for a general question about whether invoices are available.

Required fields:
- Purchase reference

Urgent service or safety issue

Name: Urgent service or safety issue

Trigger:
Create a high-priority handoff when a customer reports an immediate safety concern, fire or smoke, an electrical hazard, loss of access to a paid service, or another issue requiring urgent staff attention.

Required fields:
- None; do not delay urgent escalation to collect contact details.

For urgent situations, pass along available details without making additional contact information a prerequisite.

Payment or charge dispute

Name: Payment or charge dispute

Trigger:
Create a handoff when a customer disputes a charge, reports being charged incorrectly, requests a refund that cannot be completed automatically, or reports a payment failure after retrying.

Required fields:
- Customer name
- Order, invoice, or transaction reference
- Customer email or phone
- Custom field: paymentIssueSummary

Choose required fields deliberately

Scenario	Useful fields
Explicit human request	Uses its own route; scenario fields are not a universal contact form
Order or appointment change	Customer name, relevant reference, requested date or change
Urgent service issue	Already available details; no contact prerequisites
Payment dispute	Customer name, invoice or transaction reference, contact method

Scope each scenario to the businesses where it applies. Do not request information already present in the conversation or a connected system unless it must be confirmed.

Configure working hours

Open the Working hours tab and enter the hours when a person can respond. The schedule uses the AI timezone configured in Personalization. Test the same handoff:

During working hours
Outside working hours
On a closed day

The agent should set accurate expectations without implying that the issue has already been resolved.

Test both sides of every rule

Should trigger	Should not trigger
“I need to speak to a manager.”	“What are your support hours?”
“There is smoke coming from an outlet.”	“Do you sell smoke detectors?”
“I was charged twice.”	“What payment methods do you accept?”
“Please change my confirmed appointment.”	“What appointment times are available?”

Testing non-triggers is essential. It reveals rules that are so broad they interrupt normal self-service.

Build an operational loop

Review handoffs in Home and the Handoff Conversations view.
Read the escalation reason, captured details, missing fields, and latest customer messages.
Assign a conversation owner so responsibility is explicit.
Complete the operational task and reply to the customer.
Add a short resolution note, then select Resolve handoff.
Identify false positives, missing context, or missing scenarios.
Update one rule at a time and retest it.

Write useful resolution notes

A resolution note should let another teammate understand the outcome without rereading the entire thread.

Verified order 4821 with the operations team. Corrected the delivery date to
14 August and confirmed the change with the customer on WhatsApp.

Avoid notes such as “done” or “handled.” Include the action, result, and any remaining owner or next step.

Use internal review for quality checks

Do not create a customer-facing handoff only because a conversation should be audited. Use Mark for review for:

Quality assurance and coaching
Policy or brand-standard checks
Reviewing an unusual AI answer
Confirming that an operator followed a process

Add a focused review note, such as:

Check whether the refund explanation matches our cancellation policy and add
coaching feedback if the response could be clearer.

The reviewer can be different from the conversation owner. Completing the review with Mark reviewed does not archive the conversation or change its response mode.

Review handoff performance regularly

Sample resolved handoffs every week and look for:

Rules that trigger on harmless questions
Missing fields that force operators to ask the customer again
Handoffs that remain open after the task is complete
Vague resolution notes
Requests that should become a new knowledge-base answer or automated action

Use what you learn to narrow triggers, remove unnecessary fields, and improve the operator runbook.

Handoff Rules reference

Review switches, fields, business scope, working hours, and the operator resolution flow.

Conversations operator guide

Learn assignment, internal review, needs-reply, archive, block, and handoff workflows.

Getting Started

General

Lana

CRM

Agent

Best Practices

Connections

Tools

Workspace

AI escalation and human handoff best practices

Start with a small rule set

Configure a scenario

Where handoff rules apply

Copy-ready scenarios

Invoice request

Urgent service or safety issue

Payment or charge dispute

Choose required fields deliberately

Configure working hours

Test both sides of every rule

Build an operational loop

Write useful resolution notes

Use internal review for quality checks

Review handoff performance regularly

Handoff Rules reference

Conversations operator guide

​Start with a small rule set

​Configure a scenario

​Where handoff rules apply

​Copy-ready scenarios

​Invoice request

​Urgent service or safety issue

​Payment or charge dispute

​Choose required fields deliberately

​Configure working hours

​Test both sides of every rule

​Build an operational loop

​Write useful resolution notes

​Use internal review for quality checks

​Review handoff performance regularly

Handoff Rules reference

Conversations operator guide

Start with a small rule set

Configure a scenario

Where handoff rules apply

Copy-ready scenarios

Invoice request

Urgent service or safety issue

Payment or charge dispute

Choose required fields deliberately

Configure working hours

Test both sides of every rule

Build an operational loop

Write useful resolution notes

Use internal review for quality checks

Review handoff performance regularly