How to set up a phone menu (IVR) for a small business

A good phone menu gets callers to the right person in seconds; a bad one makes them hang up. Here is how to plan it, write it, build it and test every path before a single customer calls.

8 min read
Updated 28 Sep 2026
By the Numonym team

On this page7 sections

In short

Start from why people call: three or four options, the most common first.
Plan opening hours, public holidays and exceptions before recording anything.
Keep the greeting under 15 seconds, and give callers who press nothing a way through.
Test every path — nights, weekends, holidays, wrong keys — in the simulator before going live.

Start with why people call

Before you record anything, list the reasons people call you. Last month’s calls are the best source; your team’s memory is the second best. Most small businesses end up with three or four reasons: sales, support, orders or billing, and “something else”.

Put the most common reason first, so most callers press 1 and move on.
Keep it to four options or fewer. Callers can’t hold more in their head.
Avoid sub-menus unless one option really needs them.
Decide what happens when nobody presses anything: send the call to a default team rather than hanging up.

Then decide who answers each option: one person, a group of people who ring together, or a queue.

Business hours and holidays

Every call flow needs an answer to “what happens when we are closed?”:

Opening hours for each day of the week, in the time zone of the number.
Public holidays. On Numonym they are preloaded for each number’s country, so a US number and a French number each follow their own calendar.
Exceptions, such as an early closing or an office move, scheduled ahead of time so nobody has to remember to switch anything.
The closed path: a short announcement, then voicemail. Transcriptions can go to Telegram, email or a webhook, so someone sees them quickly.

Write the greeting

Short scripts work best. A proven structure:

Who you are: “Thanks for calling Acme.”
The options, reason first and key second: “For sales, press 1. For support, press 2.”
The fallback: “Or stay on the line to reach our team.”

Skip marketing messages and “please listen carefully as our options have changed” — they only delay callers. Keep the time before the first option under 15 seconds.

If you serve callers in several languages, add a key for each language that plays the same menu translated. You can generate every greeting with text-to-speech in the language and voice of your choice, record it in the browser, or upload an MP3.

Build the flow

In the call flow editor, a phone menu is a chain of blocks:

Block	What it does
Hours	Sends the call down the open or the closed path
Menu	Plays the greeting and waits for a key
Ring group	Rings several people at once, in turn, or in a fixed order
Queue	Holds callers with music and their position, and offers a callback after a few minutes
Voicemail	Records a message and sends the transcription where you want
Forward	Sends the call to an outside number
Announcement	Plays a message, then continues or hangs up

Everyone on the team gets an extension — as many as you need, with no per-seat pricing — and can answer in the browser, in a SIP app or on a desk phone. See call flows for every block and option.

Test every path before going live

Most broken menus were never tested outside office hours. The call flow simulator lets you pick a day, a time, the caller’s country and the keys pressed, then shows the path the call takes and plays the announcements it would hear.

Test a call during opening hours for each menu option.
Test a call at night, at the weekend and on a public holiday.
Test a caller who presses nothing, and one who presses a wrong key.
Test a full queue: does the caller get a way out?
Finish with a real call to your own number from an outside phone.

Changes are saved as a draft first. Publishing makes them live, and you can roll back to a previous version in one click if something goes wrong.

Common mistakes

Greetings longer than 15 seconds before the first option.
No path for callers who don’t press anything.
Forgotten holidays, so callers hear “we are open” on a closed day.
A queue with no way out: offer voicemail or a callback after a few minutes.
Menus that change every week — regular callers learn the keys and get lost.
One number for every country: callers trust a local number more, and each can keep its own holidays behind the same flow.

Ready to build yours? See how the phone system works, or pick local numbers in the markets you serve.

Measure and improve

Once the menu is live, look at the figures every few weeks:

Calls by hour and by day tell you when to add people to a ring group, or whether to open earlier.
Missed calls and the average waiting time show where callers give up.
Calls per person, per number and per country show which markets and which team members carry the load.

Small changes make a big difference. An automatic text after a missed call — “Sorry we missed you, we’ll call you back shortly” — keeps callers who would otherwise try a competitor. The text leaves from the same number, so replies land in your team’s shared inbox, where anyone can pick them up.

Then adjust one thing at a time: the order of the options, the ring time before voicemail, the opening hours. The simulator and the version history make every change safe to try and easy to undo.