Human Handoff for AI Chatbots: A Local Business Playbook

AI chatbot human handoff works when it has five parts: a clear trigger, the customer's consent and preferred channel, a structured summary of context, a destination someone on the team actually checks, and an honest expectation based on real business hours. Then measure whether a person followed up, not just whether a notification was sent.

"Someone will contact you soon" is not a handoff#

It is an unmeasurable promise. The customer does not know who, when or how. The team does not know the request exists unless somebody happens to check the right inbox. Handoff is the point where a chatbot either earns trust or quietly loses the enquiry.

Our guide from website question to human follow-up walks through a single workflow end to end. This playbook focuses on the handoff itself: the five parts, the wording and how to tell whether it is working.

Part 1: the trigger#

Decide in advance what moves a conversation to a person. Common triggers:

• The customer asks for a person.
• The assistant cannot answer from approved information.
• A safety topic comes up.
• A complaint.
• A high-value opportunity, such as a commercial job or a large project.
• A decision the assistant is not allowed to make, such as a discount, an exception or a confirmed arrival time.

Write the triggers down and test each one. A trigger that never fires in testing will not fire in production.

Part 2: consent and channel#

Ask the visitor how they want to be contacted and collect only what that channel needs. Someone who wants a text does not need to give an email address. Someone who asks for a call back should be asked when suits them.

Part 3: context#

The person picking up the enquiry should not have to read 40 messages to understand it. Whether your team writes it or your tools produce it, aim for a predictable format:

• Intent: what the customer wants.
• Location.
• Urgency.
• Key facts the customer stated.
• The unanswered question, if there is one.
• Preferred next step.

Keep what the customer said separate from any interpretation by the assistant. "Customer says there is no hot water" is a fact; "probably a failed element" is a guess, and it should be labelled as one or left out.

Part 4: destination#

Send handoffs somewhere the team already checks: a shared inbox, a phone, a dashboard. A new tool that nobody opens is a dead end. If more than one person can respond, decide who owns a handoff and how others can see it is already taken.

Part 5: expectation#

Set expectations by business hours, and use wording the business can keep:

• During staffed hours: "The team normally reviews new website enquiries during business hours."
• After hours: "Your details have been recorded for the team to review when we reopen."

Only use a specific promise such as "within two hours" if the business consistently meets it. An honest, general expectation beats a specific one that is broken.

Give staff a path back to the conversation#

The customer should not have to repeat everything when a person makes contact. Staff need one click from the notification to the full conversation, and they should open it before calling.

Measure completion, not creation#

A notification that nobody sees is not a successful handoff. Each week, review:

• Handoffs that did not reach anyone, such as failed alerts or a wrong address.
• Handoffs nobody picked up.
• How long the customer waited for a person.
• Handoffs that should have happened but did not.

The useful metric is "handoffs a person completed", not "handoffs created".

Handoff checklist#

• Triggers written down and tested.
• Customer asked for their preferred channel.
• Context format agreed, with facts separated from interpretation.
• One destination per handoff type, with an owner.
• Expectation wording matched to real hours.
• Weekly review of failed, unclaimed and slow handoffs.

How handoff works in Pivra#

On Starter and above, Pivra's human handoff lets a visitor ask for a person from the chat. The AI stops responding and saves the visitor's messages, the request appears in Dashboard → Conversations → Handoff, and a team member claims it and replies in real time. You can choose to offer a person only when needed, which is the default, or always show the option, and you can add trigger keywords. If nobody claims the conversation within the response timeout (180 seconds by default), the visitor sees your "team busy" message and can leave a phone number, which is saved as a lead. See human handoff.

When a person should step in, Pivra can alert your team by email or SMS. A handoff request can trigger an email or webhook action, and SMS lead alerts text a verified mobile with the lead's name and phone number. Leads, with a link to the conversation, are listed under Leads in the dashboard; see lead capture. Through integrations, leads can also go to tools such as ServiceM8.

Handoff is about bringing in a person when one is needed, not replacing that person.

Next step: replace "soon" with a handoff your team can own, and add the weekly completion review to someone's calendar.