The phone system in most small businesses is older than the computers. A box in a closet, handsets with buttons nobody has pressed in years, and a bill from a carrier that keeps going up. Moving the phones to the cloud fixes a lot of that. It also changes some habits, so it is worth knowing what moves and what stays put.

The examples below use Microsoft Teams Phone because Microsoft documents its settings in detail. If you choose another cloud phone system, ask the provider for its equivalent of each setting.

How a cloud phone system works

In a cloud phone system, the switchboard that used to sit in the closet runs in the provider's data centers. Your numbers live in the provider's system and are assigned to people, auto-attendants or call queues. Desk phones, laptop apps and mobile apps sign in over the internet, which is why one number can ring all three.

The provider also connects your calls to the public telephone network. Teams Phone offers four ways to do that: a Microsoft Calling Plan, with Microsoft as the carrier; Operator Connect, through a participating carrier; Teams Phone Mobile, through a mobile operator; and Direct Routing, which links any carrier through a certified session border controller run by you, your integrator or a Direct Routing service provider. Teams Phone Mobile covers only numbers assigned to people, so a main number answered by an auto-attendant needs one of the other three. Each person who makes or takes outside calls also needs a Teams Phone license.

What changes

The number follows the person. One business number per person rings on the desk phone, the laptop app and the mobile app, in the order you choose. Working from home or on site stops being a reason to miss calls. In Teams, each person adds to this under Settings, Calls, Call handling and forwarding, where a call can also ring another number at the same time, a contact, a call group of up to 25 people or a delegate.

The menu sounds like you. An auto-attendant with your business hours, your holiday schedule, "press 1 for sales," ring groups, queues and overflow, set up around how customers actually reach you rather than around what the old box could do. In Teams, an auto-attendant can route business hours, after hours and holidays differently and let callers search the directory by name. A call queue can redirect callers when nobody is signed in, too many people are waiting or the wait runs too long, but queues have no after-hours or holiday routing of their own, so Microsoft recommends an auto-attendant in front of them.

Voicemail lands in email. Transcribed, with the audio attached, in the inbox. Nobody dials in to check messages. In Teams, voicemail goes to the person's Exchange mailbox as an email with the recording attached and, if transcription is on, the transcript. Microsoft warns that a mail rule blocking its no-reply voicemail sender stops messages arriving, and the messages are not DKIM-signed, so check your spam filtering after the move.

Customers can text the office. Where the platform supports it, business texting goes to the same number, and replies come from it. Ask the provider whether texting needs carrier registration and who completes it. Twilio's documentation describes A2P 10DLC as the standard US carriers put in place so that texts sent from software over ordinary ten-digit numbers are verified and consensual, with registration covering a brand, which identifies the sender, and a campaign, which describes the messages and how people opt in and out.

Changes are a request, not a visit. A new hire, a new office, a new schedule: one call to the help desk, done the same day. No waiting for the phone company.

What does not change

Your numbers. Existing business numbers are ported to the new system. The port is planned with the carriers on a date, and calls are forwarded during the switch so nobody rings an empty line.

Desk phones, if you want them. Some people want a handset. They can have one. Others are happier with the app. Both work on the same number.

Check that the handsets are supported before you buy; a shared lobby phone in Teams, for example, needs a certified phone and a Teams Shared Devices license. If your desk phones take their power from the network cable, they go dark when the network switch loses power, so put the switch, router and modem on a battery backup.

Emergency calling. This one matters. A 911 call from a laptop app needs a verified address for every site and every remote user, so it goes to the right place. It is set up as part of the move, not left to chance.

Porting your numbers without a gap

Porting moves a number from one carrier to another. The new carrier submits the request, and the old carrier either rejects it or approves it with a firm order commitment, which sets the date the numbers move. Microsoft says the old carrier's response window in the United States is three to five business days, and a corrected request starts that clock again.

Mismatched details are the most common cause of errors and delays, according to Microsoft. Ask the current carrier for its Customer Service Record, the official record of your account, and confirm:

  • Every number on the account, including fax, alarm and toll-free numbers.
  • The account number and any account PIN, which is not the same as a freeze PIN.
  • The billing telephone number, the main number the account is filed under.
  • The business name and service address exactly as the carrier has them.
  • The person listed as authorized on the account.
  • Whether the account has a freeze that blocks ports.

