How to write a professional IVR script for your phone menu

A professional IVR script guides callers to the right department in under three menu options and never sounds like a robot reading a manual. This guide walks through the exact steps to write, test, and record an IVR script that works for German, Austrian, and Swiss businesses in 2026.

Why this matters

Callers decide whether a business sounds competent within the first 10 seconds of the phone menu. A cluttered IVR script with five nested options and jargon-heavy phrasing pushes callers to hang up or mash "0" until a human answers — and every mashed "0" is a routing failure your team pays for in wasted transfers.

A tight IVR script does the opposite: it routes callers correctly on the first try, sounds like a real person greeting a real business, and reduces average call handling time. Getting the words right before you record them is the difference between an IVR system that saves staff time and one that generates complaints.

What you'll need

• A current list of departments or call reasons, ranked by call volume
• Your average call data for the last 3-6 months, if available, to prioritize menu order
• A style reference: one sentence describing your brand's tone (formal, warm, brisk)
• A script template or plain document to draft in before recording
• A professional voice recording partner — TelefonSounds works with over 100 professional speakers across Germany, Austria, and Switzerland with 48-hour turnaround once your script is final
• A stopwatch or phone timer to read scripts aloud and check pacing

The steps

1. Map every call reason before you write a word

List every reason someone calls your business, then rank them by volume, not by internal org chart. This accomplishes one thing: it puts the most common request first in the menu, which is where callers expect it and where they'll wait the least.

Skipping this step is the single biggest cause of bad IVR scripts — companies build menus around their departments instead of their callers' actual needs. Pull whatever call log or CRM data you have from the past 3-6 months and count the reasons. If sales calls outnumber support calls 3-to-1, sales goes first.

Common mistake: ordering the menu alphabetically by department name instead of by call frequency.

2. Cap the menu at three options

Write no more than three choices per menu level. Anything beyond three forces callers to hold three or four items in short-term memory while still listening — and most give up before option four finishes.

If you genuinely have more than three call reasons, build a second-level submenu rather than a longer first menu. A caller who hears "press 1 for sales, 2 for support" and then a relevant submenu feels routed correctly; a caller who hears six options up front feels like they've called an automated maze.

Common mistake: adding a fourth or fifth option just in case a rare call type comes through.

3. Draft the greeting in one breath

Write the opening greeting as a single sentence a person could say in one breath, roughly 6-8 seconds when read at a natural pace. State the company name, thank the caller, and move straight into the first menu option — skip mission statements and marketing lines.

This matters because every extra second before the first useful option is a second the caller spends deciding whether to hang up. A greeting like "Thank you for calling Acme, press 1 for sales, 2 for service, or 3 to speak with our office" does the job in one line.

Common mistake: opening with a paragraph about business hours, holiday closures, or company history before the caller hears a single menu option.

4. Write for the ear, not the eye

Read every line aloud as you draft it, not after. Spoken language uses shorter sentences, fewer commas, and no subordinate clauses — a sentence that reads fine on a screen often sounds tangled coming out of a speaker.

Replace written-language habits like "in order to" with "to," cut every sentence that has more than one comma, and avoid stacking two instructions in one line. Split a doubled instruction into two clean options instead.

Expected outcome: a script that takes under 25 seconds to read aloud for a three-option menu, greeting included.

5. Build in a fallback path

Every menu needs an explicit way out — "press 0 to speak with a representative" or "stay on the line to be connected." A script with no fallback traps callers who don't fit any listed option, and those are often your highest-value calls: complaints, urgent requests, or first-time customers who don't know which department they need.

Place the fallback at the end of the option list, never first, so it doesn't compete with the routed options for attention.

Common mistake: burying the fallback inside a submenu three levels deep, where frustrated callers never reach it.

6. Match tone to your brand, then hand it to a professional voice

Decide in one sentence how your business should sound on the phone — formal and precise, warm and conversational, brisk and efficient — and write every line to that standard. A law firm's IVR script and a fitness studio's IVR script should read nothing alike even if the menu structure is identical.

Once the script is locked, record it with a professional voice actor rather than text-to-speech if brand tone matters to your callers. Verdict: professional recording wins for any business where the phone is a first impression — TelefonSounds pairs scripts with speakers matched to the requested tone and delivers the finished recording in 48 hours.

7. Time-test the full script before recording

Read the entire script aloud, start to finish, with a stopwatch running. A well-scoped three-option IVR script should run 20-30 seconds from greeting to last option; anything over 45 seconds needs cutting, not faster reading.

This step catches problems silent proofreading misses — awkward phrasing, options that sound identical when spoken back to back, and pacing that feels rushed or padded. Fix the script, not the delivery speed.

Common mistake: solving a script that's too long by asking the voice talent to read faster instead of cutting words.

Troubleshooting

Callers keep pressing 0 immediately. The menu options don't match what callers actually need — pull real call reason data and rebuild the menu around it, not around department names.

The script sounds fine written but awkward recorded. You proofread on screen instead of reading aloud. Rewrite any sentence with more than one comma and read every draft out loud before it goes to recording.

Callers hang up mid-menu. The greeting or menu runs too long. Cut the script until the full read, greeting to last option, lands under 30 seconds.

One department gets flooded with misrouted calls. That option's wording is ambiguous next to another option. Read both options back to back and check whether a first-time caller could confuse them.

The recording doesn't match the script's intended tone. The brief given to the voice talent was too vague. State tone explicitly — formal, warm, brisk — as part of the recording request, not left to interpretation.

International or bilingual callers get lost. If a meaningful share of callers speak a second language, script and record a parallel version rather than a mid-menu language switch, which adds length to every call.

Tools and resources

• Call log or CRM export for the last 3-6 months of call reasons
• A stopwatch or phone timer app for pacing checks
• A shared document for script drafts and revision tracking
• TelefonSounds for professional voice recording once the script is finalized, with speakers available for German, Austrian, and Swiss business tone

What to do next

Once your IVR script is drafted and time-tested, the next move is recording it with a voice that matches your brand tone rather than defaulting to a generic system voice. A script that reads well on paper still needs delivery that sounds human — pacing, warmth, and clarity carry as much weight as the words themselves. Businesses updating their phone system in 2026 are increasingly pairing a written IVR script with a matched hold-message and voicemail recording so every touchpoint on the call sounds consistent.

FAQ

One last thing

The menu order matters more than the wording. A perfectly written script with sales listed as option three, behind two rarely-used departments, will still generate misrouted calls and frustrated hang-ups in 2026 — pull the call volume data first, write second.