Do Cloud Phones Need Internet? What to Plan For

A customer calls your main number while the office internet is down. Does the call fail, ring an employee's mobile app, or follow an after-hours message? The answer explains whether cloud phones need internet and, more importantly, whether your organization has planned for the loss of it.

Local Business VoIP is the small-business site of Carolina Digital Phone, Inc., a hosted phone provider based in Greensboro, North Carolina since 2000. I have answered the question in this headline for twenty-six years, first to business owners who were nervous about leaving copper lines, and now to owners who have no choice because the copper is being retired. The honest answer has not changed. The planning advice has gotten a lot better.

Why do cloud phones need internet at all?

Because the phone system itself is not in your building anymore. With a cloud phone system, the PBX, which is the equipment or service that directs calls, extensions, voicemail, queues, and auto attendants, runs in the provider's network rather than in a phone closet at your office. Your desk phone is a well-made endpoint with a screen and a handset, but it does nothing useful until it registers with that service through your internet connection.

When someone dials your business number, the cloud platform receives the call and follows the rules you set. It may ring a receptionist, send the call to a sales queue, ring several people at once, or play an after-hours greeting. Once the platform decides where the call should go and sends it toward a desk phone or an app, that device needs a working internet path. If the path is gone, the platform cannot reach the device, and it has to do something else with the call.

This design is the reason a Greensboro office, a field employee in High Point, and a manager working from home can share one phone system and one set of extensions. It is also the reason you have to think about more than the provider's uptime. Your local internet service, your router or firewall, your switches, your Wi-Fi, and your electrical power are all links in the chain. Any one of them can break the connection to the phone on your desk while the provider's network is perfectly healthy.

If you are still deciding whether to move at all, the AT&T copper retirement is making the decision for a lot of North Carolina businesses this fall. Copper lines drew their own power from the phone company's central office, which is why old desk phones rang during a blackout. Cloud phones do not have that. They have something better, but only if you set it up.

What happens when your internet goes out?

An internet outage takes down the phones at the affected site, not your business number. The cloud platform can still receive calls if it is operating normally. The question is where those calls should go next, and that question has to be answered before the outage, not during it.

For a small office, a practical failover plan sends calls to a receptionist's mobile app, then to another staff member if the first person does not answer, then to a voicemail box that someone actually checks. A larger organization may send calls to a backup site, a remote queue, or a recorded message that gives callers another way to reach the team. Both approaches work. Neither one happens by itself.

This is why the call flow deserves attention. Forwarding every call to one employee's personal phone might be acceptable for a five-person firm, but it is rarely enough for a medical practice, school district, municipal department, or busy service business. You need to decide who answers, what information they need in front of them, and how they transfer or document calls while the main site is unavailable. We have written about how that looks for a municipal office and for a healthcare practice, and the shape is the same in both: a short list of calls that matter, a named destination for each, and a test.

Outgoing calls are different. A desk phone without internet cannot reach the cloud service, period. Employees can usually make business calls through a mobile app using cellular data, provided their phones have signal and the app was configured in advance. Remote staff can keep working from any other internet connection, because to the platform they are just another registered device. These are real continuity options, and they are the reason our customers rarely lose a full day of phones. They are not substitutes for testing your plan.

What callers hear with no plan in place

With no failover rule, most cloud systems send unreachable calls straight to voicemail. That is better than a fast busy signal, but a customer who needed a person at 10 a.m. on a Tuesday is not comforted by a greeting recorded two years ago. Some of them leave a message. Many of them call the next listing in the search results. You will not see those calls in any report, because from the platform's point of view the call was handled.

How much internet speed do cloud phones really need?

Much less than most people assume, and speed is almost never the problem. A standard business voice call using the G.711 codec needs roughly 80 to 100 Kbps in each direction once you count the packet overhead. Ten simultaneous calls need about one megabit up and one megabit down. A fifty-person office with a 100 Mbps connection could run every phone at once and barely register it on a bandwidth graph.

Problems come from connection quality, not from the download speed advertised on the internet plan. Three measures have a direct effect on conversation quality:

Latency is the delay between speaking and hearing the other person. The ITU's G.114 recommendation, which carriers have used for decades, treats one-way delay under 150 milliseconds as acceptable for most conversations. Above that, people start talking over each other.

Jitter is variation in that delay. Voice packets are supposed to arrive every 20 milliseconds like a metronome. When they arrive in clumps, the phone's buffer runs dry and speech sounds broken, robotic, or uneven. Most engineers want jitter under 30 milliseconds.

Packet loss means pieces of the voice data never arrive. Even one percent loss produces clipped words and gaps, because there is no time to resend a piece of a live conversation. We look for well under one percent on a healthy office network.

