Key takeaways
- Guests contact restaurants on every channel, and the phone remains the most common way to book[1].
- A single inbox works only with clear rules: who owns each request type, how fast it is answered and when it escalates.
- Treat a phone call as a message too: log a summary so the next person can follow up without calling back blind.
- Speed matters: 94% of consumers say speed is critical when ordering off-premises[2].
Messages are everywhere, and nobody owns them
A typical independent restaurant hears from guests through the phone, voicemail, texts to the restaurant line, Instagram and Facebook messages, Google Business Profile messages and questions, the website contact form, email and the reservation platform's own messaging. Each channel lives in a different app, often on a different person's phone. The result is familiar: a catering inquiry sits unread in Instagram for a week, a guest's voicemail about a severe allergy is heard after their booking, and two staff members reply to the same email with different answers.
Guests do not see channels; they see a restaurant that either answers or does not. Nearly every adult carries a phone, with 98% of US adults owning a cellphone of some kind[3], and diners have long said it is hard to reach a restaurant when they need to change a reservation[4]. One inbox will not answer messages for you, but it makes sure every message is seen, owned and closed.
Map your channels first
| Channel | Typical requests | Who answers today | Target first reply |
|---|---|---|---|
| Phone calls | Bookings, takeout, hours, directions, complaints | Host, bartender, whoever is near | Live during open hours; callback within the hour |
| Voicemail | After-hours bookings, catering, lost property | Manager next morning | By late morning next day |
| Texts to the restaurant line | Running late, changes, quick questions | Often nobody | Within 15 minutes during service |
| Instagram and Facebook DMs | Events, menus, collaboration requests, complaints | Owner or social manager | Same day |
| Google Business Profile | Questions, messages, reviews | Varies | Same day for messages; reviews per review policy |
| Website form and email | Catering, private events, job applications, invoices | Manager or owner | Within one business day |
| Reservation platform messages | Booking notes, changes | Host | Before the booking time |
What one inbox means in practice
There are two routes. A shared inbox tool pulls messages from several channels into one list that the team can assign, tag and close. Alternatively, you keep the native apps but agree that every message is logged in one place, such as a shared task list, before anyone answers it. The tool route is cleaner; the routine route is better than nothing and costs only discipline.
Phone calls are the hardest channel to bring in, because a call leaves no trace unless someone writes it down. Hosts and hostesses already greet guests, seat them and manage reservations and waitlists[5], so asking them to log every call during service rarely works. Some phone tools log calls automatically: Ava, for example, puts each call in an AssistCall inbox with a summary and transcript and notifies the person you choose. However you do it, the goal is that a manager can see every call that needs follow-up without listening to recordings.
The shift toward mobile makes this more pressing. Mobile ordering is now mainstream, with 57% of adults having used it recently, including 74% of millennials[6]. The same guests expect to message a restaurant the way they order from it, and they notice when nobody replies. Speed matters most where an order is at stake: 94% of consumers say speed is critical when ordering off-premises[2], and a takeout question left unanswered for an hour is usually an order placed somewhere else.
Set routing rules
Tag by request type
Use a short list: booking, change or cancel, takeout or delivery, catering and events, allergy or dietary, complaint, lost property, jobs, vendor, other.
Assign an owner per type
Bookings and changes to the host lead, catering to the events manager, complaints and allergy questions to the manager on duty, jobs to the GM. Write the names down, with backups.
Set a response target per type
Running-late texts in minutes, catering within a business day, job applications within a week. Put the targets where the team can see them.
Escalate on time and topic
Anything unanswered past its target goes to the manager on duty. Allergy, illness, injury and legal mentions go to the manager immediately, whatever the channel.
Close the loop
Mark each message done only when the guest has a clear answer. Note the outcome, such as booked, declined or quote sent.
One owner per message. If two people can answer, both will assume the other did.
Cover the hours nobody is watching
An inbox is only as good as its coverage. Messages arrive when the restaurant is closed, during the rush and on the owner's day off, and those are exactly the times nobody looks. Decide what happens in each window before you switch the inbox on.
- Before opening: the opening manager clears overnight messages and voicemails first, before prep starts.
- During service: the host lead checks booking and running-late messages every 15 minutes; everything else waits for the break.
- After close: an auto-reply on each channel says when the guest will hear back, and gives the online booking and ordering links.
- Days off and holidays: a named backup covers the inbox, and auto-replies show holiday hours.
- Urgent topics at any hour: allergy or illness reports reach the manager on duty by phone, not only in the inbox.
Saved replies that save time without sounding canned
Most messages are variations of a dozen questions. Write short saved replies for them, in your own voice, and edit each one before sending so it answers the actual question.
- Running late: Thanks for letting us know. We will hold your table for 15 minutes; if you will be later than that, reply and we will do our best.
- Large party: We would love to host you. For groups of eight or more we offer a set menu; can you share the date, time and number of guests?
- Catering: Thanks for thinking of us. Please send the date, guest count, location and style of service, and our events manager will reply within one business day.
- Allergy question: Thank you for asking. Our manager will call you to talk through the dish and your allergy, as we do not answer allergy questions by message alone.
- Complaint: We are sorry about your experience. Could you share a phone number and a good time to call? Our manager would like to speak with you directly.
The running-late hold time in that script reflects research showing diners view holding a table for a stated period, typically 15 minutes, as fair[7]. Use whatever your policy is, and keep it the same across every channel.
Texting and messaging rules
Replying to a guest who texted you is a conversation, not marketing. Sending promotions to the same numbers is different, and it brings consent rules into play. Keep marketing out of the shared inbox replies, and follow quiet hours for anything promotional: FCC rules bar telephone solicitations to residential subscribers before 8 a.m. or after 9 p.m. local time[8]. If a guest asks you to stop texting, stop on every number and every tool, and note it in the guest record.
Measure it weekly
- Messages received by channel and by request type.
- Median time to first reply by type, against target.
- Messages past target at the end of each day.
- Outcomes: bookings made, catering quotes sent, complaints resolved.
- Missed calls with no follow-up record.
Put the top two numbers on your weekly dashboard. If response times slip on one channel, check ownership before adding tools: usually the owner changed shifts or left, and nobody picked it up.
Example: one inbox for a neighborhood trattoria
Example (fictional): a trattoria owner found catering inquiries in four places: Instagram, the website form, voicemail and the general email. In a typical month, a few were answered after the event date had passed. She moved DMs, email, the form and Google messages into one shared inbox, set up call logging for voicemail and missed calls, and assigned catering to her events manager with a one-business-day target. Within two months, every catering inquiry had a reply within a day, and the manager could see at a glance which quotes were still open. The host stand stopped carrying the owner's personal phone on Friday nights.
Choosing a shared inbox or phone tool is easier with the restaurant technology vendor checklist, and launching it with the team is covered in rolling out new technology to staff. For kitchen-side systems that also send alerts to managers' phones, see wireless temperature monitoring and robots in restaurants.
Frequently asked questions
Do I need special software for a shared restaurant inbox?
Not to start. A routine where every message is logged in one shared list before it is answered works for small teams. A shared inbox tool helps once volume or the number of channels grows.
Should the host stand answer DMs and emails?
Usually not during service. Give hosts bookings, changes and running-late messages, and route catering, complaints and jobs to managers with clear response targets.
How fast should a restaurant reply to messages?
Within minutes for running-late and same-day booking messages during service, the same day for social messages, and within one business day for catering and events.
How do phone calls fit into one inbox?
Log a short summary for any call that needs follow-up, either by hand or with a phone tool that records summaries automatically. Guests still rely heavily on the phone for bookings[1].
References
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Food and Beverage Serving and Related Workers (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), eCFR text of FCC rule (2026). 47 CFR § 64.1200 - Delivery restrictions (opens in a new tab) ↑