Cloud communication
Communications you configure, not equipment you maintain.
Running voice in the cloud moves the hardware, the upgrades and the resilience planning off your premises. What stays with you is the part that matters: deciding how calls should behave.
Diagram: three sites with no local telephony hardware all connect into a single cloud voice layer holding numbers, routing, menus and groups.
What it solves
On-premise voice ages badly and quietly.
A PBX in a cupboard works right up until the day it does not — and then it is a hardware problem, a firmware problem and a single-site problem all at once. Moving the layer into the network makes changes routine and failure survivable.
- No on-site telephony hardware to maintain, patch or replace.
- Change routing without a site visit or a maintenance window.
- Add sites and people without adding equipment.
- Keep working when one location is unreachable.
How it works
Three things happen to every call.
Map what exists
Numbers, extensions, call flows and the endpoints your team uses today.
Rebuild it in the network
The same structure, running as a service rather than on your hardware.
Cut over deliberately
Traffic moves when you are satisfied, with the previous path available during the transition.
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.
- Managed voice layer
- Numbers, routing, menus and groups operated as a service.
- Multi-site by default
- Locations share one numbering plan instead of running parallel systems.
- Change without downtime
- Routing changes take effect without a maintenance window.
- Resilience built in
- Call paths that survive a site becoming unreachable.
- Scales both ways
- Capacity that grows and, when the season ends, shrinks.
- Migration support
- Existing numbers, dial plans and behaviours carried across deliberately.
Example migration shape
A route you could read out loud.
On-premise structure mapped into the network layer, cut over once verified.
Route definition
Illustrative- Today
- On-premise PBX, one site, local hardware
- Mapped
- Numbers, extensions and call flows recorded
- Rebuilt
- The same structure in the network layer
- Cutover
- Staged, with the old path still available
- After
- Routing changes without a maintenance window
An illustrative example. Your route is written with you before anything is configured.
Use cases
Where it earns its place.
Retiring an ageing PBX
Replace hardware that is one failure away from an unplanned project.
Consolidating offices
Several sites onto one numbering plan and one set of call flows.
Business continuity
Calls that keep arriving when a building does not.
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.
Works alongside
- SIP TrunkingConnect the PBX or platform you already run to the public network, without the physical lines.
- Business VoIPBusiness calling over your internet connection, on the devices your team already carries.
- Wholesale VoiceTermination and origination at carrier scale, for operators and resellers moving real volume.
FAQ
Common questions
Anything specific to your destinations, numbers or endpoints is confirmed directly rather than answered generically.
Do we have to move everything at once?
No. Migrations usually run in stages — a site, a department or a number range at a time — with the previous path still available until each stage is proven.
What happens to our existing numbers?
Where the destination supports porting, they come with you. We confirm which of your numbers can move and what the process involves before anything is scheduled.
Who manages it afterwards?
The infrastructure is ours. The configuration — who calls reach, when, and what happens if nobody answers — stays your decision, and changes are supported around the clock.
Next step
Ready to set up cloud communication?
Tell us how your calls work today and where they need to go. We'll map the route with you before anything is configured.