How many options should an IVR menu have?

Keep each menu short, with the most common reasons for calling first and a clear option for anything else. Long lists are hard to remember when heard rather than read. If you need many options, split them into a short first menu and a second level, or let callers say what they need in their own words.

What should an IVR greeting say?

A good IVR greeting names your company, tells callers how to get help, and gets to the first question quickly. For example: "Thanks for calling [Company]. You can say what you need at any time, or press 0 for a team member." Skip long legal or marketing messages unless they are required.

How do you write IVR scripts?

Start from your call flow map, then write one prompt per step. Say the option before the key, ask one question at a time, use the words on your bills and website, give examples for open questions, and read back important details before acting. Write separate help prompts for silence and for unrecognized answers.

Should an IVR always offer an option to speak to an agent?

Yes, in almost every case. Callers who cannot find a person may hang up, call back or pick random options, which hurts both customer satisfaction and your data. Offer the agent route in the main menu or accept 0 and "agent" at any point, and offer it automatically after repeated errors.

Is text-to-speech good enough for IVR prompts?

Modern neural text-to-speech voices work well for dynamic content such as names, amounts and dates, and for prompts that change often. Many teams still record fixed greetings and menus with a voice talent for a consistent brand voice, then choose a TTS voice that sounds similar so the two blend.

IVR call flow design: best practices and example prompts

A well-designed IVR call flow gets callers to the right outcome in as few steps as possible and makes it easy to reach a person when automation is not the answer. This guide gives you a step-by-step design process, rules for writing prompts, and example IVR scripts you can adapt for greetings, menus, input collection, confirmations, errors and transfers.

What makes a good IVR call flow?

A good IVR call flow is built around why customers call, asks one clear question at a time, handles errors without trapping callers, and passes context to an agent when it transfers. If callers finish their task quickly or reach the right person on the first try, the flow is working.

Poor flows usually share the same problems: one long menu for every caller, company jargon in the prompts, no obvious way to reach an agent, and scripts that have not been reviewed since launch.

How to design an IVR call flow, step by step

Follow these steps for a new IVR or a redesign:

Start with call reasons. Pull your top reasons for calling from agent dispositions, call recordings or IVR reports. Rank them by volume and by whether a caller could finish them alone.
Pick the tasks to automate. Good candidates are structured and repetitive: payments, balance and status checks, card activation, appointment changes and surveys.
Define the outcome of every path. Each path should end in one of three places: task completed, transfer to the right agent with context, or a scheduled callback or follow-up message.
Map the flow before writing prompts. Sketch the menu, the inputs each task needs, the back-end lookups, and every exit. Put the most common reasons first and keep menus short.
Use what you already know. If the caller ID matches an account, greet the caller by name or skip straight to the likely task. Do not ask for information you already have.
Choose the right input method. Keypad (DTMF) entry is reliable for numbers and card details. Speech works well for open requests, names and yes or no answers. Letters are hard over the phone, so use a structured grammar that knows which positions hold letters, or send an SMS to collect values like email addresses.
Design error handling. Plan what happens on silence (no input) and on an unrecognized answer (no match). Reprompt with more help, allow two attempts, then offer an agent or another route. VoiceXML 2.0 defines these as noinput and nomatch events, and most platforms expose the same idea.
Make the agent option easy to find. Offer it in the main menu or accept "agent" and 0 at any point. Never make a caller ask twice, and do not replay self-service messages while they wait.
Write and record the prompts. Follow the rules in the next section, then record with one consistent voice.
Test with real callers, then keep tuning. Watch where callers hang up, loop or transfer, fix those steps first, and review scripts at least when products, policies or hours change.

IVR prompt best practices

Good IVR prompts are short, specific and written in the words customers use. Apply these rules to every prompt:

Say the option before the key. "For billing, press 1" lets callers hear the topic first and remember the key.
One question per prompt. Ask for the account number, then the date of birth, not both at once.
Use customer language. Say "your account number from the top of your bill," not "your CIN."
Match your documents. If the bill says "account number," the IVR should not say "customer ID."
Give an example for open questions. "Tell me what you're calling about. For example, 'make a payment' or 'check my order.'"
Read numbers in chunks. Play account numbers, dates and amounts in groups so callers can follow and correct them.
Confirm what matters. Read back payment amounts and dates before you act on them.
Let callers interrupt. Barge-in lets experienced callers press or speak before a prompt finishes.
Cut filler. Skip "Please listen carefully, as our options have changed" unless they changed this week.

