OmniServe by Runox
Use case · Visual IVR

Nobody has ever enjoyed being read a list of options

A phone menu asks people to hold six choices in their head, in order, while a recorded voice says them slowly. It is a bad interface that has survived for forty years because a phone line could not draw anything.

The costs are well known and tolerated anyway. Callers mis-press and land in the wrong queue, which is the most expensive kind of answered call. They press zero to escape it, which defeats the routing entirely. And anyone who cannot hear the options, or whose English is not fluent enough to follow them at speed, is simply excluded.

Because the caller arrives through a link, they arrive in a browser — so the menu can be a thing they look at. Every option visible at once, tapped instead of memorised, in as many levels as your business actually has. And when they reach the end of it, the assistant opens already knowing which path they took.

That last part is what makes it more than a nicer menu. A phone tree collects a digit. This collects a reason, and the reason travels into the conversation and out to whoever picks it up.

What a menu can do once it is visible

All at once

Six options read in two seconds, not forty

Reading is roughly ten times faster than being read to. The caller sees the whole tree, picks, and is through before a recorded voice would have finished option three.

No mis-presses

You tap the words, not a number for the words

The single largest source of misrouted calls disappears, because there is no translation step between what you want and which key it is.

Depth without pain

As many levels as you actually need

Nested menus are unbearable spoken and trivial visually. You can route properly instead of flattening the tree to spare the caller.

Context

The path is handed to the assistant

It opens knowing they came through Billing then Payment failed, so it does not ask what it already knows. This is the part a keypad cannot do.

And onward to a person

The path travels through the handover

When it reaches a human, their screen already shows which route the caller took and what was said. Nobody is asked to explain themselves twice.

Built by dragging

A tree you edit, not a script you record

Change an option at four in the afternoon without booking a voice artist. Menus that are painful to change never get changed, which is why so many are wrong.

Accessible by construction

Readable, and it works with a screen reader

A caller who cannot hear the options can read them. That is not an accommodation bolted on afterwards — it is what happens when the menu is a page.

Skippable

They can just say what they want

The menu is an offer, not a gate. Anyone who would rather start talking can, and the assistant works out the routing itself.

This only exists for callers who arrive by link. Someone dialling your number still gets a spoken menu or goes straight to the assistant — a browser is what draws the tree, and the phone network has no way to send one.

In practice

Where the phone tree costs you

Everyone pressing zero

Visual tree · tapped

The universal escape hatch, and it lands every caller in the same queue regardless of what they wanted. A menu people can actually read gets used instead of bypassed.

The wrong department, twice

Routing · from the path taken

A misrouted call costs a full handling time and produces nothing. Tapping the words you meant removes the class of error entirely.

"Which account is this about?"

Context · into the conversation

Asked at every step of a phone tree and then asked again by the person who answers. Here it is established once, on the way in.

“I can see you came through about a failed payment — is that on the account ending 4471?”

A caller who cannot follow spoken options

Readable menu · any device

Hard of hearing, a second language, a noisy street. All the same problem, and all solved by the options being on a screen rather than in the air.

The objections
Do we have to give up our phone menu?

No, and most do not. The number keeps whatever it does today; the link gets the visual tree. Over time the traffic tends to move on its own, because the link is the thing you put in emails, adverts and profiles.

Can different branches of the tree behave differently?

That is the main reason to build one. Sales can reach the assistant at midnight while complaints only ever reach a person; each leaf can have its own assistant, its own knowledge and its own hours.

What if the caller picks the wrong branch anyway?

The assistant notices from what they actually say and moves them, rather than making them hang up and start again. The menu is a hint about where to begin, not a commitment.

See it

One platform fee. Seats only when you want people. No minimum, no term.