The Kahevo PBX roadmap.

In progress now

Being built

Work that is under way today.

Several customers on one server, proven

It is built and in testing: one Kahevo holds many businesses, each with its own extensions, numbers and records, kept strictly apart, with trunks and numbers you assign, limits, usage for billing and an archive of each. What is left is running it with real customers side by side, and copying menus and queues into a new business.

High availability, proven on hardware

Two or three Kahevo servers running as one phone system. Every step below is built and in testing, and a call has already carried on through a server losing its power, and through a server's network being cut and restored. What is left is proving the rest on real hardware, under real load.

Restore, proven

The backup tool is built: one file holds the whole system. Putting it back on a new server is being tested on real systems. Until then, we recommend keeping virtual machine snapshots as well.

iPhone app on the App Store

Out of testing and into the store, with a proper screen for transferring a call and adding contacts from the app.

Encryption proven end to end

TLS and SRTP checked against real desk phones and providers, then switched on by default.

Softphone from anywhere

Built and in testing: the browser phone and the iPhone app now reach the office from home and mobile data with nothing to set up, and a call carries on when the network changes. What is left is proving it across many more home routers.

Built and in testing

The path to the highest uptime

Each step is built. What remains is proving each on real hardware.

1. A standby that takes over

When a server fails, another takes its place in seconds. Seen on real machines.

2. Every server taking calls

Phones and calls shared between the servers, so losing one costs only its share.

3. Upgrades without downtime

One server at a time, each handing its calls to the others before it restarts, and a failure drill for the quiet hours.

4. Riding out the database

Calls and registrations carry on while the database is away, and what happened meanwhile is written down once it is back.

5. Files on every server

Recordings, voicemail and faxes kept on every server.

6. Calls that survive

Calls on a failed server carry on after a short silence, recordings included, and browser and app calls reconnect by themselves. Seen on real machines with desk phones, through a power cut and a network cut; browser and app calls so far in our own testing.

In production, with more to come

AI that does the listening

Less time spent playing back messages and calls to find the one thing you need. The first part is in production; what comes after it is planned.

Voicemail in writing

In production. Each message written out under it on the Voicemail page and in the app, and in the email that tells you it arrived. Read it in a meeting, play it only when you need to.

Recorded calls as a conversation

In production. A recorded call laid out as who said what, in order. Press a line and the recording plays from that moment.

Search by what was said

In production. Find the call where a customer gave their order number, or the voicemail that mentioned Thursday, by typing the words.

Your callers' voices kept private

Built that way. The audio is removed once the text is back. Each business switches it on for itself, and it stays off until it does.

Tuned to how Hawaiʻi talks

We keep checking how well it copes with island place names, Pidgin, Ilocano, Japanese, Tagalog and calls that move between languages, and improve it as we go.

Then, the short version

A one-line summary of each message, and urgent voicemail brought to the top. Now that the writing out is in production, these are next.

AI voice services

Tight integration with AI voice services such as ElevenLabs: type a greeting or a menu prompt and have it spoken in a natural voice, and hand a call to a voice agent that can answer, take a message or route it.

Further out: live captions and translation

Words on screen during a call, and a caller in another language heard in yours. We have looked into it and set it aside until the rest is proven.

Targeted for early 2027

Messages

What our customers ask for most after calls.

Texts to several customers, and scheduled messages

Texts on shared business numbers and messages between colleagues are in production, in the browser and in the app. Next: one text to several customers at once, and messages sent at a time you choose.

Through 2027

Built for MSPs

What it takes to run Kahevo for many customers without logging in to each one.

Central dashboard for MSPs

Every customer on one screen: which are up, which trunks are registered, which phones are offline, and a way in to each. For businesses that share one server this is built and in testing; across separate servers it is still to come.

Health checks and alerts

Kahevo watches itself, its trunks, its disk and its call quality, and tells you by email or webhook before the customer does.

More providers

Five come with Kahevo today, including two that need no registration. Tested settings for more SIP providers, each a choice in a list in place of a page of fields to get right.

Several trunks with failover

Built and in testing: an outgoing rule tries the next trunk in its list when the first is down or its provider refuses a call. What is left is proving it with real providers.

More phone brands

Setup by link for the desk phones our partners have on desks, beyond the two brands supported today.

Installers and updates from the page

A guided install for Ubuntu 24.04 LTS, and new versions applied from the browser, for one customer or all of them.

Import from your current PBX

Extensions, groups and routing read from an existing system, so a migration starts from what the customer has.

Through 2027

Bigger offices

What a busy front desk or a small call center expects.

Call queues, finished

Queues, call backs and their reports are built and in testing. What is left is proving them in busy offices, and a live view for a supervisor.

Conference calls

Three-way calling from a desk phone, and conference rooms with a number and a PIN. The mixer that blends several voices into one call is built, and already at work when a manager joins a call.

Reports

Calls by hour, by person and by number, missed calls, and time to answer, on a page and as a file.

Emergency calling

911 rules set up for you, an address per phone, and a notice to the front desk when someone dials it.

Video from intercoms and desk phones

See who is at the door on a SIP intercom's camera before you buzz them in, and carry the picture between SIP desk phones that have a video feed. Video meetings are not on this list, and here is why.

Hot desking, and more paging

Sign in to any desk phone as yourself. Paging your own department and picking up a colleague's ringing call are built and in testing; paging another department, or everyone, comes next.

An Android app

The same companion app for the other half of your staff.

Later in 2027

Opening it up

Larger pieces we want, whose shape will depend on what partners ask for.

An API and webhooks

Other software can place calls, read the call log and hear about calls as they happen. This is what connects Kahevo to a CRM or a ticket system.

Your name on it

An MSP's own logo and colors on the pages their customers see.

More languages

The pages and the spoken prompts in languages other than English.