Microsoft's porting guide flags other traps. Turn off carrier features such as call hunting and distinctive ring before the port, and clear any open orders or pending disconnects with the old carrier. Removing a freeze takes an order from the authorized person and can take one to three weeks. The authorized person cannot be changed during a port, so update it first if the person on file has left.

Check what else rides on the numbers. Microsoft warns that other services tied to a ported number, broadband included, are disconnected when the port completes, and that numbers used for DSL or broadband connections cannot be ported. Fax needs its own plan, because Teams can take over a fax number but will not send or receive faxes. Carriers also process only one port at a time for each account, so a second batch waits until the first is done.

For Teams Calling Plans, Microsoft says a port typically takes 7 to 14 days from start to finish and can take up to 30. It recommends a target date at least 15 business days after you submit, and the date cannot be more than 30 calendar days out. US user numbers can be scheduled between 8 a.m. and 8 p.m. Eastern, but some carriers' porting teams stop at 5 p.m. Eastern, so a late-day port can leave a problem until the next business day; pick a morning. If the date has to move, Microsoft's US guidance asks for changes at least two business days before the approved date and cancellations at least one business day before.

Above all, do not cancel the old service first. Disconnected numbers cannot be ported, so the old account stays open until every number has moved and been tested. Then work with the old carrier to confirm the account is closed; Microsoft calls that best practice even though a full port might close it automatically.

Getting emergency calling right

FCC rules adopted under Kari's Law and RAY BAUM'S Act apply to multi-line telephone systems made, imported, sold, leased or installed after February 16, 2020, and the FCC's definition of those systems names VoIP alongside PBX and key systems. In plain terms, anyone must be able to dial 911 directly, with no 9 or other prefix first. Where the system can be configured to do it without new hardware or software, a central point such as a front desk, or another person or organization, is notified when 911 is called, without delaying the call. And the call carries a dispatchable location: the validated street address plus the suite, floor or similar detail needed to find the caller.

Phones and apps used away from the office must send an automatic dispatchable location where technically feasible, or else an address the user updates or the best location other technology can provide at reasonable cost. If the system falls short, the FCC's rule presumes that whoever manages it is responsible. Interconnected VoIP providers must also warn subscribers that 911 may not work, or may be limited, when equipment is moved, the internet connection fails or the power goes out, so make sure staff know to use a mobile phone in those cases.

In Teams, the setup comes down to a handful of settings:

  • Add each site's emergency address in the Teams admin center with the map search, which validates it and adds the geo code that dynamic routing needs, then add places for floors or offices.
  • List the office's public IP addresses as trusted IPs, and map its subnets, switches or Wi-Fi access points to the right address so office calls carry the right location.
  • Turn on External location lookup mode in an emergency calling policy so people using the Teams desktop app at home can confirm their address; Teams desk phones do not support this, and the mobile app relies on automatic location.
  • In the same policy, choose who is alerted when someone dials 911 and the notification mode, from a Teams chat message only to joining the call, either muted or able to speak.
  • Turn off the Web PSTN calling setting in a Teams calling policy for anyone who uses Teams in a browser, because dynamic emergency calling and security desk alerts do not work in the web client.

The mapping matters. For US Calling Plan users, Microsoft sends a 911 call straight to the local 911 center when the Teams client is at a location the administrator has mapped, and screens other calls first at a national call center that confirms where the caller is. Microsoft's guide to remote locations shows which home addresses also go direct, such as a suggested address the user has confirmed, and which are screened, such as one typed in without using the address suggestions.

Then test it. Calling Plan, Operator Connect and Teams Phone Mobile users in the United States can dial 933, a test line that reads back the calling number, the emergency address and whether a real call would go straight through or be screened first; Direct Routing customers arrange a test with their emergency routing provider. Set the emergency calling policy so 933 calls do not alert the security desk, allow up to four hours for network setting changes to reach Teams clients, then test from a desk phone, an office laptop and a laptop at home.

The one thing people forget

A cloud phone system is only as good as the internet connection and the network it runs on. Voice traffic has to be prioritized on the Wi-Fi and the router, or calls stutter and everyone blames the phones. Checking the connection and fixing the network comes before the first handset is plugged in.

A voice call needs little bandwidth. Microsoft recommends 58 kilobits per second in each direction for a one-to-one Teams audio call, against 1,500 for one-to-one video, and notes that congestion greatly affects call quality. It describes the symptoms: jitter causes missing words or syllables, packet loss makes speech hard to understand, and delay makes people talk over each other.

