All Articles
·8 min read

IVR Phone Greeting Scripts: Examples and Best Practices

MP

Max P

TextSpeakPro

Callers decide within about 10 seconds whether your phone system will help them or waste their time. A greeting that runs long, reads too slowly, or hides the path to a human sends them straight to voicemail abandonment or a competitor. This guide covers the timing rules and menu design rules that keep callers on the line, plus six complete IVR scripts with word counts that you can copy and adapt today.

Why callers abandon IVR menus

Most hang-ups trace back to three script mistakes:

  • Long menus. Callers hold only a few items in short-term memory. When a menu lists eight options, most people have forgotten option 2 by the time option 6 plays, so they guess wrong or hang up and redial. Every misroute costs you a frustrated caller and an interrupted employee.
  • Slow pacing. Mission statements, "please listen carefully as our menu options have changed," and long thank-you preambles all delay the thing the caller actually wants: the options. Every second of filler before the first choice raises the odds of abandonment.
  • Burying the operator option. Some callers will always want a person. If you hide the operator path behind a full menu read, or remove it entirely, those callers do not give up and self-serve. They press 0 repeatedly, hit an error, and hang up angry.

Timing rules that keep callers on the line

Three numbers govern a good greeting:

  • Keep the main greeting under 30 seconds. That includes the welcome line and every menu option. If your script runs long, cut options, not clarity.
  • Reach the first option within 8 to 10 seconds. The welcome line plus any single announcement must fit in that window. Callers start pressing random buttons when nothing actionable has played by second 10.
  • Read at about 140 words per minute. Conversational speech runs 150 to 180 words per minute, but phone audio is compressed and callers are often multitasking, so a slightly slower 140 wpm read is the clarity sweet spot on the phone.

Those rules convert directly into word budgets:

ElementTime targetWord budget at 140 wpm
Full main greetingUnder 30 seconds70 words or fewer
Intro before the first menu option8 to 10 seconds18 to 23 words
Each menu option2 to 4 seconds5 to 9 words
After-hours or holiday greetingUnder 25 seconds58 words or fewer

You do not have to do this math by hand. Paste your draft into the free IVR phone script timer to see your runtime at phone-friendly reading speeds and catch scripts that break the 30 second rule before you record anything.

Menu design rules

  1. Cap the menu at 4 or 5 options. If you have more departments than that, group them ("For sales and new orders, press 1") and let a short second layer or a human sort out the rest.
  2. Put the most-used option first. Pull your call logs. If 60 percent of callers want scheduling, scheduling is option 1, even if your org chart says otherwise.
  3. Always offer 0 for a human. Say it out loud, and make sure the key actually works at every point in the tree, including submenus and hold.
  4. Point simple questions to your website. One short line ("For hours and directions, visit our website") deflects the easiest calls before they ever reach the queue.

Six complete IVR scripts you can copy

Each script below is written for a fictional plumbing company at a 140 wpm read. Swap in your own company name, menu options, and website, and watch the word count as you edit.

1. Main business-hours greeting (51 words, about 22 seconds)

Script: "Thank you for calling Ridgeline Plumbing. For faster service, you can book appointments anytime at ridgelineplumbing.com. To schedule or change an appointment, press 1. For billing questions, press 2. For emergency service, press 3. For all other questions, press 4. To speak with a team member at any time, press 0."

The website mention lands inside the first 8 seconds, the busiest option comes first, and 0 is stated explicitly.

2. After-hours greeting (56 words, about 24 seconds)

Script: "Thank you for calling Ridgeline Plumbing. Our office is currently closed. Regular hours are Monday through Friday, 8 a.m. to 6 p.m. For emergency plumbing service, press 1 now. To leave a message for our office team, press 2, and we will return your call the next business day. For answers to common questions, visit ridgelineplumbing.com."

State the closure immediately, then give the emergency path before anything else. Never make a caller with a burst pipe sit through your weekday menu.

3. Holiday closure greeting (46 words, about 20 seconds)

