IVR prompts best practices: scripts, voice, and menu tips
Short, clear IVR prompts, a single consistent voice, clean audio, and paths under two steps. Includes copy‑paste scripts, bilingual tips, and a simple menu design.
Telecom engineering and support at CallFlow (ALERTSIO LLC)

The IVR prompts best practices are simple: keep greetings short, limit the main menu to three to five choices, and say the action before the key (“Press 1 for sales”). Good IVR (interactive voice response, the phone menu callers use) design also gives a fast path to a person. Use one clear voice. Add language choice at the start when needed, and keep the tree shallow with at most one sub-menu. Follow this how-to and, in about an hour, you’ll have a mapped menu, tight scripts, and clean recordings that move callers to the right place fast.
What makes a good IVR prompt?
Good IVR prompts are clear, short, and written for the first listen. A caller decides in a few seconds if they understand you. Don’t waste that time on a long brand intro or legal text. State who you are in one short line, then get to the menu.
Keep your top menu tight. Three to five choices is the sweet spot. Say what the caller gets before the key: “For the front desk, press 1.” Put the live person option where people expect it (often 0 or say “agent”). If you need a sub-menu, use it to group only one topic (like “appointments”). Keep it to three or fewer choices.
Use one voice, tone, and pace across all prompts. Mixing voices sounds unpolished and confuses callers. Add language choice right up front so people don’t sit through a menu they can’t use. The first line after your greeting should be “For English, press 1. Para español, oprima 2.” (Swap languages to match your market.)
Aim for one main menu and one simple sub-menu at most. The deeper the tree, the more drop-offs you’ll see. Avoid “more options.” If you need “more options,” you need a smaller menu.
Design a short IVR menu (with examples)
Use a small clinic that has business hours, an after-hours route, and an English/Spanish option. During hours, the clinic wants: front desk and billing. After hours, callers should hear a short message and go to voicemail. Make 0 reach a person whenever possible.
Keep the top menu to three to five choices. If you have six or more, split the topic (for example, move “appointments” to a sub-menu). Place “talk to a person” at 0 and route it to the front desk during hours. After hours, send 0 to the same after-hours path. Voicemail is your clean fallback. Don’t loop callers back to the start more than once.
Greeting: “Thank you for calling Riverside Clinic.”
Language: “For English, press 1. Para español, oprima 2.”
Main (open hours): “For the front desk, press 1. For billing, press 2. To speak with a person at any time, press 0.”
After hours: “Our office is closed. Please leave a message with your name, number, and reason for calling.”
If you run a service office instead of a clinic, swap “front desk” for “service team,” but keep the counts the same. For more on when an IVR makes sense and how it fits your inbound flow, see IVR for business.
IVR prompts best practices you can use today
Write for the ear, not the page. Use short words. One idea per sentence. Say the action before the key. “For appointments, press 1.” Not “Press 1 if you would like to make, change, or cancel an appointment.”
Cut internal jargon and department names callers won’t know. “Customer accounts” is clearer than “AR” or “Client success.” If callers don’t know which option to pick, they guess, then they call back. That hurts answer rates.
Say your hours only when they change call flow. “We’re open 9 to 5” is useful if you send after-hours callers to voicemail. It’s noise if you still route to the same queue.
Confirm choices in longer branches. When a caller presses 3 for billing, say “Billing, press 3” before you route. It reduces mis-keys and makes the caller feel in control.
Set ring and queue (a waiting line that holds callers with hold music) times with care. Let each target ring 20–25 seconds (about four to five rings), then try the next target or send the call to a queue. Let the queue wait 60–90 seconds before voicemail. If many callers hit voicemail, reduce the queue time or add a backup target in your route.
Use clear error and repeat prompts. “Sorry, I didn’t get that. For the front desk, press 1. For billing, press 2. To speak to a person, press 0.” Do not repeat the menu more than twice.
Write scripts callers follow on the first listen (copy-paste)
Here are short, neutral scripts you can copy and tailor. Swap names and numbers to fit your team. Keep each line to one idea.
Opening greeting: “Thank you for calling Riverside Clinic.”
Bilingual language pick (English/Spanish): “For English, press 1. Para español, oprima 2.”
Bilingual language pick (English/Hindi): “For English, press 1. हिंदी के लिए 2 दबाएँ.”
Main menu (English): “For the front desk, press 1.” “For billing, press 2.” “To speak with a person, press 0.”
Menú principal (Español): “Para recepción, oprima 1.” “Para facturación, oprima 2.” “Para hablar con una persona, oprima 0.”
मुख्य मेनू (Hindi): “रिसेप्शन के लिए 1 दबाएँ.” “बिलिंग के लिए 2 दबाएँ.” “प्रतिनिधि से बात करने के लिए 0 दबाएँ.”
Sub-menu (example: Appointments): “For a new appointment, press 1.” “To change or cancel, press 2.” “To return to the main menu, press 9.”
After-hours message: “Our office is closed. Please leave your name, number, and reason for calling. We’ll return your call the next business day.”
Queue/hold message: “All agents are helping other callers. Please stay on the line. Your call matters to us.”
Voicemail prompt: “At the tone, please state your name, number, and how we can help. Press the pound key when finished.”
Error and repeat: “Sorry, I didn’t get that. Please choose from the menu.”
Stick to one voice across all of these. If you localize into another language, re-record the whole set in that language instead of mixing lines.
Record IVR prompts: voice and clean audio tips
Pick one consistent speaker. Choose an accent most callers expect. In the US, neutral North American English works well. In India or Pakistan, a clear Indian English or Urdu/Hindi speaker helps. In the Philippines, a Filipino English or Tagalog speaker sounds natural. Keep the same pace and energy across all files.
Text-to-speech (TTS) is fine when scripts change often or you need fast updates. Use it for short utility lines like hours or holiday closings. A human voice is better when you want warmth and brand tone. Greetings, menus, and voicemail prompts sound more welcoming with a real voice.
Record in a quiet room. Put the mic 6–8 inches from the mouth, slightly off-axis to reduce breath noise. Speak at a steady level. Do not put music under the voice. Smile a little; it helps the tone.
Prepare files in mono. Use uncompressed WAV when your IVR supports it. If your system needs a specific sample rate or file type, follow the platform’s guide. Trim long silences at the start and end so calls don’t feel slow.
Test like a caller. Upload the files, then call from a mobile phone and a landline or a VoIP (internet phone) desk phone. Listen for hiss, room echo, or words that blur together. If any line is hard to catch on the first listen, rewrite and re-record it.
Bilingual IVR prompts without long menus
Offer language selection early, before the main menu. Do not repeat the full menu in both languages before the choice. Once the caller picks a language, keep both trees equal in depth and options so no one gets a worse path.
Common pairs include English/Spanish in the United States, English/Tagalog in the Philippines, English/Hindi or English/Bengali in India and Bangladesh, English/Urdu in Pakistan, and English/Thai in Thailand. Use what your callers expect rather than what your team prefers.
English/Spanish language prompt: “For English, press 1. Para español, oprima 2.”
Main menu (English): “For the front desk, press 1. For billing, press 2. To speak with a person, press 0.”
Menú principal (Español): “Para recepción, oprima 1. Para facturación, oprima 2. Para hablar con una persona, oprima 0.”
English/Hindi language prompt: “For English, press 1. हिंदी के लिए 2 दबाएँ.”
Main menu (English): “For service, press 1. For billing, press 2. To speak with a person, press 0.”
मुख्य मेनू (Hindi): “सेवा के लिए 1 दबाएँ. बिलिंग के लिए 2 दबाएँ. प्रतिनिधि से बात करने के लिए 0 दबाएँ.”
If you serve more than two languages, still offer a simple language pick first, then branch to equal, short menus. Avoid stacking three languages in one long greeting.
Keep paths short and measure what happens
Use schedules (time-of-day rules) so callers hear only the options that apply. During open hours, play the main menu. After hours or on holidays, play the after-hours message and send to voicemail or a specific on-call line if you use one. See how to set windows in schedule-based call routing.
Set your queue and voicemail as clean fallbacks. Let agents ring, then queue for up to 60–90 seconds. After that, send to voicemail. Avoid looping callers back to the start more than once.
Check your call analytics each week. Look at where callers hang up — which prompt or which menu — and which options they choose and how often. Also watch average call length by path and voicemail rate during hours versus after hours. Those clues tell you where prompts are unclear or menus are too deep. Run a few test calls each time you change a script. Update recordings when hours or routing change so the words match the path. You can build this whole flow on CallFlow with IVR menus, schedules, queues with hold music, voicemail, and real-time call logs and analytics.
For what to check and why it matters, see our guide on call analytics. If you’re mapping a larger inbound setup, this primer helps too: inbound call management.
Build this in your call platform today
You can finish this in about an hour. Map first, write tight lines, record clean audio, then set it up and test.
Sketch the menu on paper. Draw the greeting, language pick, main menu (3–5 options), one sub-menu if needed, and the after-hours branch. Mark where 0 goes.
Write scripts for each box. Use the copy-paste lines above. Keep one idea per sentence and put the action before the key.
Choose a voice and record. Use one speaker at a steady pace in a quiet room. Save mono WAV if your system allows and trim silences.
Create the IVR and upload files. Build the language pick and main menu. Point each option to the right target: front desk queue, billing line, or voicemail.
Add schedules for hours and holidays. Route to the main menu during open hours. After hours, play the short message and go to voicemail. In places with different weekends or holidays, match the local calendar.
Set ring and queue timers. Ring each target 20–25 seconds. Let the queue hold 60–90 seconds before voicemail. Add 0 as a fast path to a person during hours.
Record error and repeat prompts. Keep them short and clear: “Sorry, I didn’t get that…” Allow one repeat, then send to an agent or voicemail.
Test and confirm it works. Call from a mobile and a landline or a VoIP (internet phone) desk phone. Try each path, including after hours by forcing the schedule or testing off-hours. Check recordings, listen for clarity, and make sure 0 reaches a person during hours. Review early call logs to see option picks and any hang-ups. Invite a teammate to test and give feedback. Iterate.
If you want a fast way to put this in production, CallFlow gives you instant US toll-free and local numbers (plus several other countries), IVR menus, schedules, round-robin and priority routing, a queue with hold music, voicemail, call recording, and real-time analytics. Billing is usage-based from a prepaid wallet with no contract. You can sign up or contact us.
Frequently asked questions
Where in the menu should “talk to an agent” go?
Put “talk to an agent” in the top-level menu where callers expect it (many systems use 0 or say “agent”), not buried in a sub-menu. Offer it as one of three to five main choices, and include a fast path that always routes to a live queue or a designated target during business hours. After hours, route the same key to your after-hours message or voicemail so callers don’t loop.
How often should we update or re-record IVR prompts?
Re-record when content changes: hours, new services, language updates, or frequent caller confusion. Otherwise, review prompts on a regular cadence—every few months—to check clarity and tone. Use short text-to-speech lines for changing items like holiday hours, and reserve human recordings for greetings, menus, and voicemail to keep tone consistent across the set.
Should I put our business hours in the initial greeting?
Only state hours when they change how calls route. Say them if you send after-hours callers to voicemail or a different queue. If hours don’t affect routing, the extra line is noise and slows callers down. Instead, use a brief hours line inside an after-hours message or on a separate TTS prompt triggered by schedule rules.
What audio file format and settings do most IVR systems accept?
Use clean mono audio and uncompressed WAV files when your IVR supports them; trim silence at the start and end. Use a steady pace and consistent level across all files. Follow the platform’s specific file-type and sample-rate guide when required, and always test uploaded files from mobile, landline, and VoIP phones to confirm clarity on first listen.
How do I handle holiday or emergency closures in the IVR without rewriting everything?
Use your system’s schedule/time-of-day windows to swap which route or greeting is active on specific dates, and point callers to an after-hours or holiday message that explains the closure. For last-minute changes, use a short TTS line or a separate holiday audio file and switch the target or schedule—this avoids re-recording the whole menu while keeping callers informed.
From the team
CallFlow Engineering TeamTelecom engineering and support at CallFlow (ALERTSIO LLC)
The engineers and support staff who build and operate CallFlow's call-routing platform. We write from what we see running inbound routing for pay-per-call marketers, agencies and small businesses every day: routing rules, carrier behaviour, spam flags, and the configuration mistakes that quietly cost calls.
Ready to get started with CallFlow?
No subscription. Transparent usage billing. Per-number spam scores. Built for scale.
Create Free Account →