Business telephony, without the legacy cost.

Yes. We port your existing numbers — geographic, 13/1300/1800, and direct-inward-dial ranges — from your current carrier to the new platform. We coordinate the carrier handover end-to-end: porting paperwork, scheduled cutover window, parallel running where the size of the estate warrants it, and a documented rollback plan if the port hits an issue. Most ports complete in 10–20 business days; complex ranges (multi-site, mixed-carrier, or legacy ISDN numbers) can take longer and we’ll tell you that up-front rather than after you’ve signed. The honest limitation: a small number of legacy carrier products are genuinely difficult to port off — usually older Telstra or AAPT inventory. Where that’s the case, we’ll set out the options (port, redirect, retire) before you commit.

The handsets fail over to mobile via the softphone app, so users keep making and receiving calls on the same number. Inbound calls can be configured to roll to a backup mobile, voicemail-to-email, or another office line. That’s the answer to the question as asked, but it’s not the question that actually matters. The more important question is how often your internet drops in the first place. A VoIP migration is the right moment to look at your connectivity: is the circuit a residential-grade NBN that drops for an hour every few weeks, or is it a business-grade service with an SLA and a failover circuit? We almost always pair a VoIP cutover with a connectivity review for that reason.

Yes. We deploy Teams Phone via either direct routing (your own session border controller and SIP trunks routed into Teams) or Operator Connect (carrier-provisioned trunks into Teams without the SBC). Which path is right depends on the tenant size, the existing telephony estate, and how much call-flow customisation you need. For straightforward deployments — calling plans, voicemail, basic call queues — Operator Connect is usually cleaner. For deployments with complex IVR, recording obligations, or integration with a contact-centre platform, direct routing gives you more control. The honest limitation: Teams Phone is excellent for knowledge workers but it isn’t a contact-centre platform. If you’re running a call centre with serious queue management and analytics needs, we’ll recommend a dedicated platform instead and tell you why.

Per-extension subscription plus call charges, with the exact number scoped per engagement. Every business has a different mix: number of users, call volumes (inbound vs outbound, local vs mobile vs international), feature requirements (recording, IVR, queues, Teams integration), and whether new handsets are needed. We quote against your last three months of call records rather than a generic per-seat figure, because the bills people are actually trying to replace are rarely uniform across a head-count. There are no per-incident fees or after-hours uplifts for support. The honest limitation: we don’t publish a public rate card. Pricing claims that survive contact with reality have to take account of your call profile, so we’d rather scope it accurately than headline a number that doesn’t apply to your business.