Unified Communications
Cloud PBX
Australian Hosted

Cloud Phone
System

A business phone system that runs in the cloud. Call flows, IVR, queues and SIP trunking on one cloud PBX. No hardware. No complexity. Just calls that work.

Talk to Us
hub.metcom.cloud/voice
LIVE
Cloud PBX live voice overview with calls in progress
Every device

Your phone system, on every device.

One business number on the desk phone at reception, the softphone on your laptop and the mobile in your pocket. Plug in a headset in the office or at home, and calls reach your team wherever they are working.

Phones, softphones and Teams
A laptop running a softphone, a headset, an IP desk phone with a touchscreen and a mobile on a call, side by side on an office desk

Everything your phone system needs.

Seven modules. One platform. Built so every part of your telephony stack talks to every other part.

hub.metcom.cloud/voice
Overview
Overview
Overview

Your phone system, in one view.

Full cloud PBX dashboard giving you complete visibility across users, queues, trunks, and call flows. Real-time system health, active calls, and alerts all in one place.

Unified admin dashboard
Real-time active call visibility
Multi-site management from one login
No on-premise hardware required
Cloud PBX vs on-premise PBX

What actually changes when the phone system moves to the cloud.

A cloud PBX does the same job as the box in your comms cupboard: it routes calls, runs the auto-attendant and holds your extensions. The difference is where it runs, who maintains it, and what happens when something goes wrong.

Up-front cost
Cloud: No phone system hardware to buy. A monthly charge instead.
On-premise: The PBX box and its installation, bought up front.
Making a change
Cloud: Add a user, edit a call flow or create a queue from a browser.
On-premise: Often a technician visit or a booked remote session.
Updates
Cloud: Applied to the platform by us. Nothing to patch on site.
On-premise: Firmware and security updates on the box, usually under a maintenance contract.
More than one site
Cloud: Every site and extension in one dashboard.
On-premise: Each site may need its own system, or links between them.
If the office loses internet or power
Cloud: Calls follow failover rules to an alternate route or to staff mobiles.
On-premise: If the box or the lines into the building fail, so do the phones.
Working from home
Cloud: Staff take calls on a softphone wherever they are.
On-premise: Usually needs extra licences or a connection back to the office.
End of life
Cloud: No hardware refresh cycle.
On-premise: The box eventually needs replacing.

When on-premise still makes sense: if you own a system that is working well and is nowhere near end of life, there is no rush. The natural time to move is when the maintenance contract is up for renewal, the hardware is ageing, you are adding a site, or more of your team works away from the office.

Read the full guide: cloud PBX vs on-premise
Phones, softphones and Microsoft Teams

Answer the business number however your team works.

Metcom Cloud PBX works with desk phones, softphones and any SIP-compatible device, and it integrates with Microsoft Teams. Teams handles individual calling well. Reception, queues, wallboards and call centre reporting are where a proper phone system behind it earns its keep, so many businesses run both.

Desk phones

IP desk phones for reception and staff who want a handset. Existing SIP phones can often stay.

Softphone

Calls on a computer with a headset, in the office or at home, on the same business number.

Mobile failover

Calls can follow staff to their mobile, per extension, so the business number still reaches them.

Microsoft Teams

Make and take business calls inside Teams, with the PBX handling numbers, routing and queues behind it.

Moving across and number porting

Keep your numbers. Skip the downtime.

Your existing Australian numbers port across to Metcom Cloud PBX, and the new system is ready before they move, so callers never notice the change.

01

Scope

We map your numbers, sites, handsets and how calls should flow, and check what your current contracts allow.

02

Build and test

Users, call flows, IVR and queues are built and tested while your current system keeps running.

03

Port your numbers

You sign a porting authority. Your current carrier validates the numbers and confirms the port category.

04

Cut over

Calls move to the new system on the agreed date, with everything already set up and tested.

Porting timeframes depend on your current provider and the port category, so we confirm the expected timing for your numbers before you commit. Your numbers also stay yours to move: if you ever leave, you can port them to another provider at any time.

How cloud PBX pricing works

A monthly cost, not a capital purchase.

There is no phone system hardware to buy, so you pay for the system as a service. The price is built from a handful of things, and we quote it against your actual setup rather than a generic plan.

Get a quote

What sets the price

How many users need a phone
How many numbers and sites you have
Call centre features such as queues and wallboards
Add-ons such as AI voice agents and call recording
Call charges, per our call rate card
One-off porting charges, set by port category

Full charges for each service are set out in its Critical Information Summary.

Why Businesses Switch

Less to manage.
More that just works.

The real difference between a cloud PBX and what most businesses are still running today.

Zero
hardware. Ever.

No PBX box in the server room. No engineer callouts for firmware. No hardware refresh cycles. The system lives in the cloud. We look after it.

Quick
to get running

New users, new sites and number porting are all handled from the dashboard. No hardware to order and no waiting on a vendor to make a change.

Australian
support, always

Local team. Local numbers. Local PSTN connectivity. When something needs attention, you're talking to someone who actually knows your setup.

Running a call centre? See Metcom Contact Centre →·Telco or MSP? See our Partner Program →

FAQ

Frequently asked questions

A cloud phone system, also called a cloud PBX (Private Branch Exchange), is a hosted business phone system that replaces the traditional on-premise PBX box. All call routing, IVR, queues, and extensions are managed in the cloud, so there is no hardware in your server room and no engineer callouts for updates.
No hardware is required. The system is fully cloud-hosted and works with softphone apps, IP desk phones, or any SIP-compatible device. We provision everything from the dashboard.
Yes. We handle Australian number porting as part of setup. Your existing DIDs transfer to the new system and you manage them from the same dashboard as everything else.
Yes. The Cloud PBX is built for multi-site management from a single login. Extensions, call queues, and SIP trunks across unlimited sites are all managed in one place with no per-site admin portals.
We configure redundant carrier path failover on SIP trunks so calls can fall back to an alternate route automatically. We can also set up mobile failover rules per extension so calls reach staff regardless of connectivity.
A traditional PBX requires upfront hardware, vendor callouts for changes, and a separate maintenance contract. With Metcom Cloud PBX there is no hardware, we can have you up and running quickly, and everything is managed from a browser. No hardware refresh cycles, ever.
There is no phone system hardware to buy, so the cost is a monthly charge rather than a capital purchase. The price depends on the number of users, how many numbers and sites you have, whether you need call centre features such as queues and wallboards, and which add-ons you choose. Call charges follow our call rate card, and one-off porting charges depend on the port category, as set out in the Critical Information Summary. Tell us your setup and we will quote it.
Yes. Metcom Cloud PBX integrates with Microsoft Teams, so staff can make and take business calls inside Teams while the PBX looks after your numbers, call flows, auto-attendant and queues.
Often, yes. SIP-compatible IP desk phones can usually be connected to Metcom Cloud PBX. We check your handset models during scoping and tell you which can stay and which are worth replacing.
Yes. Staff can use a softphone on their computer wherever they are working, and calls can be set to follow them to a mobile, so the business number still reaches them away from the office.
It depends on your current provider and on the port category, which your current carrier confirms when it validates the numbers. Because the new system is built and tested alongside your existing one, nothing changes for callers until the port completes.
Yes. You can port your numbers to another provider at any time and we will cooperate with the request. Port them before the service ends, because numbers that are not ported may be lost 30 days after cancellation.
Yes. Metcom Contact Centre is built on the Cloud PBX and adds a softphone for agents, smart queues and routing, live wallboards, agent monitoring and detailed call analytics, all on the same platform.

Ready to move to the cloud?

Talk to us about migrating off your old PBX and what that looks like in practice.