Skip to content

I Tried to Build a Simple "Press 1 for Sales" Menu in Twilio: It Took Me a Whole Afternoon

I Tried to Build a Simple "Press 1 for Sales" Menu in Twilio: It Took Me a Whole Afternoon

"Press 1 for Sales, Press 2 for Support." It is one of the most familiar sounds in business, so familiar that I assumed it was a setting somewhere. I had a Twilio number, a free afternoon and a cup of coffee. By the end of the afternoon I had a half-working menu, a server I did not want to maintain, and a new respect for every receptionist I had ever ignored.

Underneath, a phone menu is not a setting. It is a small program, written in a markup language built for developers, answered by a web address you have to host yourself. This post is what I learned: what a menu is really made of, what it takes to build one by hand on Twilio or Telnyx, how to build the same thing without code, and how to design one callers do not hate.

What a "simple" phone menu is actually made of

Every phone menu, however simple it sounds, has the same six parts:

  1. A greeting. The words the caller hears first, spoken by a computer voice or played from a recording.
  2. A question. "Press 1 for Sales, 2 for Support." The system then listens for a keypress (or, on modern systems, a spoken answer).
  3. The options. What each key does: ring a person, go to another menu, leave a voicemail, join a queue.
  4. A timeout. What happens if the caller presses nothing. Repeat the menu? Send them to a person?
  5. A wrong-key answer. What happens if they press 7 on a menu with three options.
  6. The next step. Where the call ends up, and what happens if nobody answers there.

A menu with a sub-menu ("Press 1 for Sales", then "Press 1 for new customers") doubles all of it. None of this is a flaw in the phone system. It is solid infrastructure. It is just infrastructure, not a finished menu.

What it takes to build one by hand

On Twilio, a phone menu is written in TwiML, a small XML language. When a call comes in, Twilio asks a web address you control what to do, and your server answers with instructions like <Say> (speak this), <Gather> (listen for a keypress) and <Dial> (ring this number). When the caller presses a key, Twilio calls your server again with the digit, and your code decides what comes next.

So "Press 1 for Sales" really means:

  • a web server that is always online, because if it is down, your phone line is down;
  • code that answers the first request with a greeting and a <Gather>;
  • code that reads the digit and returns the right <Dial> for each option;
  • separate handling for no keypress, a wrong key, a busy line and an unanswered call;
  • the number's voice webhook in the Twilio Console pointed at all of it.

Telnyx works the same way with TeXML, its Twilio-compatible markup, so the effort is the same. Twilio also offers Studio, a drag-and-drop flow editor. It removes the server, but it is still a developer tool: you wire widgets together, and every edge case (timeouts, wrong keys, busy lines) is a branch you draw yourself. If you want the full comparison, our guide to building a Twilio phone tree without code walks through each route.

That is where my afternoon went. Not on deciding what my menu should say, which took five minutes, but on everything around it.

Building the same menu without code

Here is the same "Press 1 for Sales, 2 for Support" menu in TelBuddy, on the Twilio or Telnyx number you already own. Nothing is hosted by you; the timeouts and wrong keys are part of the form.

  1. Open Phone Menus.

    Create a menu and give it a name you will recognise, like "Main menu".

  2. Write the greeting.

    Type what callers hear: "Thanks for calling Lopez Dental. For appointments, press 1. For billing, press 2." Choose a voice, or play a recording instead.

  3. Choose how callers answer.

    Keypad only, speaking only, or either. Speaking lets callers say "appointments" instead of pressing 1.

  4. Add the options.

    For each key, pick what happens: forward to a phone, go to another menu, a call queue, the AI receptionist, voicemail, an extension or your staff directory, text the caller a link or your address, email your team, or end the call.

  5. Set the timeout and the wrong-key message.

    How long to wait for a keypress (1 to 30 seconds) and what to say when the caller presses something that is not an option.

  6. Attach it to your number.

    In Voice Settings, point the number at the menu. Calls use it straight away; there is nothing to deploy.

  7. Call it yourself.

    Press every option once, press nothing once, and press a wrong key once. That is the whole test.

