Business phone numbers and phone menus for the United States and Canada. FRES(510) 288-6288[email protected]Sign in

Home › Call-flow templates › Lunch-hour greeting

Call-flow template

Lunch-hour greeting: a call-flow template

When the office closes for a predictable lunch break and nobody is assigned to answer during that period.

Last checked 14 October 2026 · 3 cited sources

Ready-made call-flow templates

When this flow fits

When the office closes for a predictable lunch break and nobody is assigned to answer during that period.

Keep each route tied to a caller need. With Auto Attendant each option does one thing: it rings up to three phones one after another (never together), takes a voicemail, or plays a message and hangs up; a line can also skip the menu entirely. A forwarded call shows your business number as caller ID, and the team returns calls from its own mobiles.

Why this flow is built this way

A lunch-hour greeting is the smallest template and one of the most useful for an office that closes for an hour. Callers who reach a closed-for-lunch message with a return time rarely mind; callers who reach an unexplained voicemail assume the business is closed for the day. The message needs only three things: the business name, the return time and a request for a name and number.

It works best as a scheduled change, not as something someone remembers at 12:55. If your system supports it, set the greeting by schedule. If not, assign the person who leaves for lunch last to switch it on and the first to return to switch it off.

Flow and keypresses

The diagram shows what the caller hears and where each choice leads. The count is the number of keypad selections from the first menu to that destination; a submenu adds another press.

Give the return time and offer a message.

Next: Voicemail; check messages when staff return

Caller destinationKey sequenceKeypressesRoute in this example
Default routeNo keypress0Voicemail; check messages when staff return

Original script wording

Replace the shaded fields with details your callers need. Do not read them aloud as written. Word count and duration are calculated from each script; spoken time is estimated at 150 words per minute, so pauses and keypad instructions may make the spoken greeting longer. Auto Attendant reads your wording in a text-to-speech voice; you type the words rather than recording them.

Short break · 37 words · about 15 sec at 150 words per minute

You have reached Business name. We are away from the phones for lunch and expect to return at time. Please leave your name, number and a brief message, and we will call you back after we return.

Shaded text is a fill-in field: replace it with your own.

A worked example

Illustration: a dental office closes from 1 to 2 p.m. Its lunch greeting says the office is at lunch and will return at 2, asks for name and number, and promises a call back “after 2”. The front desk reads the transcripts at 2:05 and returns the calls in order.

A common slip is naming a return time and then returning late. If the office routinely re-opens at 2:15, record 2:15, because callers who hear “2” and still reach voicemail at 2:10 lose confidence.

Timing, options and common mistakes

Schedule only the actual break window. If the team staggers lunch and someone can answer, leave the normal route active instead.

If the return time varies, say “later today” only when that is a reliable expectation.

  • Avoid making callers navigate a menu that routes to nobody.
  • Do not forget to change the greeting after the break.

Say the option before its key, put the most frequent caller need first, and repeat the key choices at the end. A practical starting point is no more than about four top-level options: callers must listen, remember the choices and select one. Use a submenu for a less common branch rather than making every caller hear every detail.

For a full routing walkthrough, see call routing and menu design. An Auto Attendant menu has up to seven options; each rings up to three phones in turn, takes a voicemail or plays a message. The menu can be in English, French or Spanish. Voicemails are emailed in the business’s chosen language with the MP3 attached, followed by a transcript in the language of the message.

Standards and rules behind it

Whether staff must answer the phone at lunch has a wage-and-hour answer. The Department of Labor’s rule is that a bona fide meal period is not working time, but the employee must be completely relieved from duty, and an employee required to perform any duties, active or inactive, while eating is working while eating 1. More generally, time is off duty only if the employee is completely relieved and has been told in advance that they may leave and need not start work until a specified hour 2. If a person must stay at the desk to answer the phone, the break may be paid working time. A recorded lunch greeting is one way to let the whole team take a genuine break.

Offer callers who need help during the break a route that exists, such as an email address, since a voicemail is not an answer 3.

This is general information, not legal advice. Rules differ by state and change; confirm anything that affects your business with the source or an adviser.

Test it before you publish it

  • Give the real return time, not the intended one.
  • Set the greeting to switch automatically, or name who switches it.
  • Confirm that no one is required to answer the phone during the break.
  • Clear lunch-hour voicemail within about 15 minutes of returning.
  • Avoid using the template for breaks longer than about two hours.
Put a clear menu on your business number
Use these words as a starting point, then point each option at the phones, voicemail or message that fit your team.
Get started

Further reading

Longer research pieces on this topic, each with its own source list and a downloadable PDF.

Sources

Every regulatory and pricing claim on this page links to the primary source it came from. Figures were checked on the date shown at the top of the page; rules and prices change, so verify before relying on one.

  1. 29 CFR § 785.19, Meal periods (US Department of Labor hours-worked rules). Retrieved 14 Oct 2026
    https://www.law.cornell.edu/cfr/text/29/785.19
  2. 29 CFR § 785.16, Off duty (US Department of Labor hours-worked rules). Retrieved 14 Oct 2026
    https://www.law.cornell.edu/cfr/text/29/785.16
  3. ADA.gov, ADA Requirements: Effective Communication. Retrieved 14 Oct 2026
    https://www.ada.gov/resources/effective-communication/