When AI Should Hand Off to a Human Dispatcher

The worst AI failure in field service is not a clumsy sentence. It is a polite loop that refuses to get a human while a homeowner's patience dies.

Handoff is the product. This playbook lists triggers, warm transfer patterns, and QA checks.

Hard handoff triggers

• Customer asks for a human
• Anger / threat language
• Payment or invoice dispute
• Safety emergency beyond script
• VIP / commercial SLA accounts
• Repeated misunderstanding after two turns
• AI uncertainty on price or ETA

Warm transfer standard

Pass name, issue, address if known, and why you are handing off. Never make the customer restart from zero.

Copy-paste scripts

Copy these, then edit bracketed fields so they sound like your shop.

Customer asks for human

Absolutely. I am connecting you to dispatch now and sharing your details.

Dispatcher whisper

Inbound handoff: {Name}, {Issue}, prefers human, sentiment {Tag}.

Callback instead of live

All humans are with callers. You are priority callback within {Minutes} minutes. Keeping this thread open.

Metrics worth tracking every week

Fifteen minutes every Monday. Same numbers. Same owners.

Metric	How to count it	Target
Handoff rate	Handed / AI calls	Healthy band, not minimized blindly
Ask-for-human fulfillment	Fulfilled / requested	100%
Restart complaints	Customer had to repeat all details	Near zero
Post-handoff CSAT proxy	Disposition quality	Track

Honest limitations: when a human must take over

Some shops over-handoff and waste AI. Others under-handoff and waste brand. QA the boundary monthly.

• Legal threats
• Discrimination allegations
• Medical emergencies
• Press / media callers

Implementation checklist

1. Write trigger list
2. Build warm transfer
3. Train barge-in
4. Review 20 handoffs
5. Tune prompts
6. Publish to team

Operator FAQ

Is asking for human a failure?

No. Honoring it is success.

Should AI apologize?

Briefly, then hand off. Do not grovel in a loop.

What if no human available?

Honest callback SLA beats fake hold music.

Petunia is designed for AI reception with dispatcher handoff, not endless containment. Features · Book.

Related pages: AI trust, Triage, Unified inbox.

Trigger engineering

Write triggers as observable events.

1. Phrase lists

Phrase lists. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Sentiment tags

Sentiment tags. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. Account flags

Account flags. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. Two-turn confusion rule

Two-turn confusion rule. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Versioned trigger docs

Versioned trigger docs. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

Warm context packets

Dispatchers need a 10-second brief.

1. Name

Name. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Issue

Issue. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. Address

Address. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. Sentiment

Sentiment. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Already promised

Already promised. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

QA that rewards good handoffs

Do not punish containment misses when handoff was right.

1. Scorecard

Scorecard. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

2. Celebrate saves

Celebrate saves. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

3. Fix late handoffs

Fix late handoffs. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

4. Coach overconfident bots

Coach overconfident bots. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.

5. Monthly boundary review

Monthly boundary review. Write the current reality in one blunt sentence. Teams improve what they can say without defensiveness. If the sentence is embarrassing, good. That means you found the real starting line.

Assign a single owner and a named backup. Dual ownership sounds mature and usually means mutual diffusion. The owner runs the weekly number. The backup covers PTO. Everyone else supports without rewriting the rule mid-call.

Define the first five minutes: who answers, what they say, where it is logged, and what the customer should expect next. Fuzzy first minutes beat fancy strategy every time. Put those four answers on a one-page card next to the phones.

Instrument one leading indicator and one lagging indicator. Leading might be speed or response rate. Lagging might be booked jobs or star rating. Review both every Monday for four weeks before you declare victory or buy another tool.

Rehearse under noise. Play a second line ringing. Interrupt with a parts question. If the process only works in a quiet room, it does not work on a dispatch floor during a heat wave or a freeze snap.

Publish what you will not do. Constraints create speed: no invented ETAs, no invoice fights over SMS at midnight, no silent on-call ignores. Clear nos protect customers and staff at the same time.

When the step fails in the wild, log the failure in one line the same day. Patterns in those lines become next week's coaching. Waiting for a quarterly meeting to discuss phone mistakes is how the same miss repeats fifty times.