Hosted PBX
Business calling, organized around your team.
Extensions, ring groups, queues and voicemail arranged the way your business actually answers — so internal structure and external call paths finally match.
Diagram: an inbound number rings a support group of three extensions; unanswered calls hold in a queue and then reach voicemail.
What it solves
The phone system should mirror the way you work.
When extensions, teams and escalation paths are set up ad hoc, every new hire and every reorganisation creates another gap where calls get lost. A structured setup keeps the call path and the team structure in step.
- Give every person and team a predictable place in the call path.
- Ring a group instead of a single desk.
- Hold calls in a queue rather than dropping them.
- Keep voicemail as a defined ending, not an accident.
How it works
Three things happen to every call.
Map the structure
Extensions and groups are laid out around teams, sites and responsibilities.
Attach the call paths
Inbound numbers, menus and rules are pointed at the right groups.
Answer from your endpoints
Calls reach the devices and destinations your team already uses.
Capabilities
What you can build with it.
Availability of individual capabilities depends on your setup and destinations. We confirm what applies before anything is configured.
- Extensions
- A consistent internal numbering plan across sites and teams.
- Ring groups
- Ring several people together, or in a defined order, for one inbound call.
- Queues
- Hold callers in order when every destination in a group is busy.
- Voicemail
- A defined ending for calls that cannot be answered live.
- Forwarding per extension
- Individual extensions can carry their own onward destination.
- Remote endpoints
- Include people working away from a fixed office in the same structure.
Example team structure
A route you could read out loud.
An inbound number into a ring group, with a queue behind it and voicemail as the defined ending.
Route definition
Illustrative- Inbound
- Main line · one published number
- Group
- Support · extensions 201, 202, 203
- Pattern
- Ring all, 20 seconds
- If busy
- Hold in queue, in order
- Otherwise
- Team voicemail with notification
An illustrative example. Your route is written with you before anything is configured.
Use cases
Where it earns its place.
Multi-site business
Several offices share one numbering plan and one set of call paths.
Small team, professional front
A handful of people present a structured, department-based experience to callers.
Growing headcount
New extensions slot into existing groups instead of needing a new arrangement.
Coverage & compatibility
Will it work where you need it?
Destinations, number types and endpoint compatibility vary. Send us the specifics and we'll confirm what is available rather than publish a list that may not hold for your case.
FAQ
Common questions
Anything specific to your destinations, numbers or endpoints is confirmed directly rather than answered generically.
Do we need new hardware?
That depends on the endpoints you already use. Tell us what your team answers on today and we will confirm what is compatible.
Can remote team members be included?
Remote endpoints can form part of the same structure where the route to them is supported.
How does this relate to forwarding and routing?
They work together. Forwarding and rules decide how a call reaches your business; the PBX structure decides how it moves once it is inside.
Next step
Ready to set up hosted pbx?
Tell us how your calls work today and where they need to go. We'll map the route with you before anything is configured.