IVR keypress does nothing: debugging call-menu options

A caller hears your greeting, presses 1 for sales, and the call just sits there or hangs up. The phone menu, called a Call menu (sometimes labelled IVR (interactive voice response), the automated menu that asks callers to press a number), is taking the keypress and doing nothing useful with it. This is almost always a configuration problem, not a broken phone. Here is how to track down which setting is swallowing the press.

First, confirm the menu is even reading digits

The keypad tone a caller sends is called DTMF (the beep your phone makes when you press a key). If the menu never reacts, the first thing to check is whether the prompt is letting the caller interrupt at all. A prompt filename with NOINT placed in front of it tells the system not to allow a key press during that message, so any digit the caller sends is ignored until the prompt finishes. Remove NOINT if you want callers to press early, or just have them wait for the prompt to end.

Next, look at the Menu Timeout. This is the number of seconds the menu waits for a digit after the prompt plays. Set it to zero and there is no wait time at all, so a caller pressing a key a moment too late gets nothing. Give it a few seconds of breathing room.

Check that the option actually exists

Every digit a caller can press needs its own option row. The Option Value field holds the key the caller presses, with valid choices being 0 through 9, star, pound, and A through D. If you defined a prompt that says press 1 for sales but never created an option row with the value 1, the press has nowhere to go. There are also two special rows worth knowing: TIMEOUT decides what happens when the caller presses nothing, and INVALID decides what happens when they press a key you did not define.

For each option you do define, the Option Route tells the call where to go. Options include sending the call to another menu, to an inbound group, to a specific phone, to voicemail, or to a hangup. If the route is set but the route value is blank or wrong, the press registers but the call lands nowhere. A common slip: routing an option to an Ingroup (the inbound queue that holds callers until an Agent is free) but leaving the in-group settings such as the handle method unset, so the call never queues.

How a keypress flows through the menu

flowchart TD
  A[Caller hears prompt] --> B{Keypress allowed}
  B -->|NOINT set| C[Press ignored]
  B -->|allowed| D{Option row exists}
  D -->|no| E[Run INVALID route]
  D -->|yes| F{Route value set}
  F -->|no| G[Call lands nowhere]
  F -->|yes| H[Send call to route]
  H --> I[Ingroup or phone or menu]

Turn on key-press logging to see the truth

If you still cannot tell what the caller pressed, enable Log Key Press on the menu. With it on, the digit the caller sent gets recorded, so you can confirm whether the press arrived at all. If logging shows a 1 came in but the call went nowhere, your problem is the option row or its route, not the carrier or the caller's phone. If no digit shows up at all, the issue is upstream: NOINT, a zero timeout, or the call never reaching this menu. You can compare against your other routing in the inbound call handling guide at our VICIdial inbound call handling guide.

One more thing to rule out: Menu Time Check. If a Call Time is attached and time-of-day restriction is on, the menu can refuse a press outside business hours. That is by design, but it surprises people testing at night. When the menu routes to a queue, it helps to understand how a queue differs from an outbound group, which we cover in what a VICIdial inbound group is.

Most keypress problems come down to a missing option row, a blank route value, or NOINT blocking the press. Walk those three in order and you will usually find it in a couple of minutes. If you would rather skip the server setup entirely, our managed VICIdial hosting gets you a working dialer in under a minute.