“For order information press 1, for returns press 2, for everything else press 3.” Everyone has heard it. Keypad-driven interactive voice response systems (IVR) have guarded contact centre front doors for decades. In the last few years a new term has joined them: the voicebot, a voice agent that understands natural speech.

Both get described as “a system that answers the phone automatically”, but they do very different jobs. This article covers the differences, when each one is enough, how to plan a transition and what the cost items are.

Definitions

IVR (Interactive Voice Response): plays recorded prompts and routes the caller by keypad presses (DTMF). Its core job is routing: getting the call to the right queue or department. Some IVRs do simple lookups (enter your order number, hear its status), but those flows are pre-drawn trees and callers can’t leave the tree.

Speech-enabled IVR: recognises keywords such as “returns” or “order” instead of key presses. The menu is still there; you just choose by word instead of digit. Say something off-menu and you usually hear “Sorry, I didn’t get that.”

Voicebot (voice agent): the caller speaks freely, the system works out what they mean and takes action. It doesn’t force “my order from last week hasn’t arrived and I won’t be home tonight” into a menu; it finds the order, gives the status and opens a delivery request. Behind it sit a language model, tools connected to your store’s systems and turn management. We walk through one such call in how an AI voice agent works.

Key differences

Keypad IVR Voicebot
How the caller explains By pressing keys, fitting the menu In their own words
Core job Routing Resolving and acting
Flow Pre-drawn tree Adapts to the conversation
Off-menu request Usually “press 0” Tries to understand, transfers if it can’t solve it
Personalisation Limited (by digits entered) Recognises the caller and talks about their order
Making changes Re-record prompts, redraw the flow Update instructions, knowledge and tools
Typical failure Wrong key, lost in the menu Misunderstanding, overly long answers
Measurement Which key was pressed Topic, resolution, transfer, transcript

The second row is the one that matters. An IVR tries to get the caller to the right person; a voicebot tries to finish the caller’s task without needing a person. So don’t compare them as “which is better” but as “better for which job”.

Same call, two experiences

The difference is clearest when you follow the same request through both. The customer’s problem: the order hasn’t arrived and they won’t be home tonight.

With a keypad IVR:

  1. Welcome prompt and recording notice.
  2. “For orders, press 1.” The customer presses 1.
  3. “Enter your order number.” The customer digs through their email and types it in.
  4. “Your order has been dispatched.” End of prompt.
  5. There’s no option for a delivery note; the customer goes back to the main menu, finds “other enquiries” and joins the agent queue.
  6. When an agent picks up, the customer explains everything again.

With a voicebot:

  1. Greeting.
  2. The customer explains in one sentence. The agent has already recognised their number and found the order.
  3. The agent gives the shipping status and tracking number.
  4. The customer says they won’t be home; the agent opens a request and says the team will arrange delivery with the carrier.
  5. Call over. The team sees the request with the transcript.

In the second flow no person was needed, and if one had been, they wouldn’t have had to hear the story from the start. At peak times that difference shows up directly in queue length.

When an IVR is enough

A keypad IVR still makes sense when:

  • Most calls are routing. If most callers genuinely need a person (B2B sales, technical service bookings) and the IVR’s job is to send them to the right team, a simple menu does it.
  • There are few, clear options. A three- or four-option menu callers can choose without hesitation works well.
  • You need mandatory announcements. Recording notices, opening hours, service alerts that everyone must hear.
  • There’s no backend data. Without access to orders and customers, a voicebot can do little more than a talking menu.

When you need a voicebot

  • The same questions keep coming. Order status, shipping, return process, address changes: questions whose answers already live in a system make up most of the volume.
  • Callers get lost in the menu. Many press 0 for an agent, or land in the wrong department and get transferred.
  • After-hours calls are lost. Evening and weekend callers get nothing but “we’re closed”.
  • Something needs doing. Opening requests, booking callbacks and taking addresses are painfully long or impossible in a menu tree.

A hybrid approach

For many businesses the answer is both:

  • Order and shipping calls go straight to the voicebot; the B2B sales line stays on the IVR.
  • The voicebot answers, and transfers what it can’t solve to the right team by topic and working hours, doing the menu’s routing job through conversation.
  • During the transition, one number or menu option on your existing phone system is forwarded to the line the voicebot is on. That kind of forwarding is configured with your phone system and carrier.

A six-step transition plan

  1. Classify your calls. Use two weeks of call records to list topics. Which repeat? Which have answers sitting in a system?
  2. Sort out data access. Decide how the voicebot will reach order, product and customer data. No data, no voicebot.
  3. Start narrow. Begin with the most frequent, clearest topic (usually order status) and leave the rest as transfers or requests.
  4. Design the exit. Write down which topic goes to whom, at what hours, and what happens if nobody answers.
  5. Test, listen, fix. Run test calls with your own team before going live. In the first weeks, read transcripts; they show exactly where the agent stumbles.
  6. Expand gradually. Add the next topic once one works. Publish each change as a version you can roll back.

Cost items

The two approaches cost money in different places. Instead of numbers, here are the items to ask about when comparing quotes:

Keypad IVR:

  • PBX or cloud phone system licence and IVR module
  • Prompt recordings (again for every change)
  • Flow design and change work
  • Agent time spent on callers who got lost or misrouted (the hidden cost)

Voicebot:

  • Platform fee and usage (usually per minute or per call)
  • Speech recognition, language model and speech synthesis costs (often included in usage; ask)
  • Integration with your store systems and setup
  • Internal time to maintain knowledge and instructions
  • Phone line and call minutes (paid to your carrier in both cases)

Compare total cost: a voicebot minute may look pricier than an IVR minute, but if it finishes a call an agent would otherwise handle, the fair comparison is the agent’s cost.

Common mistakes

  • Building the voicebot as a talking menu. “Say ‘order’ for orders” carries every limit of an IVR and none of the benefits.
  • Automating everything on day one. With a wide scope it’s hard to find the source of problems.
  • Making it hard to reach a person. Playing hide-and-seek when the customer asks for a human destroys satisfaction fast.
  • Not reading transcripts. A voicebot’s most valuable output is the conversations themselves: what customers ask and where they get stuck.

Where Zitena fits

Zitena is not a keypad menu but a voice agent that finishes the job in conversation. Whichever assistant your number maps to answers the call directly, and the customer explains in their own words. The agent recognises the caller by phone number, finds the order, reads the shipping status, opens address-change and return requests, and books callbacks from phrases like “tomorrow afternoon”. It stops talking when the customer cuts in and waits out half-finished sentences.

It also does the menu’s routing job through conversation: you decide which topic goes to whom and at what hours, and if the person doesn’t answer, the agent books a callback. Your existing SIP line is connected and your number stays the same. You test changes with test calls, publish them as versions and roll back when needed. See why teams choose us and everything the agent does on inbound calls. The agent is live in Turkish today; other languages are adapted on request.

To work out whether your calls need a menu or an agent, book a demo.