Menu Repeat: replaying the menu

Sometimes a caller misses the options the first time, maybe a kid was talking or the line crackled. The Menu Repeat setting decides how many extra times your phone menu plays before giving up. A Call menu that never repeats can feel unforgiving, while one that loops forever traps people.

What Menu Repeat controls

Menu Repeat is the number of times the menu plays after the first time when no valid choice is made. The default is 1, so the greeting plays once, and if the caller stays silent or presses nothing useful, it plays one more time. That gives a second chance without dragging the call out.

This works alongside the wait window. After the greeting, the menu pauses for the timeout you set and listens for a DTMF tone, the beep a phone makes on a key press. If nothing valid comes in within that window, the repeat count is consumed and the menu plays again.

How repeats interact with timeout

flowchart TD
  A[Play menu prompt] --> B{Valid key in time}
  B -->|Yes| C[Route to option]
  B -->|No| D{Repeats left}
  D -->|Yes| E[Decrement and replay]
  E --> A
  D -->|No| F[Run TIMEOUT action]
  F --> G[Send to agent or hangup]

Once the repeats run out, the menu follows the TIMEOUT option you defined. That is where you decide the fate of an unresponsive caller, often a route into an Ingroup so a person can help, or a hangup if the line has clearly gone quiet. This is the core of a polite IVR (interactive voice response).

Repeat versus invalid handling

It helps to separate two different situations. A repeat is what happens when the caller does nothing at all, no key press inside the timeout window. A wrong key press is a different event, handled by the invalid prompt and its own options. The two can stack: a caller might press a bad key, hear the invalid prompt, then go silent, which consumes a repeat. Thinking about them as separate triggers makes your menu easier to reason about.

Because repeats and timeouts work together, the length of your greeting matters too. A long, wordy greeting eats into the caller's patience, so each replay costs more goodwill. Trimming the greeting to the essentials means a repeat is cheap and a second listen is genuinely useful rather than tedious.

A sensible default

For most teams, the default of 1 is the right call. The caller hears the menu twice in total, which covers an honest miss without testing their patience. If your greeting is long, you might keep repeats low and lean on a clear timeout route instead. The only time a higher count makes sense is a menu where callers genuinely need a moment to find some information before they can choose, and even then two replays is plenty.

Whatever count you settle on, make sure the final destination is a real one. A repeat that runs out and lands the caller in dead air is worse than no menu at all, so confirm the timeout route sends them somewhere a person can help or, at the very least, plays a clear closing message.

To see how the repeat fits the bigger inbound picture, read our inbound call handling guide. And when you are ready to build the queue these menus hand calls to, our piece on creating an inbound group to take calls walks you through it.

Prefer to skip the install and tune menus straight away? Our managed VICIdial hosting hands you a live box in under a minute.