A good IVR script does three quiet things at once: it gets the caller to the right place quickly, sets honest expectations about wait time, and always gives them a way out. Get those right and callers feel looked after before they even speak to anyone. Get them wrong and you drive abandonment, misroutes, and frustration.
Below are practical, copy-and-adapt IVR script examples for the most common scenarios, followed by the design rules that make them work — and a free tool to build and test your own flow end to end.
IVR Script Best Practices (Read This First)
Before the templates, the rules that separate a good IVR script from a frustrating one:
- Keep menus to 3-5 options. If you need more, split into sub-menus rather than a long list callers can't remember.
- Lead with the most common reasons customers call. Put the top one or two options first — most callers never need the rest.
- Keep the greeting under ~30 seconds. Including the menu. If it runs long, cut options, not clarity.
- Say the option before the number. "For billing, press 1" is easier to follow than "Press 1 for billing" — callers listen for their reason, then the key.
- Always offer an exit. A way to reach a human or repeat the menu. Never trap the caller.
- Set honest wait expectations. If there's a queue, say so — and offer a callback.
- Prune ruthlessly. Review after 90 days and remove options chosen by fewer than ~2% of callers.
Tip: These scripts are written for a traditional menu-driven IVR. If you're moving to conversational or agentic AI (where callers just say what they need), see our guide on designing self-service for the AI era — the principles carry over, but the prompts change.
1. Welcome Greeting Script
The first thing every caller hears. Keep it short, branded, and immediately useful.
"Thank you for calling [Company Name]. Your call is important to us. To help us direct your call, please choose from the following options."
2. Main Menu Script
The core routing menu. Note the "option before number" phrasing and the always-available exit.
"For questions about an existing order, press 1. For billing and payments, press 2. For technical support, press 3. To speak to a member of our team, press 0. To hear these options again, press 9."
3. After-Hours / Closed Script
Played outside opening hours. Be clear about when you'll be back and offer a self-service or message option.
"Thank you for calling [Company Name]. Our office is currently closed. Our opening hours are Monday to Friday, 9am to 5pm. You can find answers to common questions at [website], or leave a message after the tone and we'll call you back on the next working day."
4. Hold / Queue Script
Honesty here reduces abandonment. Acknowledge the wait and offer an alternative.
"All of our agents are currently helping other customers. Your estimated wait time is [X] minutes. If you'd prefer not to wait, press 1 and we'll call you back without losing your place in the queue."
5. Callback Offer Script
One of the highest-impact additions to any IVR — it turns dead hold time into a good experience.
"We can call you back when an agent is available, so you don't have to wait on hold. To request a callback, press 1 and we'll confirm the number to reach you on."
6. No-Input / No-Match (Error Handling) Scripts
What plays when the caller says nothing or the system doesn't understand. Keep it calm and helpful, never blaming.
"Sorry, I didn't catch that. For billing, press 1. For support, press 2. To speak to our team, press 0."
"I'm still having trouble. Let me connect you to a member of our team who can help. Please hold."
7. Authentication / Verification Script
When you need to identify the caller before sharing account details.
"To access your account securely, I'll need to verify your identity. Please enter your account number using your keypad, followed by the hash key."
Security note: Verification deserves careful design. See our complete ID&V module blueprint for a reusable, secure approach — and why voice biometrics alone is no longer enough.
8. Closing / Call-End Script
"Thank you for calling [Company Name]. If you need anything else, we're here Monday to Friday, 9am to 5pm. Have a great day."
Design and Test Your IVR Script — Free Tool
Writing the scripts is the easy part. The hard part is assembling them into a flow that routes correctly, handles every error path, and doesn't trap callers — then testing every route before you go live.
That's exactly what our free IVR Design Tool is built for. Unlike generic diagramming tools, it's purpose-built for IVR: drop in Play Prompt and Recognition nodes, write your script wording directly into a central prompt table, connect the routing, and it automatically generates a test plan covering every path through your flow. There's even a CX Simulator that renders each journey as a System/Customer transcript so you can hear how the script actually flows.
Try it: Paste the scripts above into the IVR Design Tool, connect the nodes, and generate a test plan for your whole IVR in minutes — free, in your browser, nothing to install.
Frequently Asked Questions
What is an IVR script?
An IVR script is the set of spoken prompts and menu options a caller hears when they reach an interactive voice response system. It covers the welcome greeting, menu choices, hold and callback messages, error handling, and closing messages, and defines how callers are routed to the right place.
How many options should an IVR menu have?
Keep top-level menus to three to five options. If you need more, use a second layer of sub-menus rather than a long list. Short, tested menus reduce misroutes and lower average handle time.
How long should an IVR greeting be?
Keep the main greeting and menu under about 30 seconds combined. If the script runs long, cut options rather than clarity, and lead with the most common reasons customers call.
Should I use a professional voiceover for my IVR?
A consistent, professional voice — human or a high-quality text-to-speech voice — makes a measurable difference to how callers perceive your brand. Whatever you choose, keep it consistent across every prompt so the experience feels seamless.
Conclusion
Great IVR scripts are short, honest, and always give the caller a way out. Use the templates above as a starting point, tailor them to your brand voice, and prune relentlessly based on what real callers actually choose. Then assemble and test the whole flow before go-live — because a script that reads well on paper can still break in production if the routing and error paths aren't right.
Ready to build it? Design and test your full IVR flow with the free IVR Design Tool, and see our Amazon Connect best-practice guide if you're building on Connect.