A location can have fast internet for web browsing and still have poor calls when large uploads, guest Wi-Fi use, security cameras, cloud backups, or a saturated upload link compete with voice traffic. The symptom that gives it away is calls that sound fine at 7:30 a.m. and terrible at 10:15 a.m. Nothing about the circuit changed. The office woke up. We covered the diagnosis side of this in what your network needs for good call quality and in what causes one-way audio, which is the most common complaint we hear from offices that moved to the cloud without a network review.

Wired desk phones, QoS, and why both matter

Wi-Fi is fine for mobile workers and laptops, but desk phones perform more predictably on wired Ethernet. A wireless network shares airtime with every device in range, so jitter climbs exactly when the office is busiest. If a desk phone must be wireless, give it its own network name and keep guest devices off it.

Your network should also prioritize voice traffic. This is commonly called Quality of Service, or QoS. In plain terms, it tells your firewall and switches to handle a live phone conversation ahead of a non-urgent file download. QoS helps enormously on your own network. It cannot fix a failing ISP connection or a poorly managed network at a remote employee's home, because your settings stop at your building's edge.

Plan capacity for busy periods, not for headcount

Do not estimate bandwidth from the total number of employees. Estimate the highest number of calls likely to happen at one time, then add the other critical applications that share the connection. A school office sees its peak during arrival and dismissal. A property management company gets a surge the morning after a storm. A county department may need extra headroom during an emergency or a public meeting. A network readiness review should examine the circuit type, firewall, switching equipment, Wi-Fi design, existing traffic, and any sites that rely on point-to-point links. It should also tell you honestly whether a second internet connection makes operational and financial sense, because for some offices it does not.

Do cloud phones work during a power outage?

Only if the equipment that carries them has power, and that is the dependency people forget. Internet service at the building is not useful if the modem or fiber terminal, the firewall, the network switch, the Wi-Fi access points, and the desk phones themselves have no electricity. Most business desk phones draw power from the switch over the Ethernet cable, which means a dead switch is eight dead phones even if the modem is humming along on its own battery.

A battery backup, usually called a UPS, keeps selected network equipment running through a brief outage. It should be sized and tested for the equipment it actually supports. The most common mistake we find on site visits is a UPS that keeps the router running but not the switch that powers the phones. The lights on the firewall look fine, and nobody can make a call. The second most common mistake is a UPS that was installed in 2019 and has a battery that now lasts about ninety seconds.

For longer outages, organizations use a generator, mobile apps on cellular service, or call forwarding to another site. The right choice depends on the consequences of missed calls. A law office may need continuity for client calls and nothing else. A school or municipal office needs a documented communication plan that covers multiple buildings and staff roles, and that plan needs to work when the building's network is dark. The telecom resilience guide on this site walks through how to size each layer.

What the FCC requires, and what it does not

Federal rules on backup power are aimed at residential and small-business lines, and they put the choice in your hands. Under 47 CFR 9.20, providers of covered voice services must offer customers the option to buy a backup power solution capable of eight hours of standby, and later twenty-four hours, so that 911 remains reachable during a commercial power loss. The rule requires the offer and the disclosure. It does not require you to buy the battery, and it says nothing about the switch that powers your desk phones. In practice, the FCC's own consumer guidance on VoIP and 911 warns plainly that VoIP may not work during a power outage or when the internet connection fails. Treat that as the baseline you are planning against, not as an argument against the technology.

How does 911 work on cloud phones when the office is down?

A desk phone with no internet cannot dial 911, so your emergency plan has to include a device that can. The FCC requires interconnected VoIP providers to deliver 911 as a standard feature and to route each call to the correct dispatch center. Enhanced 911 planning deserves its own attention: cloud systems support emergency calling well, but administrators must keep each user's dispatchable location current when phones move between rooms, buildings, or remote work locations. A dispatchable location gives responders a floor, suite, or room number instead of a street address alone. Your provider configures the service. Your organization maintains the location details as people and devices move, and that part is a habit, not a project.

During an outage, the practical answer is simple. Cell phones always dial 911. A business mobile app can dial 911 and will present the location you registered for that user. Make sure the people who are most likely to be alone in the building during a problem, usually the front desk and the facilities staff, know which device to pick up. We say more about the standards behind this in what Next Generation 911 means for your business.

What does each kind of outage actually do to your phones?

It helps to separate the failures, because the fix for each one is different. This is the table we sketch on a whiteboard during most first meetings.

Notice that the first four rows are inside your building and the last one is not. Business owners often spend their worry on the provider row and almost none on the switch in the closet. Spend it the other way around. A reputable hosted provider has already engineered the platform for failure; we explain our own approach in geo-redundant VoIP service. The closet is yours.

How do you make cloud phones more reliable?

A sensible continuity plan does not need to be complicated, but it must be specific. Start by documenting what must keep working first: the main number, emergency lines, front desk calls, dispatch, or a key department queue. Then decide how each item behaves if the primary site loses internet or power. For most organizations the plan has four parts, and the steps below walk through building them in order.

