IVR Design Best Practices: Building Menus Customers Don't Hate

We've all suffered through bad IVR systems. Here's how to build one customers will actually use.

The Problem with Most IVRs

Traditional IVRs fail because they:

• Have too many nested menus (5+ levels deep)
• Use jargon customers don't understand
• Force callers to listen to all options before choosing
• Don't allow free-form speech input
• Make it hard to reach a live agent
• Don't remember context when transferring

Core Design Principles

1. Keep It Shallow

Limit menu depth to 2–3 levels maximum. If you need more, your IVR is too complex.

Bad: Main → Billing → Payment Methods → Credit Card → Update Card → Expiration Date

Good: Main → Update Payment Card [with all fields collected in one interaction]

2. Lead with the Most Common Requests

Analyze your call data. Put the top 3 reasons people call in the first menu tier.

Example:

• Press 1 for appointments (42% of calls)
• Press 2 for prescription refills (28% of calls)
• Press 3 for billing questions (18% of calls)
• Press 0 for the front desk (12% of calls)

3. Use Natural Language

Don't say "account servicing" when you mean "check your balance."

4. Enable Speech Recognition

80%+ of callers prefer speaking to pressing buttons. "Say 'appointments' or press 1."

5. Always Offer an Out

Every menu should include "Press 0 for an agent" or "Say 'agent.'" Don't make them listen to 5 minutes of menus first.

Self-Service Use Cases

IVRs excel at these tasks:

• Appointment scheduling and reminders
• Balance and payment collection
• Order status lookup
• Store hours and location info
• Prescription refills
• Simple FAQ answers

Avoid using IVR for:

• Complex troubleshooting
• Emotional or sensitive topics (complaints, disputes)
• First-time setup or onboarding
• Anything requiring judgment calls

Conversational IVR vs. DTMF

Traditional DTMF (push button):

• "Press 1 for English, 2 for Spanish"
• Simple, reliable, universally understood
• Best for simple routing or when speech recognition isn't viable

Conversational IVR (speech-enabled):

• "How can I help you today?"
• Collects information naturally
• Can handle free-form responses
• Requires NLU training but creates better experiences

Recommendation: Start with hybrid approach. "You can say 'appointments' or press 1."

Call Flow Best Practices

1. Greet briefly: "Thanks for calling ABC Company. For appointments, press 1..."
2. Authenticate early: Collect account number or phone number upfront if needed for routing
3. Confirm before acting: "You said you want to pay $150. Is that correct?"
4. Pass context to agents: If caller reaches an agent, transfer all collected data
5. Offer callback: "Current wait time is 8 minutes. Press 1 to hold, 2 for a callback."

Voice and Persona

• Use professional voice talent, not robot voices or the CEO's cousin
• Match your brand personality (warm and friendly vs. efficient and professional)
• Keep pace moderate — not too fast or too slow
• Use consistent voice across all prompts

Testing and Optimization

Before launch:

• Internal testing with employees
• External usability testing with 10–20 customers
• Load testing to ensure system handles peak volumes

After launch:

• Monitor completion rates by menu path
• Track "zero out" rates (people escaping to agents)
• Measure self-service containment
• Survey callers about their IVR experience
• A/B test menu wording and ordering

Modern IVR Features

Today's advanced IVR systems offer:

• Visual IVR: Send SMS with menu options or mobile app deep links
• Callback scheduling: "We'll call you back when it's your turn"
• AI-powered routing: Route based on sentiment, urgency, or predicted intent
• Omnichannel context: Remember if customer just chatted online
• Voice biometrics: Identify caller by voiceprint for fraud prevention

Choosing IVR Technology

Explore our IVR category for leading platforms.

Key questions to ask vendors:

• Cloud-based or on-premises?
• Does it integrate with our phone system and CRM?
• Speech recognition accuracy and language support?
• What's the process to update prompts?
• Can we A/B test call flows?
• Reporting and analytics capabilities?

---

Need help designing your IVR? Contact us for recommendations.