How do you set up UCaaS for a remote team?

Start with the parts that don't depend on where anyone sits. Take a team on Microsoft Teams with Atlantech Online as its carrier. Each worker needs a Teams account and a Teams Phone license, which makes Teams their phone system. Calls to and from outside numbers need a carrier. This walk-through gives each person a direct number. Teams can also share one number across a group, which changes the number step.

With Operator Connect, Microsoft's planning page says the operator runs the phone network side and your administrators manage users in the Teams admin center. You enable the operator there and assign its numbers to people. Microsoft requires those users to be in Teams Only mode. The numbers can be new ones from the operator or existing ones ported over, and moving numbers off an office PBX has a timetable of its own.

Atlantech's Operator Connect service is priced "as low as $3 per user/month" for the carrier's part, with number porting listed. Microsoft's licenses are a separate requirement. The number is assigned on an admin screen, and calls arrive in the Teams app on the worker's laptop and mobile phone, so this part can be done remotely.

A team that doesn't use Teams follows the same order with a hosted phone service. Atlantech's UCaaS page lists mobile apps for Android and iOS. Its Premium Line, which lists a softphone, starts at $18 per user a month. The plan you choose decides which features remote staff get. The setup order stays the same.

A laptop app and a headset are enough to make and take calls, and a mobile app covers time away from the desk. A desk phone at home is optional.

In Teams the choice has a consequence for 911. Microsoft's page on emergency addresses for remote locations, which covers 911 calling in the United States, says the work-from-home address experience runs on Teams desktop for Windows and Mac. Teams mobile supports automatic location detection, but a user can't enter an address there. Teams phones don't support the work-from-home experience at all.

For that reason we'd make the desktop app the standard device for a remote team. A worker whose only device at home is a Teams desk phone can't confirm a home address on it. Settle with your administrator and carrier how that phone's address will be set before you send one home.

An office phone can carry the building's address. A remote worker who dials 911 needs help sent to their home. In the United States, the FCC's rule for multi-line telephone systems covers this case for a business phone system that falls under it. Since January 6, 2022, an off-premises device associated with such a system has had to provide automatic dispatchable location where that is technically feasible. Otherwise it provides a location based on the user's manual update or on enhanced location information.

In Teams, the administrator creates an emergency calling policy with external location lookup turned on and assigns it to remote users. Each user can then add, edit or confirm an address on the Calls tab. Teams saves that address for the network the user is on and uses it automatically whenever the app is connected to that network. Signing out clears the saved addresses.

How the address was set changes how a 911 call is handled. Microsoft's table says an address suggested by the operating system and confirmed by the user sends the call directly to the 911 center. An address typed in by hand and confirmed is screened first and then transferred. What matters most is that the address is correct and complete. If the suggested one is right, the user confirms it. If it isn't, the user corrects it, and a screened call with the right address is the better outcome.

The record can be checked without calling 911. Microsoft says Calling Plan, Operator Connect and Teams Phone Mobile users in the United States and Canada can dial 933. The call reaches a bot that reads back the caller's number and emergency address. It also says whether a real call would go straight to the 911 center or be screened first. Atlantech documents a similar 933 readback for phones on its own service.

Make that a first-day task. The new hire confirms the address at home, dials 933 and reports what they heard. They do it again after a move. The readback checks the record, and it doesn't show who inside the company gets told. That is set in the emergency calling policy, which can notify a security desk when someone dials 911. A remote team has no security desk down the hall, so decide who receives that alert. For phones outside Teams, the steps differ by provider, and registering a VoIP phone for 911 starts with the same question of where the phone is used.

Suppose 25 people work from home. That is 25 internet connections and 25 WiFi setups, with no shared office circuit to size. A speed test at headquarters describes none of them.

Speed doesn't settle it for a voice call. Microsoft's network guidance for Teams puts the recommended bandwidth for audio at 58 kbps up and down per endpoint, and 1,500 kbps each way for one-to-one video. A home connection can clear those figures and still produce bad calls. The figure says nothing about whether packets arrive steadily over the WiFi between the laptop and the router.

Microsoft's notes on WiFi explain why. WiFi networks aren't necessarily designed for real-time media. The 2.4 GHz band is often affected by other consumer devices, and the 5 GHz band is better suited to calls. So when one person's calls break up, start with their WiFi. A day on a cable from the laptop to the router is a cheap test. If the calls improve, WiFi is the likely cause.

If staff connect through a company VPN, that is a part of the home setup the company controls. Microsoft recommends a split-tunnel VPN, in which Teams traffic goes directly to Microsoft and the rest stays in the tunnel. Its reasons are specific. VPNs typically aren't designed for real-time media, some don't support the UDP traffic Teams needs, and routing calls through a VPN device can add latency and jitter. That is a change to the VPN's configuration. It isn't advice to switch the VPN off.

Microsoft's advice on prioritizing voice traffic is written for a managed network, so it applies at home only if you manage the worker's router. A call quality problem reported by one remote worker is investigated in that worker's setup first. The same complaint from many homes at once points to something they share.

When a remote worker says calls sound bad, nobody can walk over to the desk. Support needs evidence from the call itself. Microsoft's network guidance separates two tools. The Call Quality Dashboard shows aggregate quality across the organization, which is where patterns show up. The Teams admin center lets an administrator investigate calls for an individual user.

For a single report, start with the second tool. So the report from the worker should include the time of the call and who it was with. The administrator opens that call and reads what the network and the device were doing. The dashboard is where a problem shared by many homes would show up.

Microsoft's planning page for Operator Connect draws the line between the two companies. Microsoft is responsible for Teams, the admin center and the integration with Operator Connect. The operator is responsible for the phone network connection, number provisioning and porting, the calling service and troubleshooting on its side. Atlantech lists 24/7 support in its Operator Connect price.

One question helps sort the reports. Ask whether the trouble also happens on a Teams call to a colleague. A call between two Teams users in the same organization stays inside Teams by default, so the carrier isn't part of it. If that call is bad too, start with the worker's device and network. If Teams calls are clear and only calls to outside numbers fail, check the user's license and calling policies. Then take it to the carrier with the time of the call and both numbers.