Who sets up Microsoft Teams calling and business phone systems in Adelaide?
Subnet does. We are based in Forestville, Adelaide, and have designed and supported business phone systems for South Australian organisations since 2006. Since 2022 our voice services have run on the Access4 platform, with Microsoft Teams calling as the main focus. We design the call flows, port your numbers, supply handsets and headsets, train your staff and support the service afterwards.
Can we keep our existing phone numbers when we move to Teams calling?
Yes, in almost all cases. Existing numbers, including main lines and direct numbers, are ported from your current carrier to the new service. Porting is booked for an agreed date and time, and Subnet manages the paperwork and tests each number after it moves. Tell us early about fax lines, lift phones, alarms and EFTPOS lines, because they need their own plan.
How much does Microsoft Teams calling cost?
There are three parts: a Microsoft Teams Phone licence for each person who makes external calls, a calling plan and phone numbers from the carrier, and a one-off set-up and porting cost. Handsets and headsets are optional, since Teams works on a laptop or mobile. The total depends on how many people need external calling and how complex your call handling is, so Subnet quotes a fixed monthly price per user and a fixed project price.
What is the difference between Hosted Voice, UCaaS and CCaaS?
Hosted Voice is cloud calling: handsets or apps, numbers and call handling delivered as a service. UCaaS adds collaboration, such as messaging and meetings, alongside voice. CCaaS is built for teams that handle customer enquiries, adding queues, workflows, integrations and reporting. Contact-centre needs are scoped separately from day-to-day calling. Start with how your people actually communicate, then agree which service and configuration fit.
Should we use Operator Connect or Direct Routing with Teams?
Access4 describes both. Operator Connect is the more native route, where the operator runs the phone-network connection and numbers are assigned in the Teams admin centre. Direct Routing suits existing PBXs, SIP trunks, custom dial plans, multi-site setups and phased moves. Microsoft notes that Direct Routing relies on a certified session border controller and a SIP trunk, which the customer side provides and operates. Which route fits depends on your current phone system and how much control you need, and it is settled in scoping.
Can we move to the new system in stages instead of all at once?
Often, depending on the route chosen. Microsoft describes Direct Routing as able to run alongside Operator Connect and Calling Plans in the same Teams environment, so different groups of users can be on different arrangements during a transition. Microsoft also advises validating before production rollout and testing failover. Agree who moves first, how long the old and new systems overlap, what is tested before each stage and how people reach the right team during the changeover.
When is a Teams call queue enough, and when do we need a contact centre?
A Teams call queue holds callers, plays music, and distributes calls to agents using methods such as round robin or longest idle, with limits on queue size, wait time and agent numbers. That can suit a team or help desk. A contact centre service becomes relevant when you need wider workflows, integrations or reporting. Test your needs against Microsoft’s documented queue limits and ask what reporting you require before choosing. Decide how you will judge success after go-live.
How does emergency calling work with a cloud phone system?
It needs deliberate setup. Microsoft says administrators configure emergency addresses and locations, and routing depends on the phone-network option and client type. Users working away from the office may need to share location, and people can be prompted to confirm their address. Because roaming and remote staff change the location a call comes from, record how locations are maintained, who owns changes and how emergency calling is tested. Check Australian requirements with your provider.
Is our network ready for cloud voice?
Check it before go-live. Microsoft’s guidance covers bandwidth per user, quality-of-service settings, firewall access, split tunnelling for VPN traffic and Wi-Fi design. It links choppy audio to jitter and packet loss and recommends tools such as the Network Planner and Call Quality Dashboard in Teams. Review each location’s connection, how failures are handled and what you will do if a link is unavailable. Results from that review inform the proposed configuration.
Who do we contact if call quality drops?
Agree that before go-live. Responsibility is split. For Operator Connect, Microsoft says the operator handles phone-network troubleshooting while Microsoft supports Teams itself. With Direct Routing, the customer side and its equipment vendor carry more of the investigation. Your network, devices and Microsoft 365 settings can also be the cause. Record who triages a report, how issues are handed between teams and what information users should collect.