How it works
Six steps from an empty account to a ringing phone.
There is no hardware to rack, no software to install and nothing to patch on a Sunday. What you get instead is four things you can name and one diagram per number that says exactly what happens when it rings.
One number, one path
- inMain number
- step 1Open hours?
- step 2Reception group
- answeredAnswered
Turn-up, in order
Each step depends on the one above it
This is a real sequence, which is why it is numbered here and why the product ships a progress panel instead of a help article describing the order.
Step 1: Say where the office is
A site is an address, a time zone, opening hours and a calling policy. Everything underneath inherits them, so this is the only place most of it gets typed. The address is also the 911 service address new lines start from.
Step 2: Add the people
A line needs a name, an email and a site. The extension is suggested from the next free one and stays editable. Nothing else is required, and the browser phone works the moment you save.
Step 3: Attach numbers
Numbers are inventory. Give one to a line, a group or a call flow — or to none of them yet. Bringing an existing number is a parallel track that does not hold the rest up.
Step 4: Pick a call flow
Every number starts from one that already works: straight through, ring the team then voicemail, open and closed with a greeting, a small menu, or a queue with overflow. Edit from there.
Step 5: Plug the phones in
Type a MAC address and a model, choose the line, and the handset configures itself the first time it boots. Nothing to copy, and no credentials on screen to copy wrongly.
Step 6: Clear the leftovers
An onboarding panel lists what is still open — a group with no overflow destination, a device that has not registered, a line without a service address. Working out the dependency order is the product’s job, not yours.
Deliberate omissions
Questions other phone systems ask that we do not
Every one of these is a real question a widely used PBX puts in front of an administrator before anything works. We answered them once, internally, so you never see them.
- “Which SIP driver should this extension use?”
- An internal implementation choice dressed up as a product decision. There is one transport here, and per-handset quirks live in a device profile you never open.
- “What is this extension’s codec string and contact rewrite?”
- Forty-field extension forms exist because nobody separated the settings almost every office touches from the rest. Simple mode contains no protocol concept at all.
- “Have you built your dial plan in the separate designer application?”
- Call routing is edited on one canvas inside the product. There is no cliff between a small menu and anything more ambitious than that.
- “Which of the eleven reports has the answer?”
- Two dashboards: what happened, and how it sounded. Every queue and attendant links straight to its own filtered view.
Worth knowing
Your connection is still your connection
Browser calling and desk phones both ride the link between your office and the internet. We cannot make a saturated connection carry clean audio.
What we can do is show you, per call, the jitter and packet loss that caused it — which is the difference between a diagnosis and an argument. That is what the call quality dashboard is for, and it is the first place to look when someone says the calls were breaking up yesterday afternoon.
What a call record holds
- Mean opinion score, jitter and packet loss, per call
- The endpoint that took it and the network it was on
- Answered, missed and abandoned, by line and by group
- Busiest hours, and how long people waited
Next
Start with one site and one line
You can be making calls from a browser before you have decided which handsets to order.