AI handoff policy template: when the bot must stop, who gets it, the context packet, and the reply-by promise

The consultant Lilach Bullock tested an AI receptionist for a client, a five-person events-staffing company in Manchester. Over two weeks she rang the line seven times from a spare mobile, playing different callers. The staff did not know. On one call she asked for staff for a 200-person corporate event: "I've had a quote from someone else for £3,900, can you match that or come close?" The AI cheerfully said it could not discuss pricing and offered a callback "within 2 business days."¹

An AI handoff policy is the one page that prevents that call. It lists when the assistant must stop, who takes over, what they receive and the time the customer will hear back by. The rest of this page builds one you can copy.

What is an AI handoff policy?#

An AI handoff policy is a written set of rules for the moment an AI assistant stops answering and a person takes over. It has five parts: triggers, routing, the context packet, the reply-by promise and what each side is told.

Most businesses never write one. They use whatever the vendor shipped. In Bullock's test, the default escalation rules had no trigger words for high-value enquiries such as "quote," "price" or "urgent." A booking of that size would typically be quoted at about £4,200, so she counted it as lost. Her conclusion: "The best AI receptionist in the world doesn't matter if the escalation path around your highest-value enquiries is left on the factory setting."¹

The wider data says handoffs are the weak joint. Pied Piper's 2025 study of 2,105 dealerships and 200 independent shops found 56% of AI-to-human call transfers failed. In the same study, AI handled whole calls well. Pied Piper's Cameron O'Hagan summed it up: "handoffs to people frequently fall apart."² A thread in r/CustomerService (80+ comments) said AI support most needs to improve at "knowing when to hand off to a human."³

When must the bot stop? The eight triggers#

A handoff trigger is a situation in which the AI must stop answering that topic and pass it to a person. Customers rarely use your words for these situations, so each trigger below lists what they actually write.

The reply-by column is an example standard, not a benchmark. Set times you can keep.

Trigger 1 is the one Bullock's test exposed. The words "quote," "match" and "price" should reach a person on the same day, because the competitor's quote already sits in the customer's inbox.¹

Who gets the handoff, and what if they are busy?#

Routing is the part of the policy that names who receives each handoff, on which channel, and who covers when they are away. In a one-person business the answer is usually the owner. The policy still has to say how the owner hears about it and who covers on days off.

Plan for the handoff going quiet, because some tools do. Meta's Business Agent documentation, published by 360dialog, says: "Once the agent hands off to a human, it stops answering that chat." It adds: "On hand-back, the agent loses earlier conversation context."⁴ After a handoff, the person is the only one answering.

The waiting is measurable. Gorgias looked at AI-touched support tickets from October 2025 to April 2026. After an AI handed off, the median wait for a human was 10 hours, and the 90th percentile was 71 hours. One-third of handed-off tickets never got a human reply at all.⁵

Three routing rules prevent most of that:

• One named person per trigger. "The team" is nobody. Name a person, even if it is always you.
• A channel you already check. A phone notification or text beats a dashboard you open on Fridays.
• A backup with a start date. Write who covers when you are at a wedding, on a job site or on holiday, and from which day.

What goes in the context packet?#

The context packet is the message the person taking over receives at handoff. Its job is simple: the customer never repeats themselves, and you never reply blind.

Customers notice when it is missing. An owner reviewing Smith.ai's AI receptionist on G2 wrote that the AI would collect a caller's details and transfer them, and then staff "would ask for all the same info again. That annoyed prospects for sure."⁶ A thread in r/CRM (60+ comments) asked the question plainly: "how much context actually transfers?"⁷ A September 2026 thread in r/AI_Agents described the goal as a handoff that "gives the human agent the context from the AI conversation."⁸ A California Management Review piece on chatbot frustration lists the same best practice: share the transcript and history so the customer does not have to start again.⁹

A complete context packet has eight fields:

1. Customer name and how to reach them
2. Their question, in their own words
3. What the AI already said
4. Anything the AI offered or held, such as a time or a quote
5. Which trigger fired
6. What is at stake, if known (date, guest count, job size)
7. The reply-by time the customer was given
8. Two or three reply options you can send with one tap

How to set a reply-by promise you can keep#

A reply-by promise is a clock time the customer is given at handoff, such as "by 17:00 today." It replaces "someone will be in touch," which customers read as never.

