IVR Script Generator and Examples
Write an IVR phone menu script from your options, hours and after-hours routing. Built for support teams; drafted by a model, so read it before anyone records it.
The phone menu is the first thing a customer hears and the last thing anyone on the team wants to rewrite. So it drifts. An option points at a queue that no longer exists, the hours are a year old, and after 6pm callers get the same greeting as at noon and then silence. Nobody owns it, so nobody fixes it, and the abandon rate on the line quietly carries the cost.
This tool writes the script from what you give it: your business, the menu options in the order you want them, your hours, and what should happen when nobody is there. It returns a greeting, the numbered menu, an invalid-entry prompt and an after-hours branch, in the tone you pick. The model reads your input once and nothing is stored beyond a short cache of the result.
This ran once, on one input. The product runs on your whole site, every conversation.
Write the script, then hear an agent answer the line — start freeExample: IVR script for a B2B SaaS support line
Thank you for calling Northwind Software support. Please listen to the following options. For help with an existing account or a technical question, press 1. For billing, invoices or plan changes, press 2. For a new sales inquiry, press 3. To speak with a member of the team, press 0 or stay on the line. To hear these options again, press 9. Invalid entry: Sorry, that is not a valid option. Please try again, or press 0 to reach a person. After hours: Thank you for calling Northwind Software. Our support team is available Monday to Friday, 8am to 6pm Eastern. For answers now, visit help.northwind.com. If you are reporting an outage, press 1 to reach the on-call engineer. Otherwise, leave your name, company and a callback number after the tone, and we will return your call on the next business day.
What each input means
- 01
Business name and what it does
One line, as a caller would understand it. The name goes in the greeting; the description keeps the wording on-topic so a software support line doesn't get a script written for a clinic.
- 02
Menu options, one per line
In the order you want them read. Put the highest-volume reason first and a route to a person last. Four or five is the practical limit — past that, callers forget option one by the time they hear option six.
- 03
Business hours
With the timezone. The script reads them out in the after-hours branch and, if you have several sites or regions, it's the one line callers use to decide whether to wait or hang up.
- 04
What happens after hours
Take a message, point to the help center, route outages to an on-call line — whatever is true today. Leave it blank and the script offers voicemail and the hours, nothing more.
- 05
Tone
Warm adds a sentence of reassurance; Professional is neutral and slightly formal; Brief cuts everything that isn't an instruction. For a support line that takes hundreds of calls a day, Brief is usually right.
Questions about this tool
Short, ordered by volume, and always one press from a person. The whole menu should read in under 30 seconds. Say the option before the number ("For billing, press 3") so the caller knows what they're choosing before they hear the key. Cut anything a caller can't act on — "your call is important to us" delays every caller and helps none of them.
Voicemail greeting generator
The after-hours, on-hold and holiday messages the menu points at.
After-hours call calculator
How many calls land outside your hours, and what that branch costs you.
What happens when an AI phone agent doesn't know the answer?
The behaviour to test before an agent replaces the menu.