Nielsen Norman Group notes that most callers want to speak with a live person. An IVR earns its place when it gets them to the right one faster. The steps below follow one call from the first seconds to the moment an agent says hello.
The first ten seconds
After an expert review of phone trees from 22 organisations, the group published 16 usability guidelines. Several apply before the first menu plays.
Offer language first. If you serve callers in English and Swahili, that choice should come at once, so nobody sits through audio they cannot follow. Cut advertising and long welcome messages too. A caller trapped in a recording cannot skip a promotion, and it only delays their reason for calling. Record a real person's voice rather than a robot voice.
The menu
Limit each menu and submenu to four or five choices, and make the wording of each option clearly different. Two options that both mention "account" force a guess.
Say the task before the key: "For delivery updates, press 1" works better than "Press 1 for delivery updates", because the caller can decide whether the option applies before they need to remember a number. Let regular callers press a key without waiting for the prompt to finish. Confirm each selection with a tone or by repeating the choice, since people often press keys mid-sentence.
Decide on your keys once and keep them everywhere. Nielsen Norman Group suggests star to repeat the options, and every level should offer a way back. If you accept voice input, always keep a keypad option as well.
Write the menu from your call reasons, not your organisation chart. Pull a month of call notes, list the top reasons, and let those decide the first menu. Anything rare can wait for a person.
The route to a person
Nielsen Norman Group's recommendation is direct: let callers press 0 for a live representative, and if a caller lets the menu play three times, connect them to someone instead of hanging up. A silent caller may be confused, using an old handset, or in need of help the menu never anticipated.
Treat these as rules for your flow:
- Pressing 0 works at every level, and the menu says so early.
- No path ends in a disconnect while your lines are open.
- A failed entry, such as a wrong account number, gets one retry and then goes to a person.
Holding is part of the route. Give updates on the expected wait about every 1.5 to 2 minutes, and offer to keep the caller's place and call back. For a local yardstick, the Communications Authority of Kenya's consumer protection guidelines set licensed service providers a 20/80 principle for answering customer calls, 20 seconds for 80 percent, and that period includes hold time where an IVR manages the queue. Those guidelines address licensees, but the way they count is useful: time in the queue is still the caller's time.
The handoff
Few things annoy a caller more than keying in an account number and being asked for it again. The data has to travel with the call, and that takes planning.
List what the IVR knows at the point of transfer and decide what the agent needs:
- Calling number and language chosen.
- Menu path, in plain words such as "Delivery, then missed delivery".
- Any reference the caller entered, and whether it matched a record.
- Whether identity checks passed, failed or were never attempted.
- Number of failed attempts or menu repeats, which tells the agent to start with an apology.
Contact center platforms treat this as a standard pattern. Amazon Connect's documentation calls showing that information at the start of a contact a screen pop, and it exists so agents have context before the conversation begins. Test yours by making a real call and checking what reaches the agent's screen, including after a transfer.
Pass only what the agent needs. Kenya's Data Protection Act expects personal data to be limited to what is necessary for the purpose. Agents should open with what they can see: "I can see you are calling about a missed delivery on order 4471. Is that right?" That one line tells the caller the system listened.
Apply the same rule to internal transfers. A warm transfer with a spoken summary is better than a cold one, and any second agent should see the first agent's notes.
Out of hours
Closed does not have to be a dead end. Nielsen Norman Group suggests a recording that gives your opening hours, relevant web pages and emergency contacts. Add the fastest alternative you actually staff. That might be a WhatsApp number or website chat that someone reads in the morning. Be honest about the response time.
If a problem can be urgent, such as a lost card, a safety issue or a power fault, give it a real route that works overnight. Update the recording whenever hours change, including public holidays.
If your IVR calls customers
Outbound automation carries extra rules. Kenya's 2010 consumer protection regulations under the communications law make it an offence to use automated calling systems without human intervention for direct marketing without the subscriber's prior consent. Meta also lists an IVR flow as a supported way of collecting opt-in for WhatsApp. If you plan either, read the consent guide first.
Finding the dead ends
Dashboards show call volume easily and dead ends poorly, so measure these directly:
- Hang-ups inside the menu, by menu level. A spike at one prompt points to that prompt.
- Menu repeats and timeouts. Callers are stuck or the wording is unclear.
- Zero-outs, meaning calls that pressed 0 straight away. If most do, the menu may not be earning its place.
- Misroutes. Ask agents to mark calls that reached the wrong team.
- Repeat calls from the same number within a day or two on the same topic.
- Out-of-hours calls, by hour, to test whether your opening hours match demand.
Numbers tell you where to look, not why. Nielsen Norman Group recommends giving callers tasks and asking them to think aloud as they use the tree. A handful of those sessions, plus listening to recordings where your law and policy allow it, will explain a lot. The conversational flows guide applies the same thinking to chat and voice agents.
Where Jadility fits
Jadility Voice covers IVR, contact center and voice agents, and the platform page shows the wider product. If you are redesigning a phone line, bring your top call reasons and talk to us.
Sources
- The UX of Phone-Tree Systems: 16 Usability Guidelines, Nielsen Norman Group, accessed 6 November 2026.
- Consumer Protection Guidelines and Customer Care Standards, Communications Authority of Kenya, accessed 6 November 2026.
- Display contact information in the agent workspace when a contact begins, Amazon Web Services, accessed 6 November 2026.
- The Data Protection Act, No. 24 of 2019, Office of the Data Protection Commissioner, accessed 6 November 2026.
- Kenya Information and Communications (Consumer Protection) Regulations, 2010, Communications Authority of Kenya, accessed 6 November 2026.
- Get opt-in for WhatsApp, Meta for Developers, accessed 6 November 2026.











