Why do generic helpdesks struggle in restaurants?
Generic helpdesks assume the support team owns the fix. In a restaurant group the people who can fix it, the general manager, the chef and the events lead, are running service, and each problem belongs to one location and one shift.
- The location matters more than the customer. "My order was wrong" means nothing until you know which kitchen made it and when.
- Same-day messages can't wait. A 7 pm table or a bag on the pickup shelf can't wait for a next-business-day SLA.
- Dine-in, off-premises and catering share one inbox. Dine-in guests, off-premises orders and catering or event sales each need a different owner.
- Some orders aren't yours to refund. Delivery app orders are paid through the app, so staff need to see where an order came from before promising anything.
- Teams turn over fast. In the Bureau of Labor Statistics turnover figures for August 2026, accommodation and food services had the highest quits rate of any industry: 3.5% in the month, against 2.1% across the private sector. Put policy in templates and views so a new host can answer on their first shift.
How should a restaurant group set up its support inbox?
Create queues by who must act and how soon, then give each location its own view. This layout suits a group of three to fifteen locations.
| Queue | What lands there | SLA target (example) | Owner |
|---|---|---|---|
| Tonight | Same-day bookings, running-late messages, orders in progress or just collected | 10 minutes during service hours | Guest services lead on shift |
| Online orders | Problems with earlier orders, refund status, credits for a bad order | 4 business hours | Guest services team (round-robin) |
| Reservations | Future bookings, large parties, special occasions, accessibility requests | 1 business hour | Guest services team |
| Catering | New inquiries, quotes, headcount changes, invoices | First reply in 1 business hour; quote the same day | Catering sales manager |
| Private dining and events | Buyouts, room holds, minimum spends, deposits | Same business day | Events manager |
| Gift cards and loyalty | Balances, e-gift delivery, bonus card terms, missing points | 1 business day | Guest services team |
| Guest feedback | Complaints, compliments and comp requests after a visit | Reply the same day; GM contact within 1 business day | General manager of that location |
| Guest safety | Allergic reactions, illness reports, injuries, health department mentions | Manager contact within 1 hour, any time | Director of operations or food safety lead |
These SLA targets are starting points; tune them to your service hours.
Routing rules for day one
- Safety jumps the line. Workflow rules triggered by keywords move reaction, illness and injury messages into Guest safety from any channel, and a workflow posts an alert to the operations Slack channel.
- Tag the location on arrival. Give each location its own email address where you can, and fill a custom location field from the order or booking. Per-brand phone numbers keep each concept's calls apart.
- Route catering by size. A headcount or order-value field sends large inquiries to the catering manager and spreads smaller ones by round-robin (Growth and up).
- Side conversations in Slack to ask a kitchen manager whether an item went out.
- One view per general manager, plus a morning view of everything that arrived after close.
The Aftersales Inbox runs this setup across email, web chat, SMS, WhatsApp, phone and social DMs.
What reply templates should restaurant guest services use?
Write templates where a careless word loses a regular or creates liability, and have a manager send the first two. The CDC advises anyone who thinks food made them sick to report it to their local health department, so never word a reply to discourage that.
Allergic reaction reported after a meal
Hi {guest_name}, thank you for telling us, and I'm very sorry. {manager_name}, the general manager at {location}, is reviewing your visit on {visit_date} with the kitchen and will call you at {phone} by {time}. It would help to know which dishes your party ordered and which allergy you mentioned to your server. If anyone is still unwell, please put getting care first.
Illness report after dining
Hi {guest_name}, I'm sorry you've been unwell, and thank you for letting us know. Your message is now with {food_safety_lead}, who will contact you by {time}. Could you share your visit date, what you ordered and when you began to feel ill? If you report this to your local health department, we will cooperate fully.
Problem with a delivery app order
Hi {guest_name}, I'm sorry your {app_name} order from {location} arrived {issue}. Because you paid through {app_name}, the refund comes from them: {app_refund_steps}. Our {location} kitchen has the details so they can find out what happened.
No-show or late cancellation fee dispute
Hi {guest_name}, thanks for getting in touch about the {fee_amount} charge for your {booking_date} booking at {location}. Our policy, shown when you booked and in your confirmation, is {fee_rule}. I've checked the booking and {what_we_found}, so {outcome}. If something outside your control kept you away, tell us and {manager_name} will review it personally.
Private dining minimum spend explained
Hi {guest_name}, thank you for thinking of {location} for your {event_type} on {date}. {room_name} seats up to {capacity} and has a food and beverage minimum of {minimum} before tax and service, and everything your group orders counts toward it. A deposit of {deposit} holds the date, with the balance due {terms}. Could we set up a 15-minute call on {call_slot} to plan the menu?
How should a restaurant guest services team cover hours and peaks?
Staff the inbox for the hours before and during service rather than office hours, and plan the year around dining holidays, catering season and gift card season.
- Guest services agents take first touch on bookings, orders, gift cards and feedback.
- A shift lead owns the Tonight queue from mid-afternoon to the end of dinner service.
- Catering and events managers own their queues and quotes.
- General managers answer complaints for their location and approve comps on Lite seats, which let them view, comment, @mention and approve at no cost.
- The director of operations owns Guest safety and the weekly review.
Expect messages to build in late morning, peak in the afternoon with same-day booking changes, and shift to order problems once dinner pickups start. Hosts can't answer mid-rush, so route their phones and texts into Tonight.
Seasonal peaks
- Valentine's Day and Mother's Day: booking changes, waitlist requests and set-menu questions. For Mother's Day 2024, a National Restaurant Association survey found 43% of consumers planned to use restaurants to celebrate.
- May and June: graduation parties drive catering inquiries and large-party bookings.
- November and December: holiday party buyouts, gift card orders and e-gift delivery questions, then prepaid New Year's Eve dinners.
- January: gift card redemptions and questions about when bonus cards expire.
Where does AI help a restaurant guest services team?
Let AI do the typing and reading, and keep judgment calls with managers. Copilot works beside your agents; Agent takes the repeatable share before anyone sees it.
- Drafts that cite their sources. Copilot drafts replies from your allergen matrix, cancellation policy or catering menu and shows where each answer came from.
- Summaries of long catering and event threads before a manager calls the client.
- Translation for tourists booking a table or asking about a dish's ingredients before they travel.
- Agent resolves booking changes, fixes for orders placed on your own site and gift card balances. Its procedures and guardrails are in AI customer service for restaurants.
- Insights flags spikes, such as missing-item complaints from one location's dinner shift, and on Growth its Monitors score every conversation instead of a sample.
Each rep gets 10 Copilot and 10 translation conversations a month on every plan; the Copilot add-on is $29 per rep per month billed annually ($35 monthly).
Which customer service metrics should a restaurant group track?
Measure by location and by queue, because a group-wide average hides the kitchen that keeps missing items.
| Metric | Formula | Target guidance |
|---|---|---|
| Order issue rate | Order-problem conversations ÷ online orders × 100, per location | Compare each location with the others and with its own last month |
| Tonight response time | Median minutes from message to first reply in the Tonight queue | Agree a target with operations; review every miss tied to a booked table |
| Catering lead response time | Median minutes from inquiry to first human reply | Track daily during graduation and holiday seasons |
| Safety escalation time | Median minutes from a safety-tagged message to manager contact | Review every case with your food safety lead |
| Repeat contact rate | Guests who write again about the same issue within 7 days ÷ all guests who wrote × 100 | A rise points to unclear replies or slow refunds |
| CSAT by location | Positive survey responses ÷ total responses × 100, per location | Split dine-in from off-premises; read every comment on complaint threads |
| Comp and refund value per location | (Refunds + credits + comps) ÷ covers or online orders, per location | Compare locations monthly; a jump usually traces to one shift or menu item |
Base each target on your group's own history. No published benchmark fits every restaurant group.
How do you switch a restaurant group from its current tools?
Most groups answer guests from several places at once: an info@ mailbox, the phone at each host stand, the messaging inside the reservation platform, social DMs on a manager's phone and catering emails in a salesperson's own inbox. Keep your systems of record, move two-way conversations into one inbox, and switch one channel at a time.
Many reservation platforms send booking confirmations and reminders and offer guest messaging; those can stay there.
- List every inbound path, including each info@ and events@ address and every location's phone number.
- Link your reservation, ordering and point-of-sale systems so a host sees the booking or ticket beside each thread; we check your exact stack during the migration call.
- Move catering out of personal inboxes first, since a lead in someone's own mailbox disappears when that person leaves.
- Rebuild your macros from the templates above and retire the ones nobody trusts.
- Switch channels in order: email, web chat, SMS and social DMs, then phone.
- Leave old mailboxes read-only for two weeks.
Aftersales says most teams finish migrating in an afternoon, and on Growth and Scale its team runs the migration with you. Compare tools in best omnichannel customer service software or see pricing.