Quality of Service, or QoS, marks voice packets so the router and switches send them first, and Microsoft recommends it before adding bandwidth. Every device in the path needs the same settings, and QoS only helps on the network you manage, not across the internet or on someone's home connection. For Teams, Microsoft's starting point marks audio from ports 50,000 to 50,019 with DSCP 46, known as Expedited Forwarding, and the Teams admin center setting Insert Quality of Service (QoS) markers for real-time media traffic must be on.

On Wi-Fi, Microsoft recommends QoS or Wi-Fi Multimedia (WMM) and favors the 5 GHz band, since the 2.4 GHz band is often affected by other devices. It suggests band steering to move dual-band devices onto 5 GHz and channels that do not overlap on neighboring access points. It also recommends keeping calls off VPNs, or using a split tunnel that sends Teams traffic around the VPN.

Two router issues are worth checking. If your phone system uses SIP (Session Initiation Protocol) to set up calls, check whether the router's SIP ALG (application layer gateway) feature is on. The IETF's guidance on getting SIP through routers says experience shows these gateways can harm SIP, including by not working with encrypted signaling, so ask the phone provider whether it wants the feature on or off. The other is bufferbloat, where latency climbs while the line is busy, which Microsoft says is often down to the buffers in consumer network gear filling up.

To check an office connection for Teams, run the Microsoft 365 network connectivity test at connectivity.m365.cloud.microsoft from a Windows PC at the office during a busy hour. Most of its tests run in a small Windows app it asks you to download, which needs the .NET 6.0 Runtime, and installing that runtime takes administrator rights. Signing in saves the report to your Microsoft 365 tenant. It flags bufferbloat of 100 milliseconds or more, and its Teams checks pass when a 10-second test audio call shows packet loss under 1 percent, latency under 100 milliseconds and jitter under 30 milliseconds.

Plan for outages too. If the office loses internet or power, the desk phones there stop working, but the auto-attendant and voicemail keep running in the cloud and the mobile app can still work over cellular data. Decide in advance where calls should go when the office is down.

This is also why the phones and the network should be looked after by the same people. When a call drops, you want one help desk that can see the router and the phone system, not two vendors blaming each other.

Which system

If your team lives in Microsoft Teams, Teams Phone puts calling in the app they already have open. If not, a cloud phone system is the better fit. The right answer depends on how your team works, and the honest provider tells you which fits and what it costs rather than selling the one with the biggest margin.

These questions usually settle it:

  • Does the team work in Teams all day, with email in Microsoft 365?
  • Do you need business texting, fax, call recording or queue reports?
  • Which desk phones, headsets and shared phones will you need, and are they supported?
  • Who is the carrier, and who fixes a wrong number or a wrong 911 address?
  • What happens to the alarm, elevator and card terminal lines?

One Teams detail matters here. Cloud Voicemail delivers only to an Exchange mailbox and does not support third-party email systems, so voicemail in the inbox needs your email on Exchange, such as in Microsoft 365.

What it costs

Cloud phones are usually priced per user per month, plus desk phones if you want them. For many small businesses that lands below the old carrier bill once the maintenance contract and the line rental are added up, but not always. The only way to know is to put the two side by side, in writing, before you move.

On the new side, count:

  • The per-user license and the calling plan or carrier charge.
  • A number for each auto-attendant or queue that outside callers dial, and any toll-free line.
  • Desk phones, headsets, shared-phone licenses and network upgrades such as a battery backup.
  • Taxes, regulatory fees and one-time setup or porting charges.

On the old side, add line rental, long distance, the maintenance contract and any early termination fees, and note each contract's end date and notice period. In Teams, each auto-attendant or queue runs on a resource account with a free Teams Phone Resource Account license. With Microsoft Calling Plan numbers, also budget for a funded pay-as-you-go plan or Communications Credits if an auto-attendant or queue transfers callers to outside numbers.

How the switch happens

  • Map how calls flow. Who calls, who answers, when, and what happens when nobody can. Written down before anything is touched.
  • Pilot. A few users on the new system while the old one keeps ringing. Routing, devices and call quality checked on real calls.
  • Port and cut over. Numbers move on the planned date, with forwarding in place during the switch.
  • Run it. Moves, adds and changes through the help desk from then on.

For the map, list every number and where it rings, the hours, the holidays, who covers lunch and where unanswered calls go. Then call your main number after hours and note what callers hear. The new auto-attendant is built from that map, not from the old box's settings.

