How to Write Better IVR Greetings and Voice Prompts

A good IVR greeting helps a caller make the right choice quickly. It identifies the business, explains only what the caller needs at that moment, uses predictable keypad options, and gives a clear path when the caller is unsure. It does not try to advertise every service or reproduce the company website. For a small business, the strongest prompt is usually short, spoken at a natural pace, and tested by people who did not write it. The words, recording quality, menu design, and routes behind the keys must all agree. MYLO can help a business organise and review an IVR proposal, but the business owns the wording, customer experience, approvals, and ongoing accuracy. A prompt is successful only when real callers can hear it clearly and reach the intended destination.

Start With the Caller’s Immediate Job

Most callers arrive with a simple purpose: speak to sales, ask for support, confirm an appointment, check an order, or reach a known person. The greeting should help complete that purpose with the least effort. Internal organisation charts are rarely a useful script. A caller may not know whether a billing question belongs to accounts, customer service, or administration.

Before writing, list the three or four reasons people call most often. Put frequent, urgent, and clearly understood choices first. Combine routes that lead to the same people. If almost every caller needs a receptionist, a long menu may add friction without improving routing. The article What Is an IVR, and Does a Small Business Need One? helps with that earlier decision.

Write a Useful Welcome Message

The opening should confirm that the caller reached the correct organisation. A practical pattern is: “Thank you for calling [business name].” Add a location or brand only when two operations could easily be confused. Avoid stacking slogans, website addresses, opening hours, and promotional offers before the menu. A caller who already chose to phone needs direction more than marketing.

If calls are recorded, if unusual service conditions apply, or if the office is closed, the required notice should be placed where callers hear it before the relevant action. Keep operational notices separate from the permanent greeting when possible. That makes temporary information easier to remove and reduces the chance of leaving an outdated message live.

Make every sentence earn its place

Read the script aloud with a timer. Remove greetings repeated by a submenu, explanations that belong on a website, and statements that do not change what the caller should do. A short pause between the business name and first option is useful; a long musical introduction is not. Spell difficult names phonetically for the speaker rather than hoping the recording session fixes pronunciation.

Keep Options Concise and Consistent

State the destination before the key: “For sales, press 1.” That lets the caller recognise the relevant word early. Use the same structure for each option. Do not alternate between “press,” “select,” “dial,” and “enter” unless the action really changes. Consistency lowers listening effort.

Numbering should remain stable across levels. If zero reaches a person in the first menu, it should not suddenly mean “repeat” in a submenu. Avoid making keys resemble priorities unless that is intentional: callers should not assume option 1 receives faster service than option 3. Keep commonly expected escape choices, such as zero for reception or star to return, consistent and announce them where available.

Too many choices are difficult to remember. A compact menu with a clear fallback usually performs better than a list of every employee and service. When the structure genuinely needs layers, review How a Multi-Level IVR Works and limit depth so callers do not become trapped.

Design for Real Listening Conditions

Callers may be outdoors, driving hands-free, using a low-cost mobile connection, or surrounded by office noise. Write for the ear, not the page. Prefer common words, short sentences, and one action per option. Say “appointments” instead of an internal department title. Avoid abbreviations that sound similar over a phone channel.

Give callers enough time to act, but do not insert long silences that make the call seem disconnected. Decide what happens after no input and after an invalid key. A useful response briefly explains the problem, repeats the available choices, and eventually offers a person, voicemail, or safe end state. Endless repetition is not a customer experience.

Protect Recording Quality

A strong script can still fail through weak audio. Record in a quiet, soft-furnished room with a consistent microphone position. Use one approved speaker or a well-managed professional voice across related prompts so the menu sounds coherent. Record at a steady conversational pace, leaving clean silence at the beginning and end for editing.

Telephony audio has narrower bandwidth than studio playback. Test the final file through the actual call path rather than approving it through laptop speakers. Listen for clipped first words, harsh “s” sounds, volume jumps, background hum, and names that become unclear after conversion. Music and effects can mask speech and should not compete with instructions.

Maintain a prompt inventory

Give each approved prompt an owner, purpose, script, language, recording date, and route. Keep the source recording available where the business’s policy permits. When a department name, operating hour, or key changes, search the inventory for every affected prompt. Updating the main greeting while leaving a contradictory submenu is a common maintenance failure.

A Practical Example

A repair company initially records: “Welcome to Excellent Home and Commercial Appliance Solutions, serving the city since 2008. Please listen carefully because our menu has changed. For all refrigerator, washing machine, air-conditioning, installation, warranty, billing, new purchase, complaint and other matters…” Callers must remember a long list before hearing a key.

After reviewing actual call reasons, the business uses: “Thank you for calling Excellent Appliance Service. For a new repair booking, press 1. For an existing job, press 2. For billing, press 3. To speak with reception, press 0.” Each choice reaches a staffed route or defined fallback. The company places seasonal closure information in a separate time-based message and tests mobile calls to every option.

The shorter script does not solve capacity by itself. If option 2 reaches an overloaded team, the business also needs a queue, overflow, voicemail, or callback process. Prompt writing and route design must be tested as one experience.

Limits and Responsibilities

• The business approves names, claims, notices, languages, hours, and escalation choices.
• The telecom provider supplies the incoming number and trunk service; MYLO does not act as the carrier.
• MYLO may guide a supported proposal, while authorised people approve consequential changes and Asterisk executes the call path.
• A clear prompt cannot compensate for unavailable agents, unstable connectivity, insufficient channels, or an unowned voicemail box.
• Accessibility, customer notice, recording, and sector-specific obligations remain customer responsibilities requiring appropriate professional guidance.

IVR Prompt Checklist

• Does the first sentence identify the right business?
• Are the most common caller goals represented in plain language?
• Can the menu be understood without seeing an organisation chart?
• Are key numbers, escape actions, and wording consistent?
• Are invalid input, no input, busy, closed, and failed destinations defined?
• Has the final audio been tested on real external calls?
• Does an owner know when and how to update each prompt?

Next, consider whether the same menu genuinely needs more than one language in Should Your IVR Offer Multiple Languages?. For a supported MYLO deployment, bring the approved wording, destinations, schedules, and fallback decisions to the configuration discussion. Custom integrations or unusual routing should be scoped separately with MyLineHub.

Test Comprehension, Not Just Sound

Ask several people who did not write the script to call without seeing the menu diagram. After one listen, ask which key they would choose for realistic tasks. Note hesitation, incorrect choices, repeated prompts, transfers, and abandoned calls. A recording can sound polished yet fail because the labels do not match the words customers use.

Test during open and closed hours, from mobile and fixed networks where relevant, and through every submenu. Confirm that a key pressed near the end of a prompt is accepted, that invalid input does not create a loop, and that zero or another escape key works exactly as announced. Re-test after changing a prompt, destination, schedule, or provider configuration.

Use outcomes to improve the script

Review which options callers select, where they repeat or abandon, and how often agents transfer calls after selection. These signals can reveal unclear language or a route that no longer reflects the organisation. Do not interpret a high selection count alone as success: callers may be choosing the least confusing option. Pair call evidence with agent feedback and a small sample of customer feedback.

Maintain a simple approval history containing the script version, owner, date, route, recording file, and test evidence. This makes later changes reviewable and prevents an old recording from returning accidentally. The purpose is not bureaucracy; it is ensuring that the voice customers hear matches the route the system executes.