Key takeaways
- Send every voicemail as text plus audio to a shared inbox, not to one manager's personal email.
- Sort before you listen: today's bookings, then catering and events, then complaints, then everything else.
- Play the audio for every phone number, date and headcount; transcripts get those details wrong.
- Delete voicemails that contain card details once handled: PCI guidance says card security codes may not be stored[2].
- Plan each callback as a message you leave, because 67% of adults let unknown numbers go to voicemail[1].
What the Monday mailbox looks like
On a Monday morning the restaurant mailbox holds whatever the weekend could not answer: a catering order for Thursday, a birthday dinner for twelve, a complaint about a cold delivery, three vendor pitches and a guest who left her number twice because the first message cut off. Played in order, that is twenty minutes of listening before you know which call mattered most. As text, it is two minutes of reading and a sorted list.
Guests rely on voicemail more than restaurants assume, and they expect you to use it back. In a 2020 Pew Research Center survey of 10,211 US adults, 67% said their habit is to not answer calls from unknown numbers but to check any voicemail left; only 19% generally answer, and 14% ignore voicemail altogether[1]. That cuts both ways. A guest who calls you will often leave a message instead of trying again, and when you call back, you will usually reach their voicemail.
- Don't answer, but check voicemail 67%
- Generally answer 19%
- Don't answer, ignore voicemail 14%
Source: Pew Research Center, 2020[1]
Show the data
| General practice | Value |
|---|---|
| Don't answer, but check voicemail | 67% |
| Generally answer | 19% |
| Don't answer, ignore voicemail | 14% |
Four ways to turn voicemail into text
Pick the option that matches how your phones already work. The goal is the same in each: every message becomes a written record with the audio attached, somewhere more than one person can see it.
| Option | How it works | Good for | Watch for |
|---|---|---|---|
| Visual voicemail on a mobile | The carrier or handset transcribes messages on the phone | A chef-owner whose mobile is the restaurant line | One person's phone; nobody else sees messages; history leaves with the phone |
| Cloud phone voicemail-to-email | The phone system emails each message with a transcript and the audio file | Most restaurants on a VoIP plan | Messages land in whatever inbox you set; transcription is sometimes an add-on |
| Shared inbox or helpdesk tool | Voicemail emails feed a team inbox with assign and done buttons | Groups with a manager at each location | Another login to keep; keyword rules need upkeep |
| Answered calls with summaries | Calls that would reach voicemail are answered and summarized instead | Overflow and after-hours calls | Covers forwarded calls only; a person still acts on each summary |
For most restaurants the second option is the place to start, and the one inbox guide covers pulling it together with texts and direct messages. Setting it up takes an afternoon.
Create a shared address
Something like phones@ on your own domain, readable by the general manager, the catering manager and whoever opens. Never a personal inbox.
Turn on transcription and keep the audio
You need both: the text to sort quickly, the audio to check numbers and names.
Put caller ID and time in the subject
Most systems allow a subject template. Reading subject lines is the first minute of every sweep.
Ask the greeting for what you need
Name, number, the date and the party size or event date. The voicemail greeting examples show how to ask without a long recording.
Add keyword rules
Flag messages that mention catering, party, event, refund or sick so they sort to the top of the inbox.
Test with three calls
Leave a catering message, a reservation change and a mumbled message from a noisy street. Check the subject, the transcript and the audio for each.
The triage order
Triage is an order of operations, not a fresh judgment on every message. Read all the subject lines first, then work the categories from the top down. The callback targets below are a starting point; write your own on the sweep checklist so the closing manager and the opening manager use the same ones.
| Category | Words to look for | Call back within | Who |
|---|---|---|---|
| Today's and tomorrow's bookings | tonight, running late, cancel, change, tomorrow | Before the next service; within 15 minutes when open | Host or manager on duty |
| Catering and private events | catering, party, event, office, headcount, rehearsal | Same business day; within two hours where possible | Catering or events manager |
| Complaints and food safety | wrong order, cold, refund, sick, allergic | Same day, before next service; illness reports at once | General manager |
| Future reservations and large parties | weekend, birthday, anniversary, group | Same day | Host |
| Questions and everything else | hours, gift card, lost, job, parking | Next sweep | Anyone on the sweep list |
| Vendors and sales calls | special offer, your account, marketing | Weekly, or never | Owner |
Same-day changes come first because they are the ones you can still act on. Diners in Cornell research said guests should call when plans change, yet often found it hard to reach a restaurant to do so[3]. A cancellation heard at 7:30 for a 7:00 table is a lost table either way; one heard at 4:00 can be resold to the waitlist.
Catering and events come next because they are tied to a date and other places want them too. Demand is real: 70% of consumers say they are interested in restaurant tasting events and 52% in private dinner events with a chef[4]. So is the competition, with 13,929 private caterer establishments in the US in 2025[5]. An office manager who called three places on Monday morning often books whoever calls back first. The catering inquiry questions make that callback count.
Complaints come third, not last. A guest who took the trouble to leave a message is giving you a chance to fix it before writing a review. Treat any mention of illness as urgent and follow your own reporting policy; the angry caller guide has callback wording for the rest. Vendor pitches and robocalls go to the bottom or straight to the bin, and the spam and vendor pitch guide covers blocking the worst offenders.
Transcripts get the important parts wrong
Speech-to-text handles ordinary sentences well and the details badly: names, phone numbers, street names, dates and headcounts. Those are exactly the parts a callback depends on. Make it a house rule that nobody returns a call from the transcript alone. Play the audio for the number and the date, and compare the number with caller ID; if they differ, try the one the guest said first.
- Fifteen and fifty, thirteen and thirty. Confirm every headcount out loud on the callback.
- Names spelled by sound. Search the reservation book by phone number instead of by name.
- Days instead of dates. “This Friday” in a Sunday message is next Friday by the time you read it on Monday.
- Messages cut off by the mailbox limit. The caller may have left a second one; check the whole list before calling.
Card numbers in voicemail
Catering clients and party bookers sometimes read out a card number to hold a date. With voicemail-to-email, that number now sits in the audio file, the transcript and every inbox that received the message. PCI guidance says sensitive authentication data such as the card security code may not be stored after authorization, even encrypted, and that when a recording captures it, the merchant must securely delete it[2]. A transcript emailed to four people is hard to call secure storage.
- Add one line to the greeting: “Please don't leave card details; we'll send you a secure payment link.”
- If a card number arrives anyway, take payment through your normal secure process, then delete the message, the audio and the transcript email from every inbox that received it.
- Empty the deleted-items folder as well; most mail systems keep a copy for a while.
- Never forward a card-number voicemail to a personal address or paste it into a text to a colleague.
The catering deposits and payment terms guide covers taking deposits without anyone reading a card number aloud.
The two-minute sweep
- Caller
- System
- Your team
01Caller
Guest leaves a message
Name, number, date and party size, as the greeting asks.
02System
Transcript and audio emailed
Shared inbox; caller ID and time in the subject; keyword rules flag catering.
03Your team
Manager sorts by subject
Today's bookings, catering and events, complaints, then everything else.
04Your team
Details checked by ear
Number, date and headcount confirmed from the audio, not the text.
05Your team
Callback or full message
If the guest does not pick up, a message that finishes the job.
06Your team
Outcome logged, email filed
Done, assigned or waiting on the guest; card details deleted.
Example workflow. Run the sweep before lunch, mid-afternoon and after close, and name who owns each one.
Example: a fictional 80-seat bistro gets fifteen voicemails on a typical day. Listening to each in full at about a minute and a half takes roughly 22 minutes of a manager's time. Scanning transcripts at fifteen seconds each and playing audio only for the six that need a callback takes closer to ten. Food service managers earned a median $33.36 an hour in May 2025[6], so the saving is modest in money. The real gain is that the catering call gets returned before lunch, not after the dinner rush.
Callback scripts that finish the job
Most guests screen unknown numbers[1], so plan every callback as a voicemail you are about to leave. Say who you are, what you are calling about and the one thing the guest needs to do next. The message should complete the job even if you never speak to them.
- Example, catering: “Hi Dana, it's Sam from Harbor Street Kitchen, returning your call about lunch for twenty-five on Thursday. We can do it. I'm emailing three menu options to the address you left; reply with your pick by noon tomorrow and the date is yours.”
- Example, reservation change: “Hi, this is Harbor Street Kitchen. We've moved your table for four to 8:15 tonight, as you asked. No need to call back unless that time doesn't work.”
- Example, complaint: “Hi Marcus, it's Priya, the manager at Harbor Street Kitchen. I'm sorry about last night's order and I'd like to put it right. I'm here until six today, or leave me a time and I'll call you then.”
Log the outcome on the email itself or in the shared inbox: done, waiting on the guest, or passed to someone named. A voicemail that has been listened to but not logged is the one that gets returned twice, or not at all.
When a call shouldn't reach voicemail at all
Voicemail is the right tool for a closed Monday and a quiet afternoon. It is a poor one for Friday at 6:30, when a catering lead or a same-night booking can sit in a mailbox for hours. The after-hours options compared lay out the alternatives. One is to forward unanswered and after-hours calls to an SI Employee: it answers in the restaurant's name, takes the reservation request or the catering details, and the call summary arrives by email with the recording and transcript in your account, so there is nothing to transcribe. Calls it marks urgent arrive as an email flagged URGENT.
- Answered2 events
- Request captured3 events
- Passed to staff2 events
- Confirmed by staff2 events
Activity
- Call
Kitchen hours
Caller asked when the kitchen closes tonight. Ava gave the approved time: 10 pm.
- Call
Table request · party of 8
Saturday, 7:30 pm, birthday. Saved as a request for the host to confirm; no table promised.
- Text
Ordering link sent
Caller wanted pickup and agreed to a text. Ava sent the restaurant’s official ordering link.
- Call
Allergy question → manager
Guest asked about a tree-nut allergy. Ava did not answer it and took a callback for the manager on duty.
- Web form
Catering inquiry · 40 guests
Office lunch next Thursday, drop-off, vegetarian options wanted. Sent to the catering manager.
- Call
Missing item on a delivery
Guest said a side was missing. Ava logged the order name and passed it to the manager with a summary.
- Call
Host confirmed party of 8
Host called the guest back and confirmed Saturday at 7:30 pm. Status updated in the inbox.
- Chat
Private room question
Website chat: rehearsal dinner for 22 in March. Event request created for the events lead.
- Call
Catering manager followed up
Catering manager called back, confirmed the date and sent menu options. Marked as quoted.
- 46Calls answeredExample
- 12Requests sent to staffExample
- 3Catering and event leadsExample
- 5Handed to a managerExample
Example only. Fictional business, people and numbers; not a recording or a live account.
The catering and events example models that setup for a three-restaurant group, and what the answering setup handles today lists the details. Keep the voicemail box either way. Some calls will still land there, and the sweep above is how they get answered on time.
Frequently asked questions
Is voicemail transcription accurate enough to rely on?
For sorting, yes. For phone numbers, names, dates and headcounts, no. Play the audio for those details before you call back, and compare the number with caller ID.
Should voicemails go to one manager or a shared inbox?
A shared inbox. Messages sent to one person's email stop being answered on that person's day off, and leave with them when they change jobs.
How fast should we return a catering voicemail?
The same business day, and within a couple of hours where you can. Office managers often call several places at once, and there were 13,929 private caterer establishments competing for that work in 2025[5].
What if a guest leaves a card number in a voicemail?
Process the payment through your normal secure method, then delete the message, the audio and every transcript email. PCI guidance says card security codes may not be stored after authorization and must be deleted from recordings[2].
Do we still need voicemail if an SI Employee answers overflow calls?
Yes, as a fallback. Forwarding covers the hours and conditions you choose; calls outside them, or any time forwarding is switched off, still need a mailbox and a sweep.
References
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (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) ↑
National Restaurant Association (2025). Restaurant Industry Poised for Growth in 2025 (2025 State of the Restaurant Industry press release) (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Quarterly Census of Employment and Wages, 2025 annual averages, NAICS 722320 (US private) (opens in a new tab) ↑
US Bureau of Labor Statistics (2025). Occupational Employment and Wage Statistics, May 2025: Food service managers median hourly wage (opens in a new tab) ↑