During the pilot, test the awkward cases: a transfer, a call nobody answers, a long wait in the queue, Wi-Fi at the far end of the building and a laptop at home. In Teams, the Make a test call option under Settings, Devices has a test bot record a short message, play it back and show a summary of how the microphone, speaker and camera are working.

On port day, keep the old system connected until the numbers have moved, then check:

  • The main number reaches the auto-attendant, and each option goes where it should.
  • Direct numbers ring the right person on every device.
  • After-hours and holiday routing play the right greeting.
  • Voicemail arrives in email with the recording and, if it is on, the transcript.
  • Outbound calls show the expected number, which Teams sets in a caller ID policy.
  • A 933 test from each kind of device reads back the right address.
  • Fax, alarm and other special lines work or have moved to their new home.

For problems with newly ported Teams numbers in the first 24 to 48 hours, Microsoft points customers to its Phone Number Service Center, and to Microsoft support after that. From then on, review the emergency addresses whenever a site is added, the office network changes or a remote worker moves house.

Common mistakes and how to spot them

  • A port order stuck at Exception. In Teams this status means the old carrier rejected the order, and Microsoft puts exceptions down to incorrect details such as the PIN or ZIP code, so compare every field with the Customer Service Record.
  • Forgotten lines. Alarm panels, elevator phones, fax machines and card terminals show up on the bill, not in the call-flow map.
  • Remote workers without a 911 address. If a 933 test from a home laptop reads back the office, the setup is not finished.
  • Static, cut-outs or robotic voices. Microsoft links them to jitter or packet loss, so look at the network before the phones.
  • Missing voicemail. Look for mail rules or spam filters that block Microsoft's no-reply voicemail sender.
  • A menu built from the org chart. If callers need three key presses to reach the person everyone asks for, rebuild it.

A worked example

Imagine a twelve-person accounting office with a main number, ten direct numbers, a fax line and an alarm line, all on one carrier account billed under the main number. Two partners work from home on Fridays, the office runs on Microsoft 365, and tax season brings a rush of calls.

The owner picks Teams Phone with a Calling Plan. Most callers want an appointment or a particular accountant, so the auto-attendant offers two options and a dial-by-name directory. Appointment calls go to a queue that rings three staff and falls back to shared voicemail if the wait runs long.

The connectivity test flags bufferbloat, and a walk-through finds the back-office Wi-Fi on a busy 2.4 GHz channel. The router is reconfigured to fix the bufferbloat and apply QoS, the switches get the same settings, the access points steer devices to 5 GHz, and the network gear goes on a battery backup. A second test at the same busy hour passes.

The Customer Service Record lists a former partner as the authorized person, so that is fixed first. The main number is the billing number and the alarm line stays with the old carrier, so the port order names the alarm line as the account's new billing number. The fax number moves to a fax service in a separate port afterward. The main port is booked 15 business days out, for a Tuesday morning, while three staff pilot the system.

Emergency setup is one validated address with the floor as the place, the office network mapped, External location lookup mode on for the partners and alerts to the office manager. On port day, 933 tests from a desk phone and a home laptop read back the right addresses, and only then does the owner confirm with the old carrier which lines have closed.

What to do this week

  • Pull the latest bill from every phone carrier and list every number, including fax, alarm, elevator and toll-free lines.
  • Ask the carrier for your Customer Service Record and check the authorized person, the service address and any account freeze.
  • Call your main number after hours and write down what callers hear.
  • Find the end date and notice period of the phone contract and any maintenance agreement.
  • Test call quality on the office connection during a busy hour.
  • Note who works where, who wants a desk phone and who will be happy with the app.

Where ALCO can help

ALCO deploys Microsoft Teams Phone for Microsoft 365 clients and a cloud phone system for everyone else, chosen with you based on how your calls flow, the devices you want and your budget, with the choice and the price in writing. We port your numbers without a gap, build the auto-attendant and routing, set up desk phones and apps on one number per person, verify emergency addresses for every site and remote user, and check and fix the network for call quality. We also find the lines that still matter, such as the fax, the alarm panel and the elevator phone, and plan for each before anything is canceled.

The phones are then looked after by the same help desk that looks after the computers. It is staffed 24 hours a day, including holidays, and calls are answered by a person. The full scope is at alcohq.com/services/phones-and-voip if you want the detail.

If your phone system is a box in a closet, the box is not the problem. The missed calls are.

Sources