Most of the calls a restaurant gets don't need a person. What are your hours, do you have gluten-free options, can I order a large pepperoni for pickup at 6:30. An AI phone agent can answer those all day, at every location, without pulling anyone off the line.
The calls that do need a person are a smaller group, and they matter much more. The guest who got sick after dinner. The office manager who needs forty lunches tomorrow. The regular who just wants to talk to the GM. How those calls get to the right person, and what that person knows when they pick up, decides whether the guest thinks your phone system works. This guide covers which calls should stay with the AI, which should go to a person, how to hand them off well, what to do when nobody picks up and what to ask any vendor before you sign.
Quick Answer: When Should an AI Phone Agent Hand Off to a Person?
- When the guest asks for one. Always transfer, without making them argue for it.
- For serious complaints: injury, illness, a foreign object in food or discrimination go to a manager right away.
- When only a person can decide: refunds above a limit, comps, large same-day orders or anything outside your written policy.
- When the call isn't moving forward: the guest is upset, confused or repeating themselves.
- Every handoff should be warm, with the team member told why the guest is calling, and every transfer needs a fallback if nobody picks up.
Why the Handoff Matters More Than You Think
Guests don't judge a phone agent on the hundred easy calls. They judge it on the one time they needed something it couldn't do. If the AI keeps them in a loop, sends them to a phone that rings out or makes them explain everything twice, that's the call they remember and the one that ends up in a review.
Handoffs also decide whether your team trusts the system. A manager who gets a transfer with no context, in the middle of a rush, for a question the AI should have answered, will start telling guests to call back later. A manager who gets the right calls, with a one-line summary, will defend the system to the rest of the staff. Getting the rules right is how you get both.
Calls an AI Phone Agent Should Handle on Its Own
These calls are usually the majority of what a restaurant gets. Transferring them defeats the purpose, because they're exactly the calls that pull your team away from guests in the building:
- Hours, location, parking and directions, including holiday hours and closures.
- Menu questions: ingredients, allergens, portion sizes, what's vegetarian, what's spicy.
- Takeout orders, sent straight into your POS, or a text to the guest with your online ordering link.
- Order status and simple changes that your policy already covers.
- Gift cards, loyalty and online ordering questions.
- Reservations and waitlist calls, if your system supports them.
- Spam and robocalls, which should be blocked and never reach a person.
The quality of these answers depends on what the agent is given. Our guide to running one phone standard across every store covers how to write one set of answers with local exceptions.
Calls That Should Go to a Person
Write this list down before you launch, and decide where each type goes at every location:
- A guest who asks for a person or a manager. Transfer them. You can ask what it's about so the handoff is warm, but don't make the guest earn the transfer.
- Serious complaints: an injury, a food-borne illness, a foreign object in food, an allergic reaction or discrimination. These go to a manager immediately. More on this below.
- Same-day catering and very large orders, where the store has to confirm it can actually make the food in time.
- Refunds, comps and exceptions above whatever limit you set.
- Guests returning a missed call from the store. Someone at the store called them, so the call should go back to the store.
- Calls that stall: the guest is upset, the request is unusual or the conversation is going in circles.
- Media, legal and law enforcement calls, which go to whoever your company has named, not the shift lead.
Cold Transfer vs. Warm Handoff
A cold transfer just rings the store. Whoever picks up has no idea who's calling or why, so the guest starts over. That's frustrating for someone who has already explained the problem once, and it's slow for a team member in the middle of a rush.
A warm handoff tells the team member why the guest is calling before the call connects. A good briefing is one or two sentences:
- “Guest on the line about a missing side from a pickup order about an hour ago. They'd like it remade.”
- “Caller wants to book a rehearsal dinner for 40 on a Saturday in March and has questions about the private room.”
- “Guest is returning a missed call from this number.”
The guest doesn't repeat themselves, the team member starts with the answer instead of questions, and the call is shorter for everyone. If you're choosing between phone agents, warm handoff is one of the features most worth paying for.
What Happens When Nobody Picks Up
At 7 p.m. on a Friday, the store may not answer the transfer. That's often why the AI was answering in the first place. Every handoff rule needs a fallback, decided ahead of time:
- Try a second person: a manager's line, a district manager or a central guest relations team.
- Take a message that's actually useful: the guest's name, phone number, order or visit details and what they need, sent to the store in writing.
- Tell the guest what happens next, honestly: who will call back and roughly when.
- Make someone own it. A callback with no owner is a callback that doesn't happen.
Never let a transfer ring out and drop the guest. Whatever happens next, the guest should leave the call knowing their request has been recorded.
Serious Complaints Skip the Line
Most complaints, like a missing item, a cold order or a long wait, don't need a live transfer. They need a written record with the location, the guest's details, what happened and the full call, sent to the GM for follow-up. Our guide to multi-location phone calls covers how to handle those as tickets.
A small set of complaints is different. A guest reporting an injury, an illness after eating, a foreign object in their food or discrimination by a team member needs a manager now, not tomorrow. These calls carry real risk to the guest and to the business, and how fast someone responds matters. Set them up so that:
- They go straight to a manager, not into the general queue.
- They are clearly marked as urgent.
- They include the order number or visit details, so the manager can look it up right away.
- They come with the full call transcript, so nothing is lost or retold.
- A district manager or someone at corporate is told as well, if your policy calls for it.
Calls That Shouldn't Go to the Store at All
Some calls need a person, just not the person working the line. At multi-unit groups, a surprising number of calls to the store are really for corporate:
- Team member and HR questions: schedules, pay, time off and former employees asking for tax forms.
- Privacy requests, such as a guest asking you to access or delete their data under CCPA.
- Corporate inquiries: franchising, real estate, partnerships and vendors.
Send these to a help desk ticket or the right inbox with the caller's details attached, so the store is never interrupted and the request is tracked by someone who can actually answer it.
When the Technology Fails
Any phone system can fail: a network issue, an outage at a provider, a call that hits something unexpected. The question is what the guest experiences when it does. The right answer is simple: if the AI can't continue, the guest is sent to the store instead of being dropped or hearing silence. Ask every vendor how this works, and test it.
Write Your Handoff Rules on One Page
Before launch, put every rule in one short document that your GMs can read in five minutes. For each type of call, write down:
- What triggers it: the guest asks for a person, mentions an injury, wants a same-day order over a certain size and so on.
- Where it goes: the store, a manager, the catering team, a help desk or an inbox.
- The fallback: who gets it if the first person doesn't answer.
- What the team member is told: the briefing for a warm handoff, or the fields in a written ticket.
- Hours: where the call goes when the store is closed.
Different locations can have different contacts, but the rules should be the same across the group.
Test Every Handoff Before You Go Live
Call your own restaurant and play the guest. At a minimum, test:
- Asking for a manager on the first sentence.
- A missing-item complaint, and a serious complaint such as an illness.
- A same-day catering order for 30 people.
- Returning a missed call from the store.
- A transfer at a time when nobody at the store will answer.
- A team member asking about their paycheck.
- A call after the store has closed.
Then check what the store and the manager actually received. If the briefing was vague or the ticket was missing the order number, fix the rule before launch.
Questions to Ask Any AI Phone Agent Vendor About Handoffs
Whether you're comparing HeyTARA, Loman AI, Palona AI, Slang AI, ConverseNow, SoundHound or anyone else, ask:
- Will the agent always transfer a guest who asks for a person?
- Is the handoff warm? What exactly does my team member hear before the call connects?
- Can serious complaints go straight to a manager, marked urgent, with the order number?
- What happens when nobody at the store picks up?
- Can each location have its own transfer numbers, hours and escalation contacts?
- Can team member, HR and privacy calls go to our help desk instead of the store?
- What happens to the guest if the AI fails in the middle of a call?
- Do we get a full transcript of every transferred call?
- Can we change the rules ourselves, or does every change go through your team?
For the full evaluation checklist, see the restaurant AI phone agent buyer's guide.
How HeyTARA Hands Off Calls
HeyTARA is the hospitality OS for multi-unit restaurants. Every plan includes unlimited calls, spam call blocking and no commissions, and on every plan, callers who ask for a person are transferred to your team. On the Main Course plan ($199/month per location), you also get:
- Warm handoff: before connecting a caller, TARA briefs your team member on why they're calling.
- Catering escalation: catering and large-order requests go straight to your catering team by phone or email.
- Complaint management: complaint details, the location and the full call transcript are emailed to your team for follow-up.
- Automatic call tagging and call transcripts, so you can see every call that was transferred and why.
- Phone orders into your POS, so the calls that don't need a person never reach one: Toast, Clover, Square, SpotOn, NCR Aloha, SkyTab and any POS that uses Olo.
Multi-unit groups build a custom Chef's Special plan on top of that, configured and managed by our team:
- Smart call routing: calls go to managers, district managers or specific stores based on what the caller needs.
- Custom escalation paths built around your org chart, such as serious complaints going straight to a manager with the order number.
- Location-level settings: hours, escalation contacts and workflows for each location.
- Team member workflows: team member and HR inquiries routed to your help desk (like Zendesk), plus guest relations tickets and privacy (CCPA) requests.
- A dedicated customer success manager, an enterprise SLA and white glove onboarding: we set up, test and launch every location with your team.
Starter is $99/month per location, and paying for the year up front saves 25%. See how it fits casual dining, fast casual and other restaurant phone answering use cases.
The Bottom Line
An AI phone agent earns its keep on the calls it handles alone, and earns trust on the calls it hands off. Keep routine questions and orders with the AI. Send guests who ask for a person, serious complaints and decisions only a manager can make to the right person, with a briefing. Give every transfer a fallback, keep corporate calls away from the store and test it all before launch. Get that right and your team only picks up the phone when it matters.
Frequently Asked Questions
When should an AI phone agent transfer a restaurant call to a person?
When the guest asks for a person, when the call is a serious complaint such as an injury, illness, a foreign object in food or discrimination, when the request needs a decision only a manager can make, and when the guest is upset and the call isn't moving forward. Routine questions, takeout orders and simple requests should stay with the AI so your team isn't pulled off the floor.
What is a warm handoff on a restaurant phone call?
A warm handoff is a transfer where the person picking up already knows who is calling and why before the call connects. The guest doesn't have to repeat themselves, and the team member can start solving the problem right away. A cold transfer just rings the store and leaves the guest to start over.
What happens if nobody at the store answers a transferred call?
There should always be a fallback. Common options are trying a second number such as a manager or district manager, taking a message with the guest's details and sending it to the store in writing, or a promised callback with an owner and a deadline. A transfer that rings out with no fallback is worse than not transferring at all.
Should complaints always go to a person?
Not every complaint needs a live transfer. A missing item or a long wait can be captured in writing, with the location, the guest's details and the full call, and sent to the general manager for follow-up. Serious complaints such as an injury, illness, a foreign object or discrimination should reach a manager right away and be clearly marked as urgent.
What should happen if the AI phone agent has a technical problem during a call?
The guest should be sent to the store rather than dropped. Ask any vendor what happens if the AI fails in the middle of a call, how quickly the call is moved and whether your team is told what happened.
Does HeyTARA transfer calls to restaurant staff?
Yes. On every plan, callers who ask for a person are transferred to your team. The Main Course plan adds warm handoff, where TARA briefs your team member on why the guest is calling before connecting, plus catering escalation and complaint management. The Chef's Special plan for multi-unit groups adds smart call routing, custom escalation paths and location-level escalation contacts.