When the drive-thru AI should hand the lane back to staff | Maple Blog

When the drive-thru AI should hand the lane back to staff

By Maple Team · Published

When a drive-thru AI should pass one order to the crew, when to switch the whole lane off, what vendors describe, and a fallback plan to copy.

A drive-thru AI should pass an order to a person as soon as the guest asks for one, when it still cannot understand after asking twice, and when the order falls outside what you have set it up to handle. Switch the whole lane back to staff when the network, POS or AI is failing, or when nobody is free to answer its alerts. Write these rules down before launch.

Our one-lane pilot worksheet tests the takeover once, before the trial. This page is the plan your shift leads use every day after that: what triggers a hand-off, who acts, what the guest hears, and how the lane goes back to normal.

How do vendors describe the hand-off?

Each row comes from the vendor's own manual or web page. We have not tested these controls.

VendorWho steps inWhat triggers it, in the vendor's words
HME (NEXEO headsets)A crew member presses the lane button on a headsetThe bot sends an escalation when it cannot understand what the guest wants, or the guest's language is not supported; automated order taking is off by default and only an installer can turn it on
PrestoRemote agents, in three of its four modesModes range from Pure AI with no agents, to agents pulled in when issues emerge, to constant oversight, to agent-led ordering
Hi AutoTrained remote agentsWhen the AI lacks confidence or cannot fully understand the order; every intervention is logged
SoundHoundThe crewCrew members stay looped in to support only when it is truly needed
MapleThe crewGuests can ask for a person at any time; a one-press kill switch puts the lane back to normal with no AI in the loop

Sources: HME's NEXEO user's guide and NEXEO Pro page, Presto Voice, Hi Auto's FAQ, SoundHound's drive-thru page and Maple's drive-thru page.

The table mixes two kinds of fallback: remote agents at the vendor, whom your crew may not hear, and your own crew on the headset. Our guide to remote drive-thru order taking compares the two. This page assumes your crew is the fallback.

When should one order go to a person?

One outside count comes from the 2025 QSR Drive-Thru Report. In 120 mystery-shop orders at AI drive-thrus of three brands, 21% began with the AI and were transferred to an employee, because the AI could not answer a question, could not follow a customization, or an item was out of stock. The transferred orders were 95% accurate, against 81% for orders the AI took alone. Our AI drive-thru accuracy guide explains what those figures count.

Set your own per-order triggers. These are ours to start from:

  1. The guest asks for a person, in any words. Hand over at once; the AI should not try to finish the order first.
  2. Two failed tries. If the AI has asked the guest to repeat twice and still has it wrong, a person takes over.
  3. Unusual size. A quantity far above a normal car's order. At a Taco Bell in 2025, a guest ordered 18,000 water cups for a social video before an employee took over, Nation's Restaurant News reported in September 2025.
  4. Allergies and health questions. Send any question about ingredients or allergens to a trained crew member.
  5. Complaints. A problem with an earlier order, a refund or an upset guest.
  6. Anything the menu setup does not cover: a coupon the AI cannot apply, an item from another chain, a long silence.

Some guests will not talk to a bot at all. In September 2026, Burger King said its pilot restaurants saw drive-offs from guests who did not want to, and that it is building a way for guests to choose how they order, Restaurant Business reported. The same story cited Technomic data: 23% of consumers find ordering from an AI drive-thru bot appealing and 46% find it unappealing. Say in the greeting how to reach a person.

When should the whole lane go back to staff?

Turning the lane off stops the AI for every car until someone turns it back on. Pick the conditions ahead of time so a shift lead does not have to decide in the middle of a rush.

ConditionWhat to do
Internet or the AI system is downLane off; crew takes orders on the headset
POS down or tickets not arriving in the kitchenLane off; follow your normal POS outage steps
Hand-offs keep coming, for example three in fifteen minutesLane off; note the orders and tell the vendor
A menu change or promotion has not reached the AILane off until the vendor confirms the update
Nobody free to answer alerts, such as one person short at the rushLane off, or keep a lead on the headset
Wind, rain or a fault at the speaker post making guests hard to hearLane off; check the post before turning it back on
Prank or abusive orders repeatingLane off for the rest of the daypart

The "three in fifteen minutes" figure is an example. Choose your own number from the first weeks of the trial. Taco Bell's technology chief told the Wall Street Journal the chain was weighing where to use its system, and Nation's Restaurant News noted that busier restaurants may benefit more from a person taking orders. The rush is a fair time to ask whether the AI should run at all.

Ask what happens to the audio itself if the base station fails. HME's NEXEO installation guide lists an optional connection to a backup intercom such as its IC300.

What should the written fallback plan say?

Copy this, fill in the blanks with your vendor and shift leads, and keep it by the headset base station.

  1. Lane owner by shift: the person who listens for alerts and takes over. Opening ____, mid ____, close ____.
  2. Takeover control: what the crew presses to take one order, and where it is. ____.
  3. Lane-off control: what switches the whole lane off, where it is, and who may use it. ____.
  4. Per-order triggers: the list above, edited for your menu. ____.
  5. Lane-off conditions: the table above, with your own numbers. ____.
  6. What the guest hears during a hand-off, word for word. ____. Our drive-thru script guide has example wording.
  7. Half-built orders: whether items the AI already took stay on the check or must be keyed again. ____.
  8. Outage steps: who calls the vendor, the support number, and how the crew takes orders meanwhile. ____.
  9. Turning it back on: who decides, and one staff test order checked on the kitchen screen first. ____.
  10. Log: time off, time on, reason and name, reviewed each week with the vendor. ____.

How do you keep the crew ready?

Practice the takeover at the start of each shift for the first weeks: one staff car, one hand-off, one lane-off and back on. Repeat it when a new crew member joins. A control nobody has pressed in a month is slow to find when a guest is waiting.

Review the log weekly. If one trigger fires far more than the others, fix its cause with the vendor, such as a menu item, a noisy post or a missing word, before adding more hours of AI.

How does Maple handle it?

Maple's drive-thru unit stands beside the existing speaker post, so the headsets keep working. Its page says guests can ask for a person at any time and a one-press kill switch returns the lane to normal with no AI in the loop. It is in early access with a small number of restaurants and priced per unit, with no public price. Ask for the fallback plan above to be filled in during setup.

Published by Maple. This AI-assisted guide combines vendors' manuals and web pages, a trade study, reporting from Nation's Restaurant News and Restaurant Business, and Maple's published drive-thru scope with an original trigger list, lane-off table and fallback plan. The example thresholds are our suggestions and were not measured, and the guide does not report a test of any vendor's takeover control.