Script: "Thank you for calling Ridgeline Plumbing. We are closed Thursday, November 26 and Friday, November 27 for the Thanksgiving holiday. We will reopen Monday, November 30 at 8 a.m. For emergency plumbing service, press 1. To leave a message, press 2. Thank you, and happy holidays."

Give the exact reopening date and time. "Closed for the holiday" with no return date guarantees repeat calls that also go nowhere.

4. Hold message (51 words, about 22 seconds)

Script: "Thanks for holding. A team member will be with you shortly. While you wait: you can schedule service, view invoices, and make payments anytime at ridgelineplumbing.com. If you would rather not wait, press 1 to leave a message, and we will call you back in the order your call was received."

A hold message should offer an exit, not just apologize. The callback option turns an abandoned call into a saved one.

5. Voicemail prompt (41 words, about 18 seconds)

Script: "You have reached the voicemail for Ridgeline Plumbing. Please leave your name, phone number, and a brief description of the issue after the tone. We return all messages within one business day. For emergencies, hang up and call 555-0142. Thank you."

Tell callers exactly what to leave and when to expect a callback. A stated response window sharply cuts repeat calls.

6. Call-recording disclosure line (10 words, about 4 seconds)

Script: "This call may be recorded for quality and training purposes."

Play a disclosure like this before any recording begins, typically at the very start of the greeting. Requirements for call-recording notices vary by region: some jurisdictions require all-party consent, others accept notice alone, and wording that satisfies one may not satisfy another. This is general information, not legal advice, so confirm the rules that apply where you and your callers are located. The free compliance disclaimer generator can produce a starting draft to review with a qualified professional.

Why one consistent AI voice beats recording prompts yourself

The typical small-business prompt library is a patchwork: a main greeting recorded by an office manager three years ago, a holiday message from whichever employee was free in December, a voicemail prompt from someone who has since left. Callers hear the seams, and the whole system sounds improvised. A single AI voice fixes three specific problems:

  • Consistency. Every prompt, from the main greeting to the deepest submenu, is read in the same voice at the same pace and volume. The system sounds like one professional recording session instead of five.
  • Instant updates. When your hours change, you edit a sentence and regenerate the file in minutes. No hunting down the original speaker, no hoping they can match their own tone from two years ago.
  • No re-recording sessions. No booking a quiet room, no six takes because a phone rang in the background, no employee who cringes at their own voice. A typo in the script gets fixed by retyping, not re-performing.

Generating IVR audio with text to speech

Here is the full workflow using TextSpeakPro:

  1. Finalize the script first. Check every prompt against the word budgets in the table above before you generate anything.
  2. Pick one voice for everything. TextSpeakPro offers 135+ AI voices. Audition a few on your main greeting, choose one, and use it for every prompt in the system.
  3. Tune the delivery. Use the emotion controls to keep the read calm, warm, and professional. An even tone works for menus; save energetic reads for marketing audio.
  4. Download WAV files. Paid plans include WAV and MP3 downloads. Most phone systems accept WAV uploads for greetings and prompts, so generate one file per prompt and label each clearly, such as main-greeting.wav and after-hours.wav.
  5. Upload and test. Load the files into your phone system, then call the number from a real handset and time the greeting yourself.

Commercial use is included on paid plans, and IVR audio is a supported commercial use, so the prompts you generate are cleared for your business line. The free plan gives you a one-time 2,000 characters across 10 voices, enough to generate and test the six sample scripts above, which total roughly 1,500 characters. The Starter plan at $4 per month includes 150,000 characters per month, enough to rebuild an entire prompt library many times over whenever hours, menus, or staff change.

Write tight, lead with the busy options, keep 0 working everywhere, and give every prompt one consistent voice. Do that and your phone system stops being the reason callers give up.

IVRphone greetingsauto attendanttext to speechbusiness audio

Ready to create your voiceover?

Turn your script into natural-sounding speech with 60+ AI voices.

Try TextSpeakPro Free