Key takeaways
- Write for the first 30 seconds. Most holds at a host stand are short, so the first message has to land before the host comes back.
- Keep each message to 10 to 15 seconds inside a loop of about a minute, and record separate loops for lunch, dinner and closed hours.
- Point callers to your ordering link but keep the person route open: 85% of millennial full-service diners would order by app, against 33% of baby boomers[1].
- Leave out prices, allergen reassurance, table promises and any music you are not licensed to play[2][3].
The thirty seconds that decide whether a caller waits
Most holds at a restaurant are not planned. The host says “one moment, please,” presses the button, seats a four-top and comes back. Whatever plays in between is the restaurant talking to a guest it has not finished helping, and on a busy night that happens dozens of times. Cornell researchers described the root of it years ago: when the person taking reservations also greets guests, seats them and assembles takeout orders, callers get put on hold, the agent is rushed and record keeping slips[4]. That is still the job description at most host stands.
Callers give you a short window and then they don't. In the National Restaurant Association's 2025 off-premises research, 94% of consumers said speed is critical when ordering takeout or delivery[5]. Plenty of them still want a person: in a 2012 Cornell survey, about two-thirds of diners who had never booked online said they wanted to talk to someone to make a reservation[6]. A hold message cannot fix a long wait. Its job is narrower: prove the call is still connected, answer one likely question, and offer a faster route to anyone who wants one.
This guide covers loop length, eight scripts you can adapt by daypart, and what to leave out. For the host's side of the hold, asking permission and coming back with an answer, see how to put a restaurant caller on hold politely.
How long the loop should run
Build the loop around the hold you actually have. If the host normally returns inside 30 to 45 seconds, the caller should hear one complete message in that window and should never hear the same sentence twice. A loop of about 60 seconds does that: music starts at once so the line never sounds dead, the first message lands within a few seconds, a second message comes near the halfway point, and the loop repeats.
0:00
Music starts straight away, so the line never sounds dead
0:05
Message 1: thanks for holding, the host will be right back
0:20
Music only, at a low level
0:30
Message 2: the ordering link or one useful fact for tonight
0:45
Music, then the loop starts again from the top
Example timing. If your normal hold runs past a minute, fix the staffing or routing before you lengthen the loop.
Message length matters more than loop length. Example: a 30-word message read at an unhurried pace runs roughly 12 to 15 seconds, so two of them plus music fill a minute comfortably. A 90-word promotion fills the whole minute on its own, and that is usually the message that makes people hang up.
| Line | Typical hold to plan for | Loop length | Messages per loop | Music |
|---|---|---|---|---|
| Quick-service or pizzeria pickup | Under 30 seconds | 30 to 45 seconds | 1: the ordering link | Upbeat, low volume |
| Casual full-service | 30 to 60 seconds | About 60 seconds | 2 | Neutral instrumental |
| Fine dining reservations | Under 45 seconds | About 60 seconds | 1 or 2, no promotions | Quiet, or none |
| Catering or events transfer | 1 to 2 minutes | About 90 seconds | 2 or 3 | Neutral instrumental |
| Prep hours before opening | Varies | About 60 seconds | 2: hours and website | Optional |
To find your real number, ask hosts to jot the time on three or four holds per shift for a week, or pull hold durations from the phone system's call log if it records them. Take the middle value, not the worst one. If that middle value is over a minute, the loop is not the problem; the last section of this guide covers what is.
Eight scripts by daypart
Each script below reads in 10 to 15 seconds. The restaurant names and web addresses are examples; swap in your own and keep one idea per message. Record each loop as its own file and switch them on a schedule, the same way you rotate voicemail greetings.
- Weekday lunch, pickup-heavy: “Thanks for holding at Linden Street Kitchen. We'll be right with you. If you're ordering pickup, the quickest way is our website, lindenstreetkitchen.com.”
- Dinner service, full-service room: “Thanks for waiting. You've reached Linden Street Kitchen, and your host will be back in a moment. Tonight the kitchen takes orders until ten.”
- Friday peak at a pizzeria: “Thanks for calling Quarry Hill Pizza. We're busy and we haven't forgotten you. Ordering at quarryhillpizza.com skips the line, or stay on and we'll take it here.”
- Weekend brunch with a waitlist: “Thanks for holding. Brunch is first come, first served, and you can join the waitlist on our website before you leave home. We'll be right back.”
- Holiday week: “Thanks for holding. We're open Christmas Eve until eight and closed Christmas Day. For New Year's Eve, stay on the line and the host will help you.”
- Catering line, while the manager is fetched: “Thanks for holding. We're getting our catering manager. If you have your event date and guest count handy, that's all we need to start.”
- Large party or private room: “Thanks for waiting. Our private dining room seats up to twenty-four. Stay on the line and we'll check your date with you in a moment.”
- Prep hours, when a manager answers between tasks: “Thanks for calling. We open at five tonight. Stay on the line and we'll be right with you, or find the menu and hours on our website any time.”
Read every script aloud against a stopwatch before you record it. If it runs past 15 seconds, cut a clause rather than speeding up the voice.
Should the hold message push the ordering link?
On a pickup-heavy line, usually yes, as the first or second message. Most callers can use it. In the National Restaurant Association's 2024 technology survey, 63% of full-service customers said they would place an order with a smartphone app if a local table-service restaurant offered one, and 84% of delivery customers said they would order delivery through a restaurant's website[1].
Source: National Restaurant Association, 2024[1]
Show the data
| Group | Would order by app |
|---|---|
| All adults | 63% |
| Gen Z (18-27) | 79% |
| Millennials (28-43) | 85% |
| Gen X (44-59) | 67% |
| Boomers (60-78) | 33% |
The age split is the reason to keep a person on the other end. Only 33% of baby boomers said they would order through an app at a full-service restaurant, against 85% of millennials[1]. A hold message that says “please order online” and stops there tells an older regular the restaurant would rather not talk to them. Pair the link with a promise: “or stay on the line, and we'll be right with you.”
Say the address the way a listener can type it: the bare domain, no “https,” no slashes, no tracking codes. If the name is hard to spell, say it once, slowly, or buy a short domain that is easy to say. A caller who would rather have the link in a text can ask the host when the hold ends.
What never belongs in a hold message
- Prices and specials that change. A recording outlives the special, and when the hold loop disagrees with the menu, the host loses the argument.
- Allergen reassurance. “We're happy to accommodate any allergy” is a promise the kitchen may not be able to keep on every dish. The eight major allergens accounted for 90% of US food allergies and serious reactions when federal labeling law passed[7], so allergy questions belong with a person who can check. See handling allergy questions over the phone.
- Table or wait-time promises. “Tables are available tonight” is false by eight o'clock. Quote times live, never on tape.
- A radio station or someone's playlist. Copyright owners hold the exclusive right to perform their music publicly[3], and the law counts transmitting a performance to the public as performing it, even when listeners are in separate places at different times[2]. Use hold music your phone provider licenses, buy licensed production music, or play none.
- Long promotions. A 45-second pitch for brunch, played to someone trying to change tonight's booking, is the clip that gets hung up on.
- Stock lines such as “your call is important to us.” Callers hear them as a sign the wait will be long. Say who will pick up, and what is quicker.
- Menu options that loop back. If the message offers “press 1,” check that pressing 1 does not drop the caller into the same hold. Setting up a restaurant phone menu covers menu design.
Recording and installing the loop
Write and time it
Draft each message, read it aloud against a stopwatch and cut anything past 15 seconds. One idea per message.
Record in a quiet room after close
Use a decent phone or a USB microphone in an office with the door shut, not the dining room. Keep the voice warm and slightly slower than normal conversation.
Set the levels
Keep music clearly below the voice and both a little below normal call volume, so nobody is blasted when the host picks back up.
Load it and assign it
Upload the files in the phone system's portal, attach them to the hold action, and set a schedule if the system allows different loops by hour.
Test from an outside phone
Call the main number from a mobile, ask to be put on hold and listen to two full loops. Check volume, when the first message starts and that the loop restarts cleanly.
Give it an owner and a review date
Name one manager who owns the hold loop and check it every quarter and before each holiday period. Stale hold messages are usually ones nobody owned.
Don't put a recording notice in the hold loop. If you record calls, the notice belongs in the greeting before anything is recorded, and some states require every party's consent rather than one[8]. Restaurant call recording laws by state has the state-by-state detail.
Use one voice across the greeting, the hold loop and the voicemail, often the owner's or the general manager's, and never name staff in the recordings. People move on; files stay on the system for years.
When the hold itself is the problem
- Caller
- Your team
- System
- SI Employee
01Caller
Guest calls the main line
Asks for a table for six on Saturday.
02Your team
Host asks to hold
Waits for a yes and gives a time: “about thirty seconds.”
03System
Dinner loop plays
Music at once, the thank-you message, then the ordering link.
04Your team
Host returns with an answer
Back inside 45 seconds, or takes a name and number for a callback.
05SI Employee
Third caller to overflow
Both lines busy, so the forwarded call is answered and logged, not parked.
Example. The last step uses overflow forwarding, so the third caller never joins a hold queue at all.
A good loop makes a 40-second hold feel shorter. It does nothing for a four-minute hold, and it cannot help the second and third callers ringing while the first one waits. If your week of timed holds shows waits of more than a minute as a matter of routine, fix capacity first: a second person on the phone at peak, a clear rule on when to let the phone ring, or overflow forwarding that picks up when every line is busy.
Overflow is where an SI Employee fits. The restaurant forwards its number when the lines are busy or nobody picks up in time, and the forwarded call is answered from house information you approve: hours, location, reservation requests for the host to confirm, and your ordering link by text when the caller agrees and you have a registered texting number. Each call lands in your inbox with a summary and transcript. The pizzeria Friday-rush example models what that does for a two-line counter on its busiest night, and AssistCall's phone orders and catering example works through the same setup for a full-service menu.
Frequently asked questions
How long should a restaurant on-hold message be?
Each message should run 10 to 15 seconds, inside a loop of about a minute with music between messages. If your normal hold lasts longer than a minute, fix staffing or routing before you lengthen the loop.
Can we play the radio or a streaming playlist on hold?
It is a risk. Copyright owners control public performance of their music[3], and transmitting a performance to the public counts even when listeners are in different places at different times[2]. Use music licensed for hold through your phone provider or a production-music library, or none.
Should the hold message tell callers to order online?
On pickup-heavy lines, yes, as one of two messages. Most diners are comfortable ordering by app or website, but only a third of baby boomers would order by app at a full-service restaurant[1], so always say someone is coming back.
Who should record the messages?
Someone with a calm, clear voice, often the owner or general manager, so the greeting, hold loop and voicemail sound like one restaurant. Don't name staff in the recordings; people move on and the files stay.
Does the hold message need to say the call is recorded?
No. If you record calls, put the notice in the greeting at the very start, before recording begins. Some states require the consent of everyone on the call[8].
References
National Restaurant Association (2024). Restaurant Technology Landscape Report 2024 (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 17 U.S. Code § 101 - Definitions (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 17 U.S. Code § 106 - Exclusive rights in copyrighted works (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View On-line Reservations (Cornell Hospitality Report, Vol. 9 No. 5) (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 (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
US Food and Drug Administration (2026). Food Allergies (opens in a new tab) ↑
Legal Information Institute (Cornell Law School), US Code (2026). 18 U.S. Code § 2511 - Interception and disclosure of wire, oral, or electronic communications prohibited (opens in a new tab) ↑