Example IVR prompt scripts

These example IVR scripts cover each stage of a typical call. Replace the bracketed items with your own details.

Stage	Example prompt	Why it works
Greeting	"Thanks for calling [Company]. You can say what you need at any time, or press 0 for a team member."	Short, sets expectations, shows the agent route up front
Personalized greeting	"Hi [first name]. Are you calling about your payment due on [date]?"	Uses caller ID data to skip the menu for the most likely task
Main menu (keypad)	"To make a payment, press 1. To check your balance, press 2. For anything else, press 3."	Three options, most common first, option before key
Main menu (speech)	"In a few words, tell me why you're calling. For example, 'pay my bill' or 'report a lost card.'"	Open question with examples of what to say
Input collection	"Please enter your 10-digit account number, found at the top right of your bill, then press pound."	States the length, the location and how to finish
Confirmation	"I have [amount] from the card ending in [last four], to be paid on [date]. Press 1 to confirm or 2 to change it."	Reads back key details before the transaction
No input	"Sorry, I didn't hear anything. Your account number is 10 digits and is at the top right of your bill. Please enter it now."	Adds help instead of repeating the same words
No match	"That number didn't match our records. Please enter the 10 digits again, or press 0 to speak with someone."	Offers a retry and a way out
Second error	"Let's get you some help. I'm connecting you to a team member now."	Stops the loop after two failed attempts
Transfer	"I'm transferring you to our billing team. I've passed along your account details, so you won't need to repeat them."	Tells callers where they are going and reduces repetition
Callback offer	"The wait is about [minutes] minutes. To get a call back instead, press 1. Your place in line is saved."	Respects the caller's time
Task complete	"Your payment of [amount] is complete. Your confirmation number is [number]. I can also text it to you. Press 1 for a text."	Gives proof and an easy record

IVR message examples for hours and hold

After hours: "Our team is available Monday to Friday, 8 a.m. to 6 p.m. Eastern. You can still make a payment or check your balance now. To do that, press 1."
Holiday: "Our offices are closed today for [holiday]. Automated payments and balance checks are available as usual."
Hold message: "Thanks for waiting. You can also make payments any time by calling this number and pressing 1."

Should you use recorded audio or text-to-speech?

Use recorded audio for fixed prompts and text-to-speech (TTS) for dynamic values such as names, amounts and dates. Most flows mix both, so the two need to sound like they belong together.

	Recorded audio	Text-to-speech
Best for	Greetings, menus, fixed instructions	Names, amounts, dates, frequently changing content
Sound	Most natural, consistent brand voice	Neural voices sound far more natural than older engines
Cost to change	Needs a new recording session	Edit the text and publish
Tips	Use one voice talent and keep pace and volume consistent	Choose a TTS voice close to your recorded voice; tune pronunciation with SSML

When you split prompts into reusable files, such as a question file and a shared instruction file, record them in the same session with matching tone so they flow together when the IVR joins them.

Common IVR design mistakes to avoid

One menu for every caller, regardless of why they are calling
No clear way to reach an agent, or a hidden 0 option
Timeouts that are too short for callers to find an account number
Errors that send callers back to the main menu
Prompts that mention discontinued products or old hours
Transfers that drop the details callers already entered

To see how these mistakes show up in your numbers, read our guide to IVR containment and first call resolution.

How Plum Voice handles this

In Plum Fuse, teams build call flows visually and can start from 37+ prebuilt templates, such as Payment Processing, Account Inquiry, Card Activation and Appointment Scheduling. The Prompt module joins pre-recorded audio with TTS variables, and the Audio Manager and bulk upload keep recordings organized. Module settings cover barge-in, timeouts and custom error handling, and the Transfer module reports results such as no answer or busy so the flow can respond. Developers on Plum DEV use the standard VoiceXML noinput and nomatch tags.