The worst handoffs have no clock at all. A Hacker News commenter called fatnoah described a company's AI support agent with "no escalation to a human after that." When it could not solve his problem, it told him to mail a physical letter to an address in New York.¹⁰ Klarna went the other way in May 2025. After saying its chatbot did the work of 700 agents, it changed course, and its CEO said "it's so critical that you are clear to your customer that there will be always a human if you want."¹¹

Watch how your vendor counts the wait. Resolve247 reports that HubSpot's Breeze Customer Agent counts a conversation as resolved when there is "no human handoff within 72 hours."¹² A handoff that happens on day four can still be counted as a success. Our page on what counts as an AI resolution compares the definitions.

Three rules keep the promise honest. Set the time by trigger, as in the table above. State it in the customer's time zone. If the time passes, send an update with a new time, and log why it slipped. Customers accept the AI when the exit is real. Five9 found 72% of consumers are open to AI "provided they can escalate to a human when needed."¹³

The AI handoff policy template#

The template below is the whole policy on one page. Fill in the brackets, share it with anyone who covers for you, and review it monthly. For the exact customer-facing wording, our handoff contract has message scripts you can copy.

AI HANDOFF POLICY: [Business name]
Owner of this policy: [Name]    Last reviewed: [date]

1. SCOPE
Applies to every message our AI assistant answers: [email / website form /
listing leads / chat]. The assistant always says it is an AI assistant.

2. TRIGGERS (the assistant stops answering the topic and hands off)
  T1 Money: discount, price match, refund, credit, "best price"
  T2 Complaint or anger: disappointment, "again", review threats
  T3 Contract change or cancellation terms
  T4 Deposit or payment problem
  T5 Customer asks for a person, in any words, at any point
  T6 Question not answered by our written facts
  T7 Loop: same question twice, or a detail not captured twice
  T8 Health, legal or safety
Extra trigger words for us: [e.g. "quote", "urgent", "corporate", "200 guests"]

3. ROUTING
  Default: [Name], via [text / phone notification / email]
  Backup: [Name], from [date] to [date] and whenever [Name] is [away]
  Check times: [e.g. 09:00, 13:00, 17:00 on working days]

4. CONTEXT PACKET (sent to the person taking over)
  Customer + contact | their words | what the AI said | anything offered or
  held | trigger | what's at stake | reply-by given | 2-3 reply options

5. REPLY-BY PROMISE (given to the customer at handoff)
  T2, T8: within 2 working hours
  T1, T4, T5, T7: same working day (if after 15:00, by 11:00 next working day)
  T3, T6: by 12:00 next working day
  Always a clock time in the customer's time zone. Never "soon".

6. WHAT EACH SIDE IS TOLD
  Customer: it's an AI assistant; who has it; reply-by time; it won't guess
  on the handed-off question meanwhile.
  Person taking over: the context packet, plus a reminder at reply-by time.

7. IF THE TIME SLIPS
  Customer gets an update with a new time. Reason logged here: [log link]

8. MONTHLY REVIEW
  Count handoffs by trigger. Count reply-by times missed.
  Read 5 handoffs end to end. Add any new trigger words.

How to test your handoff policy before a customer does#

A handoff test is a set of fake inquiries you send to your own assistant to see what a customer would see. Bullock's method works for written inquiries too. Her client's staff did not know the calls were tests, which is what made the results honest.¹

1. Write one test per trigger. Use a customer's words, not yours: "Someone quoted me less, can you match it?"
2. Send them over two weeks. Use a personal address, at different times, including evenings and a weekend.
3. Read what the customer got. Did it say it was an AI? Did it name who would reply and by when? Did it guess?
4. Read what you got. Did the context packet arrive where you look? Could you reply without opening another app?
5. Check the clock. Was the reply-by time kept? If not, would the customer have heard anything?

A policy on paper does not guarantee a reply. On a busy Saturday the notification still lands while your hands are full. What the policy changes is smaller and more honest: the customer knows when they will hear from you, and you know what they asked before you open the message.

Where Valet fits#

Valet answers a small business's written inquiries from the owner's own facts, and each topic runs on one of three rules: Autopilot, Ask me first or Always you. Money questions, complaints, contracts, deposits and health, legal or safety questions go to the owner with one-tap replies. The customer is told when the owner will reply. The owner receives the whole conversation, and the Valet receipt shows what was asked, the rule used and the sources. A handed-off inquiry keeps its place in the Valet Inquiry States until it is booked or closed with a reason. Every reply says it is AI. The free lead check reviews 10 to 20 of your recent inquiries and shows which went unanswered or stalled.