When to hand off to a human, and how to decide

Every conversation with an assistant has a moment where continuing costs more than escalating. Finding that moment reliably is the difference between a tool that helps and one that traps people in a loop.

The mistake is treating it as a judgement call. Judgement made fresh each time is inconsistent and impossible to audit. Written rules can be tested and improved.

The five rules worth writing down

1. Two failed attempts

If the assistant has given two answers and the visitor has rephrased twice, escalate. The third attempt rarely succeeds and each one costs patience. This single rule catches most bad experiences.

2. Explicit request

If someone asks for a human, they get one immediately. No qualification step, no "let me try to help first". Resisting an explicit request is the fastest way to make someone hostile, and it is a pattern people recognise and resent.

3. Detected frustration

Short, repeated or capitalised messages, or profanity, indicate the conversation has gone wrong. Escalate rather than trying to recover it. This does not need a sentiment model to work at a basic level; message length collapsing and repetition are simple signals.

4. Outside the knowledge boundary

If the question concerns something the assistant has no source for, such as account specific data, a legal question, or anything requiring a commitment, escalate instead of approximating. This is a design decision, not a fallback.

5. Commercial signal

A question that indicates a serious evaluation, such as asking about contract terms, security review or team pricing, is worth a person even if the assistant could answer. This is the one rule where the goal is not deflection.

The tension to be honest about

Rule five conflicts with how these tools are usually sold. Deflection rate is the headline metric, and escalating a good lead lowers it. That is a sign the metric is wrong rather than the behaviour.

On a marketing site, a conversation that reaches a salesperson is often the best possible outcome. Measuring success by how many people you avoided talking to gets this exactly backwards.

When nobody is available

Handoff needs a defined behaviour outside working hours, and "the message disappears" is not one. The options are collecting contact details with a stated response time, offering an alternative channel, or being explicit that the team is offline and when they return.

Say the actual expected time. "We will get back to you soon" is worth less than "we reply within one working day", and if you cannot commit to a number, say that instead of implying one.

Auditing the rules

Once a month, read ten escalated conversations and ten that were not escalated but ran long. The second group is where the rules are failing. If you find conversations that should have escalated and did not, tighten the rule that should have caught them rather than adding a new one.