1. List the calls that must keep working firstWrite down the main number, any emergency or dispatch line, the front desk, and the one or two department queues that cannot go quiet. Rank them. Everything else can wait for the site to come back.
2. Decide where each important call goes when the site is darkFor each item on the list, name the person, mobile app, remote queue, or recorded message that answers when the office has no internet. Name a second destination for when the first does not pick up.
3. Build the failover rules in the cloud platformHave your provider configure a ring group or time condition that detects unreachable desk phones and sends calls to the destinations you chose, with no one having to log in and change anything during the outage.
4. Install and configure the mobile app before you need itEvery person on the failover list needs the business app signed in on their phone, with cellular data allowed and notifications on. Confirm each one can place and receive a call from the business number today.
5. Protect the equipment that carries voicePut the modem or fiber terminal, firewall, and the switch that powers the phones on a battery backup sized for at least the runtime you need to move calls elsewhere. Label the outlets so no one unplugs the wrong device.
6. Test it twice a year and write down what callers heardUnplug the internet on a quiet afternoon, call the main number from a cell phone, and follow the call. Record who answered, how long it took, and what the caller heard. Fix what surprised you and put the next test on the calendar.

A second internet circuit can add valuable protection, but it is not automatic protection. If both circuits enter the building through the same conduit, land on the same firewall, or depend on the same power strip, one incident still takes out both. Ask how each connection enters the site, how failover works, and whether your firewall can switch between them without anyone touching it. A cellular backup modem on the firewall's second WAN port is the most cost-effective version of this for a small office, because the cell network is physically separate from whatever the contractor's backhoe just found.

For multi-location organizations, another office can be part of the plan. Calls move between locations without the caller knowing a site is unavailable. This works particularly well for professional offices, campuses, and public agencies where staff are already trained to handle another department's calls. Our guide to routing after-hours calls covers the same time-condition and ring-group tools you would use here.

The federal Ready Business program and the Small Business Administration both make the same point about continuity planning in general: the businesses that recover are the ones that wrote the plan down and rehearsed it. Phones are the part of that plan your customers notice first.

The mobile app is the backbone of the plan

Every failover route in the steps above ends at a person with the business app on a cell phone. Carolina Digital Phone customers use Digital Voice Plus, our app for Apple, Android, Mac, and Windows, which registers to the same extension as the desk phone and shows the caller your business number, not your personal one. The setup guide takes about ten minutes per user. The part most offices skip is the second half: confirming that cellular data is allowed for the app and that notifications are on, so the phone actually rings in a pocket. Do that on a calm day. It is a miserable thing to debug while a customer is holding.

What should you ask a provider before moving to cloud phones?

Ask about the outage before you ask about the features. Specifically, ask how they assess network readiness, what happens to incoming calls during a site outage, and who builds the failover rules. Ask whether mobile and desktop apps are included or cost extra. Ask how voicemail is handled when no one can reach the office, and how emergency locations are managed as staff move around.

Then ask who will answer when the issue is not straightforward. A cloud platform can have redundant data centers and multiple carrier connections, and ours does, yet a problem at your office may still require someone who understands your network, your phones, your call flow, and your priorities. That is where accountable support matters, and it is the reason we keep our engineers in North Carolina instead of in a queue. The reasons businesses choose Carolina Digital Phone come down to this one more than any other.

A few more questions that separate a provider from a reseller:

• Will you show me the platform's redundancy design, or just describe it?
• Will someone from your company look at my firewall and switch before go-live, or is that my problem?
• If my phones cannot register, how fast will you know, and who calls whom?
• Can I see a failover test on a demo system before I sign anything?
• Who is my support contact by name, and where do they sit?

If a provider hesitates on the last two, you have learned what you needed to learn. We have been asked every one of these questions since the company's early days, and we would rather answer them in a sales meeting than during a storm.

Is a cloud phone system still the right choice if internet outages happen?

For almost every business, yes, and the outage question is actually an argument for it. A premise PBX in your closet needs the same internet, the same power, and the same switch to reach the outside world through a SIP trunk, and when the building goes dark, so does every number tied to it. With a cloud system the numbers are already somewhere else. The outage becomes a routing problem, and routing problems are solvable in advance.

The honest trade is this. Copper lines protected you from one specific failure, a building power loss, and did nothing about the other four rows in the table above. Cloud phones ask you to plan for power and connectivity yourself, and in return give you a system that can ring anywhere, that keeps working for your remote staff when the office is down, and that keeps your business number alive no matter what happens to the building. Most of our customers would not go back, and the ones who have been with us the longest are the ones who tested their failover plan once and then stopped thinking about outages altogether.

Carolina Digital Phone plans hosted phone deployments with the local network and the continuity path in mind: number porting, phone configuration, call routing, mobile apps, training, and ongoing support from North Carolina engineers. The goal is not to pretend outages never happen. It is to make sure your callers and your staff have a clear path when they do.

Frequently asked questions about cloud phones and internet