Nobody calls a business because they enjoy calling businesses. They call because they want something, usually quickly, and often while doing something else. Then they hit a menu with nine options, none of which describe their problem, and no obvious way to reach a person.
Here is the part worth sitting with: a phone menu is not inherently bad. A good one gets people to the right desk faster than a receptionist juggling four lines. The bad reputation comes from menus built by whoever had portal access on a Tuesday, using defaults nobody revisited. Good menu design is a small amount of thinking done once.
Fewer Options, and Only Ones That Actually Route
Listening is harder than reading. Nielsen Norman Group, citing Stolovitch and Keeps (2011), notes that an estimated 83 percent of the information humans take in comes through the eyes and only 11 percent through the ears. Your caller cannot scan a phone menu. They have to hold every option in their head until the list ends.
That is why Nielsen Norman Group recommends limiting the choices in each menu and submenu to four or five. It also recommends presenting options starting from the most frequently selected and working down to the least. And it advises putting the information first and the number second: “for billing questions, press two,” not “press two for billing questions.” Callers who hear the number first have already forgotten what it was for.
One more rule, not in any manual. Every option must route somewhere a human monitors. If option four rings a desk that has been empty since last spring, delete option four. A choice that leads nowhere is worse than no choice, because the caller made a decision and got punished for it.
Give People a Human in the First Menu
Some callers will never fit your categories. Their situation is weird, or urgent, or they are angry. Burying the operator three levels deep does not reduce that call, it just makes the person angrier before they get there.
Nielsen Norman Group describes the familiar pattern of letting callers reach a live representative by pressing zero, and also mentions connecting the caller directly to a representative if they let the menu play through three times. Both are worth building.
Microsoft’s auto attendant documentation makes the same point technically. It recommends configuring an operator, and warns that you have to assign an operator key in the menu options or the operator feature is not enabled. Microsoft describes the operator as where callers go when they make no selection or when a call processing error occurs, and says it lets callers break out of the menus and speak to a designated person. That is the safety net. Build it, and test that it catches people.
Nielsen Norman Group also suggests using the star key to repeat the menu, and automatically repeating options if the caller does not choose right away. People miss things. Let them hear it again without starting over.
Hours and Holidays That Are Actually Correct
This is the most common broken thing we find, and the easiest to fix. A greeting that says you are open when the doors are locked costs you a customer and gains you a bad review.
Check the defaults first. Microsoft’s documentation notes that if business hours are not changed, the business-hours call flow runs from 9:00 AM to 5:00 PM every day of the week, with the after-hours flow outside that. If your shop opens at seven and closes at four, the out-of-the-box settings are wrong from day one. Microsoft’s system also supports multiple breaks during the day, so a real lunch closure can be configured honestly instead of letting the phone ring in an empty office.
Holidays need their own attention. Microsoft’s documentation describes configuring holidays with a different call flow for each one. Sit down once a year, enter every holiday you actually close, and record what you want callers to hear. A greeting naming the specific holiday and the date you reopen is worth ten generic ones.
The Greeting Should Inform, Not Sell
Your caller already chose you. They dialed your number. Reading them a paragraph about your commitment to excellence before they can press anything is not marketing, it is a toll.
A good greeting is short and carries information the caller can use:
- Who they reached: your business name, clearly, at the front.
- Anything that changes their next move: a closure, a location change, a known outage. This is the only place promotional-sounding content earns its keep, and only when it is genuinely useful.
- The menu, right away: get to the options before attention runs out.
- Nothing else: your hours and address belong on your website, where people can read them at 83 percent efficiency instead of hearing them at 11 percent.
Microsoft’s documentation supports either an uploaded recording or typed text the system reads aloud. A human recording almost always sounds better. If you type it, keep it short: the fact that Microsoft allows up to 1,000 characters is a technical limit, not a target.
Voicemail That Reaches a Person
Voicemail fails quietly. Nobody complains about a mailbox nobody checks, because the person who left the message went to a competitor instead.
Route voicemail to email. A message that lands in an inbox with the audio attached gets read, forwarded, and answered like any other work item. A message behind a passcode on a desk phone gets found on Thursday.
Send it somewhere a group can see, not one person’s personal mailbox. When that person is on vacation, the shared destination still gets read. Microsoft’s auto attendant documentation supports routing to a mailbox associated with a group for exactly this reason, and notes that the group needs to be configured to accept email from outside your organization for the messages to arrive.
Then assign a name. Not a team, a person, with a backup. Systems do not check voicemail. People do, and only when they know it is theirs. That is the same principle we wrote about in why saving time takes priority over saving money: the process fails at the handoff, not at the technology.
Call Your Own Business
Almost nobody does this, and it takes ten minutes. Pick up a cell phone, call your main number, and go through it as a customer would.
- Press every option: confirm each one rings where you think it rings.
- Press nothing: see where silence sends you. It should reach a person or a monitored mailbox.
- Press zero: from every menu and submenu, not just the first.
- Call after hours and on a holiday: the after-hours path is the one that is wrong most often, because nobody is there to notice.
- Leave a voicemail: then check whether it actually arrived, and how long it sat.
- Listen for dead air: long silences make people think the call dropped, and they hang up.
If callers wait in a queue, Nielsen Norman Group suggests updating them roughly every 1.5 to 2 minutes, and considering an option that saves their place in line and calls them back when it is their turn. Silence reads as abandonment.
The Bottom Line
People do not hate phone trees. They hate long menus that do not describe their problem, dead ends, wrong hours, and no way out. Every one of those is a design decision somebody made or forgot to make.
Four or five options. Most common first. Information before the number. A human available from the first menu. Hours and holidays that match reality. A short greeting. Voicemail that reaches somebody by name. Then call it yourself once a quarter, because businesses change and menus do not.
We design and configure business phone systems for companies across Denton County, including the unglamorous part where somebody maps what should happen to every call. It is the kind of detail a good outside IT partner should catch without being asked. If your menu has not been reviewed since setup, that is worth an hour. Contact us today.
Sources:
Comments are closed