Seasonal peak greeting: a call-flow template

When this flow fits

For a temporary busy period when calls concern a small number of common topics and a short recorded message can set expectations.

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

During a peak, demand exceeds the number of people who can answer, and a simple capacity idea from telephone engineering explains why. Traffic is measured in erlangs, where one erlang is one circuit occupied continuously for an hour 1. Three people who each spend 40 minutes of every hour on calls are carrying two erlangs of work with a capacity of three; as the load approaches the capacity, more calls go unanswered and some callers give up. A peak greeting is a way of managing that honestly.

It does three things: acknowledges that the business is busy, routes the most common call types so each lands with the right person, and offers voicemail for the rest. It should not promise a call-back time unless the team has the headroom to meet it. In a peak, an accurate “within two business days” is better than a hopeful “today”.

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.

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.

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

A worked example

Illustration: a heating company records its autumn greeting in October: “We are handling a busy seasonal period. For a new enquiry, press 1. If you have a job with us, press 2. For anything else, press 3 to leave a message.” In December the same menu stays but the promise changes: the company has hired another coordinator and shortens the call-back window.

Peak seasons also end. A business that forgets to remove its busy-season message in March sounds overwhelmed in the quiet part of the year. The template belongs on the calendar with an on date and an off date.

Timing, options and common mistakes

In general practice, a 20-second ring period before voicemail is a reasonable starting point. Shorten or lengthen it after checking how often callers abandon.

If the main issue is status updates, provide one clear option for existing work.

• Do not promise a response interval you cannot maintain.
• Remove seasonal language promptly when normal volume returns.

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

Peaks are often tax-related for accountants, whose callers ask about deadlines. The IRS publishes return due dates 2 and the estimated tax schedule 3; quote them only after checking the current year’s page.

Ready.gov’s planning guidance includes thinking through what happens when demand or conditions exceed normal capacity 4. For a small business, a peak greeting is a cheap, concrete example of that planning.

Interactive voice response menus are a long-established way to route traffic 5; a short one is better than a long one at the busiest time.

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

• Add “on” and “off” dates to the calendar.
• Route the most common call type first.
• Promise only a call-back window you can meet on the worst day.
• Check the voicemail inbox at fixed times through the peak.
• Review call volume afterwards and decide whether an extra person is needed next year.

Related templates and guides

• Main business greeting: call-flow template
• Overflow when nobody answers: call-flow template
• Field crew dispatch: call-flow template
• Holiday closure: call-flow template
• HVAC business: phone menu guide
• Roofing company: phone menu guide
• Accounting and bookkeeping firm: phone menu guide
• Landscaping business: phone menu guide
• Missed calls and what they cost
• Call routing and menu design