Multi-tenant is built and in testing: each business walled off by the database, with limits, usage for billing and an archive.
This is the one our MSP partners asked for first. Until now, one Kahevo was one phone system: every customer got an install and a database of their own. Now one server can hold many businesses. It is built, and in testing.
The wall
Each business's extensions, numbers, calls, recordings, messages and contacts are kept apart by the database itself. A page asks for extensions and is handed only its own business's, whatever it asked for. We did not want a wall that depends on every page remembering to ask politely.
Dial another business's extension and it is simply a number nobody has. The same goes for their park lines, their lamps, their pickup and their paging.
What each business has of its own
- Its own extension numbers. Two businesses can both have a 101.
- Its own administrator, who runs everything of theirs and nothing of the server's.
- Its own time zone, park lines, hold music and logo.
What you have, looking after the server
| For each business | What it is for |
|---|---|
| Limits on calls, extensions, people and storage | So one customer cannot take every line |
| Usage: extensions, numbers, calls and minutes | Your monthly billing, on a page and as a file |
| A switch | Off without deleting anything |
| An archive | Everything of one business in one file, to keep, hand over or move |
A new business can start from another's departments, hours and settings, and you step into any of them from one list.
The honest part
It is in testing. We have tried every feature we could think of across the wall, and each one fails the way it should, but it has not yet run with real customers side by side. In production today, each customer still gets an install of their own. When that changes, you will read it here first.