Asterisk IVR: IVR Guidance Link (Latest Versions)

A well-designed IVR should not trap callers in long menus. Instead, it should guide callers quickly to the right action: an agent, a queue, a callback option, or self-service information.

This concept is called an IVR guidance link — the logical routing that connects menu choices to meaningful business outcomes.

In modern Asterisk (PJSIP-based) deployments, IVR guidance is implemented entirely in the dialplan, making it flexible, scalable, and automation-friendly.

What Is an IVR Guidance Link?

An IVR guidance link is the routing decision behind each keypad option.

• Press 1 → Sales queue
• Press 2 → Support queue
• Press 3 → Voicemail or callback
• No input → Repeat or exit

Without proper guidance links, IVRs become confusing and customers hang up.

Core Principle of Good IVR Guidance

• Each option must lead somewhere useful
• Navigation should be simple and predictable
• Timeouts must still provide help
• No caller should reach a dead end

This transforms IVR from a menu into a customer journey system.

Basic IVR with Clear Guidance Links

[main-ivr]
exten => s,1,Answer()
 same => n,Background(custom/main-menu)
 same => n,WaitExten(5)

; Sales
exten => 1,1,Queue(sales)
 same => n,Hangup()

; Support
exten => 2,1,Queue(support)
 same => n,Hangup()

; Callback / Voicemail
exten => 3,1,Voicemail(1000@default,u)
 same => n,Hangup()

; Timeout → repeat menu once
exten => t,1,Goto(repeat,1)

exten => repeat,1,Playback(custom/please-choose-again)
 same => n,Goto(main-ivr,s,1)

This ensures:

• Every option routes somewhere meaningful
• Timeout still helps the caller

Linking IVR to Real Business Actions

Guidance links should reflect actual business workflow, not just technical routing.

• Sales → fastest available agent
• Support → queue with wait announcements
• Billing → recorded information or callback
• Emergency → priority routing

This alignment is what makes IVR effective.

Multi-Level IVR Guidance Structure

Larger organizations use hierarchical guidance:

Main Menu
 ├─ Sales Menu
 │   ├─ New Sales → Queue A
 │   └─ Existing Orders → Queue B
 └─ Support Menu
     ├─ Technical → Queue C
     └─ Complaints → Supervisor Queue

Each branch must still maintain clear exit or fallback paths.

Handling Invalid Input Gracefully

exten => i,1,Playback(pbx-invalid)
 same => n,Goto(main-ivr,s,1)

Never disconnect immediately on wrong key press. Always guide the caller back.

Timeout Strategy for Better Customer Experience

Recommended timeout flow:

1. Repeat menu once
2. Route to operator or queue
3. Fallback to voicemail if unanswered

exten => t,1,Goto(operator,1)

exten => operator,1,Queue(support)
 same => n,Voicemail(1000@default,u)
 same => n,Hangup()

Common IVR Guidance Mistakes

Too Many Menu Options

• Confuses callers
• Increases hang-up rate

Dead-End Routing

• Call disconnects without help
• No fallback to queue or voicemail

No Timeout Handling

• Caller stuck in silence

Best Practices for IVR Guidance Design

• Limit first menu to 3–5 options
• Always provide queue or operator fallback
• Repeat menu only once before routing
• Keep prompts short and human-recorded
• Test IVR using real external calls

Good IVR guidance reduces support load and improves conversion rates.

Business Impact of Proper IVR Guidance

• Faster customer resolution
• Lower abandoned call rate
• Better agent productivity
• Professional brand perception

IVR guidance is not just telecom logic — it is a customer experience strategy.

What Comes Next?

After understanding IVR guidance links, the next step is building:

• Full IVR configuration
• Advanced multi-level menus
• Looping IVR flows
• Database-driven IVR routing

Key Takeaway

An IVR is only as good as the guidance it provides. Every key press must lead to a clear, helpful, and reachable destination.

When IVR guidance is designed correctly, Asterisk becomes not just a phone system — but a structured customer navigation platform.