Every caller who reaches your phone system meets your IVR script before they meet your company. Most IVR scripts were written by committees, translated literally, and never tested — and callers punish them with hang-ups and zero-presses.
Good IVR script writing is a discipline: menu structures callers can actually navigate, prompt wording that reduces confusion, and graceful handling of every edge case. This guide covers the best practices.
Key Takeaways
- Write for stressed, distracted callers — not the ideal user in a conference room.
- Keep menus shallow (max 4 options per level) and always offer repeat and zero-out options.
- State the action before the keypress: 'For billing, press 2' — never 'Press 2 for billing.'
- Time every prompt: callers should reach a human or resolution within 60 seconds.
- Test with real first-time callers and measure hang-up rates, not just colleague opinions.
The Caller's Mindset
Your caller is not sitting attentively with a notepad. They're driving, cooking, annoyed about a bill, or juggling a toddler — calling you is already friction, and your IVR is more of it. Every second of confusion converts directly into frustration, hang-ups, and 'representative!' shouting.
Design for cognitive load accordingly. Callers can hold about 3–4 options in working memory while listening — more than that and earlier options evaporate. They can't re-read a prompt they missed. They're primed to distrust the system from past bad experiences with other companies' phone trees.
The goal isn't a clever menu; it's the fastest path to resolution. Every IVR decision should be tested against one question: does this get the caller where they need to go with minimum effort? If not, simplify.
Menu Structures That Work
Pick the structure for the call volume pattern:
| Structure | When to use | Max options | Example |
|---|---|---|---|
| Flat menu | Few departments | 4–5 | Small business |
| Two-level tree | Many departments | 4 per level | Enterprise |
| Intent routing | Varied reasons | 3–4 intents | Support lines |
| Direct-to-human | High-value callers | — | VIP/sales lines |
| Time-based | Hours vary | — | After-hours routing |
Put the most-called option first — check your call data, don't guess. Keep the total path under three levels deep; deeper trees have exponentially worse completion rates. And always, always provide escape hatches: repeat the menu, return to the previous level, and reach a human.
Prompt Wording: The Details That Matter
State the action before the keypress: 'For billing inquiries, press 2.' Leading with the action lets callers press the moment they recognize their need; leading with the number ('Press 2 for billing') forces them to hold the number while waiting for the label — measurably worse.
Use plain language, not internal jargon. Callers don't know your department names — 'customer success operations' means nothing; 'help with your account' means everything. Write prompts from the caller's vocabulary outward.
Keep prompts short: under 10 seconds per menu level, under 5 for confirmations. Cut every word that isn't load-bearing. 'Please' survives (politeness matters); 'we're delighted to help you today' does not. Read each prompt aloud and time it — then cut 20%.
Greetings, Holds, and Goodbyes
The greeting sets the tone: company name, one-line orientation, then the menu — in under 15 seconds. 'Thank you for calling Acme. For sales, press 1; for support, press 2.' No mission statements, no menu-change announcements (nobody cares), no 'your call is important to us' (it's demonstrably not, if they're in a queue).
Hold messaging should inform, not soothe. Tell callers their queue position and expected wait honestly; offer callback options; never loop the same 20-second message — vary it or go silent with periodic updates. Nothing breeds rage like the seventh repetition of smooth jazz plus platitudes.
End calls cleanly: confirm what happened ('your payment of $50 is scheduled'), state next steps if any, and close warmly but briefly. A good goodbye is 10 seconds. And always offer the survey opt-in after resolution, never before — asking for feedback from someone still stuck is insulting.
Frequently Asked Questions
How many options should an IVR menu have?
Maximum four per level — callers can hold about 3–4 options in working memory while listening. More options cause earlier ones to be forgotten. Keep total depth under three levels, put the most-called option first, and always offer repeat and human-escape options.
Should the action or the number come first in prompts?
The action: 'For billing, press 2.' Callers press the moment they recognize their need. Leading with the number forces them to hold it in memory while waiting for the label — measurably worse for completion rates.
How long should IVR prompts be?
Under 10 seconds per menu level, under 5 for confirmations, greeting under 15 seconds total. Read each prompt aloud, time it, then cut 20%. Every non-load-bearing word is friction for a stressed caller.
What's the biggest IVR script mistake?
Writing for the ideal user instead of the stressed, distracted real caller — deep menu trees, internal jargon, long-winded greetings, and no escape to a human. Test with real first-time callers and measure hang-up rates.
How should hold messages be written?
Inform, don't soothe: state queue position and honest wait times, offer callbacks, and vary the message or use periodic updates instead of looping one recording. Never play 'your call is important to us' to someone waiting 20 minutes.
Related Guides
- How to Write Scripts for AI Voiceovers
- Text-to-Speech API Guide for Developers
- AI Voice Credits Explained
The fastest way to learn is to do. Try SynVoice free and turn your first script into a finished voiceover today.