Sub-menus are the same form again: an option set to "go to another menu". You can see how the builder looks on the phone menu feature page.

How to design a menu callers do not hate

  • Four options at most. Nobody remembers option six. If you need more, use a sub-menu.
  • Most common first. If 70% of callers want appointments, appointments is option 1.
  • Say the reason before the number. "For billing, press 2" is easier to follow than "Press 2 for billing", because people listen for their reason first.
  • Keep the greeting short. Skip "your call is important to us" and "please listen carefully as our options have changed".
  • Always give a way to a person. Make 0, or a timeout, reach someone or a voicemail. A caller stuck in a loop hangs up.
  • Use a different greeting when you are closed. Pair the menu with business hours routing so after-hours callers hear the right thing.
  • Offer a text instead of a wait. "Press 3 and we will text you a booking link" turns a hold into a conversation.

Three menus you can copy

A dental or medical office
"Thanks for calling Bright Smile Dental. To book or change an appointment, press 1. For billing and insurance, press 2. For anything else, press 0 or stay on the line."

A home services company
"Thanks for calling Gulf Coast Plumbing. For an emergency, press 1 and we will connect you now. To book a visit, press 2. To get a text with our booking link, press 3."

A real estate office
"Thanks for calling Sunshine Realty. If you are calling about a property sign, press 1. To speak with an agent, press 2. For rentals, press 3."

Mistakes I made so you do not have to

  1. No timeout plan. My first menu hung up on anyone who did not press a key. Plenty of people just wait.
  2. Too many options. I listed seven departments for a three-person business.
  3. Testing only the happy path. I pressed 1, it worked, I moved on. Pressing 9 dropped the call.
  4. Forgetting where calls end up. "Press 2 for Support" rang a phone nobody answered on Fridays. Every option needs a plan for no answer: a backup phone, a queue or voicemail.

A phone menu is often the first thing a customer experiences about your business. Done right, a one-person company sounds like it has departments. Stuck in markup for an afternoon, the menu never gets built at all, which is its own kind of first impression. If you are comparing the full picture of calls on your own number, see phone menu, call queue and AI receptionist setup.

Frequently asked questions

Do I need to know how to code to build a phone menu?

Not with a visual builder. On raw Twilio or Telnyx a menu is written in TwiML or TeXML and answered by a server you host. In TelBuddy you type the greeting, pick what each key does, and save.

Can a phone menu have sub-menus?

Yes. Set an option to go to another menu, for example Press 1 for Sales, then Press 1 for new customers. Each menu has its own greeting, options and timeout.

What happens if a caller presses nothing or a wrong key?

You choose. Set how long to wait for a keypress, from 1 to 30 seconds, and the message for a key that is not an option. Always give callers a way to reach a person or voicemail.

Can callers say what they want instead of pressing a key?

Yes. Each menu can listen for the keypad, for speech, or for either, so callers can say "appointments" instead of pressing 1.

What can a phone menu option do?

In TelBuddy an option can forward the call, go to another menu, join a call queue, reach the AI receptionist, go to voicemail, ring an extension, open your staff directory, text the caller, email your team, or end the call.

Does this work on both Twilio and Telnyx?

Yes. The same menu works on numbers from either carrier, and you keep your own account and numbers.

How many options should a phone menu have?

Four at most. Put the most common reason first, say the reason before the number, and use a sub-menu if you need more choices.

Phone Menus (IVR) in TelBuddy

Build a press-1 phone menu with a visual builder. No code, on Twilio or Telnyx.

Joseph Johnson
Founder of TelBuddy. Built it on the Twilio and Telnyx APIs after getting his own number blocked, and went through A2P 10DLC registration the hard way. More about me.