The Internet Connection Conversation

The MSP's Guide to VoIP: Part 6 of 20

There is a conversation that every MSP dreads. You have finished your assessment, you have run the numbers, and you are sitting across from a client who is excited about moving to VoIP. And you have to tell them their internet connection cannot support it.

This is one of the most delicate moments in a VoIP project. Get it right and you build trust, set realistic expectations, and lay the groundwork for a successful deployment. Get it wrong and you sound like you are padding the invoice, pushing unnecessary upgrades, or stalling a project the client is eager to start.

This guide is about navigating that conversation with honesty, clarity, and a focus on business outcomes rather than technical specifications.

Why This Conversation Matters

Most clients do not think about their internet connection in terms of voice quality. They think about it in terms of whether web pages load and whether email arrives. If those things work, the internet is "fine." Telling them it is not fine, specifically for voice, requires you to bridge a knowledge gap without being condescending.

The stakes are real. If you deploy VoIP on an inadequate connection, calls will sound terrible. The client will blame the phone system, blame you, and possibly blame VoIP as a technology. You will spend months troubleshooting problems that were predictable from day one. Understanding why voice traffic is uniquely demanding is the foundation of this entire conversation.

On the other hand, if you insist on a connection upgrade that the client sees as unnecessary or too expensive, you risk losing the project entirely, or worse, losing the client relationship.

The goal is to present the situation accurately, frame the upgrade as a prerequisite rather than an upsell, and give the client options that respect their budget and timeline.

Assessing What They Have

Before you can have the conversation, you need to know exactly what you are working with. This means more than running a speed test.

Connection type matters more than speed. A 100 Mbps cable connection and a 100 Mbps fiber connection are not equivalent for voice. The cable connection shares bandwidth with neighbors, has asymmetric speeds, and may have unpredictable latency spikes during peak hours. The fiber connection offers symmetric speeds, consistent latency, and dedicated capacity. Both say "100 Mbps" on the invoice, but they will deliver very different voice experiences.

For a thorough understanding of how different connection types affect voice, review the detailed breakdowns for fiber, cable, DSL, and fixed wireless. Each has distinct characteristics that matter for real-time communication.

Measure during business hours. Weekend speed tests are meaningless. You need to understand what the connection looks like at 10 AM on a Tuesday when the entire office is working. Jitter, latency, and packet loss during peak usage hours are the numbers that predict voice quality. A browser-based VoIP quality test the client can run from their own desk makes this measurement a two-minute email instead of a site visit.

Account for existing traffic. The client's internet connection is not sitting idle waiting for voice traffic. It is handling email, web browsing, cloud applications, file syncs, video conferencing, and whatever else the business runs. Voice needs its share of capacity on top of everything else.

Check the contract, not just the speed. Many business internet contracts include language about best-effort delivery, contention ratios, or fair-use policies. A connection that advertises 50 Mbps may only guarantee 10 Mbps. That guaranteed floor is what matters for voice.

Framing the Conversation

When you sit down with the client, resist the urge to lead with technical details. Nobody makes budget decisions based on jitter measurements. Instead, frame everything in terms of business outcomes.

Do Not Say This

"Your connection has 47 milliseconds of jitter and 2.3 percent packet loss during peak hours, which exceeds the acceptable threshold for G.711 codec operation."

Say This Instead

"When your team is busy during normal working hours, your current internet connection gets congested. Think of it like a two-lane road during rush hour. Email and web browsing handle that congestion fine because they can wait a fraction of a second and retry. Voice calls cannot wait. When a voice call hits that congestion, you hear choppy audio, words cutting out, and delays that make it hard to have a natural conversation. Your current connection does not have enough reliable capacity to add voice traffic on top of everything your team already uses it for."

The key principles:

• Use analogies the client already understands. Roads, pipes, and lanes are intuitive. Codec specifications are not.
• Connect to their daily experience. If they have ever had a bad video call where audio cut out, reference that. It is the same underlying problem.
• Be specific about the consequence. Not "it might have issues" but "your team will experience choppy calls and missed words during the busiest parts of the day, exactly when call quality matters most."

Connection Types: A Business-Oriented Summary

When discussing options with clients, you do not need to explain the physics of each connection type. You need to explain what each one means for their daily operations.

Fiber is the gold standard for voice. It provides the same speed in both directions, consistent performance regardless of time of day, and handles voice traffic alongside everything else without breaking a sweat. For a deeper look, see the fiber guide. If fiber is available at the client's address, it is almost always the right answer for a business running VoIP.

Cable can work for voice, but it comes with caveats. The upload speed is typically much lower than the download speed, and performance can vary throughout the day because capacity is shared with other businesses and residences in the area. For smaller offices with moderate call volumes, cable can be adequate, especially with proper QoS configuration. For larger deployments or call-heavy businesses, it is a gamble. The cable internet breakdown covers the specifics.

DSL is increasingly marginal for modern VoIP deployments. Speed depends heavily on the physical distance from the provider's equipment, and bandwidth is often too limited for voice alongside other business traffic. It can work for very small offices with minimal concurrent calls, but it is rarely the right foundation for a VoIP project. See the DSL guide for more detail.

Fixed wireless varies enormously by provider and location. Some fixed wireless services deliver fiber-like performance. Others are essentially overloaded cellular towers that struggle with real-time traffic. Weather can also affect performance. This one requires careful, location-specific evaluation. The fixed wireless overview helps you assess what you are actually getting.

For a structured approach to weighing these options, the ISP selection guide walks through the evaluation process. And once you are comparing actual proposals, the guide to reading ISP quotes will help you cut through the marketing language.

Understanding the foundational role your ISP plays in overall VoIP quality is essential context for these conversations. It is not an optional upgrade. It is the platform everything else depends on.

When an Upgrade Is a Prerequisite

There is a difference between "an upgrade would be nice" and "this project cannot succeed without an upgrade." Be honest about which situation you are in.

An upgrade is a prerequisite when:

• Current measured performance (not advertised speeds) cannot support the planned number of concurrent calls plus existing traffic with any reasonable margin.
• The connection type is fundamentally unsuitable. A shared residential cable line for a 30-seat call center, for example, will not work.
• Measured packet loss or jitter during business hours already exceeds acceptable thresholds before adding any voice traffic.
• The connection has no service level agreement and the provider offers no guarantees about performance.

An upgrade is a strong recommendation (but not a hard prerequisite) when:

• Current performance is technically adequate but leaves very little headroom for growth or traffic spikes.
• The connection type is workable but not ideal, and the client's business depends heavily on call quality.
• You can make it work with aggressive QoS and traffic management, but the margin for error is thin.

Be direct about which category the client falls into. If it is a prerequisite, say so clearly: "I would not be doing my job if I deployed this system on your current connection. The calls will sound bad, your team will be frustrated, and we will both spend time troubleshooting a problem we could have prevented."

That is not an upsell. That is professional responsibility.

For businesses where voice quality is mission-critical, dedicated internet access may be worth exploring. It is more expensive, but it comes with guarantees that shared connections cannot match.

The Backup Connection Question

Backup internet connections come up in nearly every VoIP conversation, and the answer is not always the same. Here is how to think about it honestly.

A backup connection is genuinely necessary when:

• The business has a single internet connection and depends on phone service to operate. A medical office, a sales team, a support center. If the phones go down and revenue stops or patients cannot reach you, a backup connection is not optional.
• The primary connection has a history of outages or the provider's uptime record is poor.
• The business has compliance or contractual obligations that require communication availability.

A backup connection is nice to have (but not essential) when:

• The business has multiple ways to communicate during a short outage. Cell phones, email, and a "we will call you back" message can bridge a few hours.
• The primary connection is highly reliable with a strong SLA and a track record to match.
• The business can tolerate occasional brief interruptions without significant financial or operational impact.

Be honest with yourself and the client about which category they fall into. Recommending a $200/month backup circuit to a five-person office that could survive on cell phones for a few hours is hard to justify. Recommending one to a 50-seat sales floor where every hour of downtime costs thousands in lost deals is common sense.

The redundancy and failover guide covers the technical architectures in detail. Use it to design the right solution once the client has decided a backup makes sense for their situation.

When the Budget Does Not Stretch

Here is where the conversation gets hardest. You have assessed the connection, you know it is not adequate, and the client either cannot afford or does not want to pay for an upgrade. What do you do?

First, acknowledge the constraint honestly. Do not pretend the current connection will work if it will not. That path leads to a failed deployment, a frustrated client, and damage to your reputation.

Instead, present options.

Option 1: Delay the Deployment

Sometimes the timing is not right. If the client's lease is up in six months and they are moving to a building with better connectivity, it may make sense to wait. If their ISP contract is renewing soon and better options will be available, a few months of patience can save significant money.

Frame this positively: "Let's get the right foundation in place first so that when we do deploy, it works perfectly from day one."

Option 2: Start With Fewer Seats

If the connection can support some VoIP traffic but not the full deployment, consider a phased approach. Start with the roles that benefit most from VoIP (the reception desk, the sales team, the executives who travel) and keep everyone else on the existing system temporarily.

This lets the client experience the benefits of VoIP, builds internal momentum for the upgrade, and gives them time to budget for the connection improvement needed to expand.

Option 3: Find Compromises in the Connection

Sometimes there are middle-ground options between the current connection and the ideal one. A modest upgrade from a 25/5 Mbps cable plan to a 100/20 Mbps business plan might cost only an extra $50 to $100 per month and provide enough headroom. Adding a lower-cost secondary connection for failover might be more palatable than upgrading the primary.

Explore what is actually available at the client's address. Availability varies enormously by location, and sometimes a better option exists that the client simply has not been offered. Call the ISPs. Check the service maps. Ask about business-class tiers that may not be prominently advertised.

Option 4: Optimize What You Have

If an upgrade is truly impossible in the near term, you can sometimes squeeze acceptable performance from a marginal connection through aggressive network optimization. Dedicated VLANs for voice, strict QoS policies, traffic shaping to limit bandwidth-hungry applications during business hours. These measures can create enough protected capacity for a limited VoIP deployment.

Be clear with the client that this is a compromise, not a solution. Set expectations explicitly: "We can make this work for your core phone needs, but call quality will not be as consistent as it would be on a better connection, and we will not have room to add more lines or features without addressing the underlying connection."

Option 5: Rethink the Scope

Sometimes the answer is to adjust the VoIP project itself. Instead of a full-featured deployment with video conferencing, call recording, and advanced call routing, start with basic phone service that uses less bandwidth. Scale the project to fit the infrastructure rather than the other way around.

Evaluating What Is Available

One of the most valuable things you can do for a client is research what connectivity options actually exist at their address. This is not something most business owners know how to do effectively, and the information is not always easy to find.

Check multiple providers. The client's current ISP may not offer the best option for their address. Fiber availability, in particular, varies block by block in many cities.

Ask about business tiers. Residential and business services at the same address can be dramatically different. Business tiers often include static IPs, SLAs, faster repair times, and more consistent performance, all of which matter for voice.

Consider the timeline. ISPs are constantly expanding their networks. Fiber that was not available six months ago may be available now, or may be coming in the next quarter. A quick call to the provider's business sales team can reveal options that the website does not show.

Look at the physical infrastructure. If the building already has fiber run to it for another tenant, getting service connected may be faster and cheaper than a new installation. If the building is in a business park, there may be options that residential neighborhoods lack.

Get actual quotes. Comparing advertised pricing to actual quotes is essential. The guide to reading ISP quotes will help you decode what providers are actually offering versus what their marketing suggests.

Documenting the Recommendation

Whatever the outcome of the conversation, document it. Put your assessment and recommendation in writing. Not as a CYA exercise, but as a professional practice that protects both you and the client.

Your documentation should include:

• Current connection details. What they have, what it actually delivers during business hours, and where it falls short.
• Your recommendation. What connection would properly support the planned deployment.
• The options you discussed. Including costs, timelines, and trade-offs for each.
• The client's decision. What they chose to do and any limitations they accepted.
• Expected outcomes. What voice quality the client should expect given their chosen path.

If the client decides to proceed on a connection you have flagged as inadequate, that documentation becomes critical. Not as ammunition to say "I told you so," but as a reference point when quality issues arise. It shifts the conversation from "why does this sound terrible?" to "this is the trade-off we discussed, and here's what we can do to improve it."

The Long Game

The internet connection conversation is not a one-time event. Connections change, businesses grow, and what was adequate two years ago may not be adequate today. Build connection assessment into your regular review cadence with clients.

As you add seats, enable new features, or see the client's overall internet usage grow, revisit the capacity question. A proactive "your connection is starting to get tight, let's plan an upgrade before it affects call quality" is a much better conversation than a reactive "your calls sound bad because your connection is overloaded."

This is also where your ongoing monitoring and testing tools become essential. Regular testing gives you data to back up these conversations: not opinion, not intuition, but measured performance over time.

Bringing It Together

The internet connection conversation is fundamentally about trust. You are asking a client to spend money on something they may not fully understand, based on your professional judgment. The way you handle this conversation either builds or erodes the trust that your entire client relationship depends on.

Be honest about what you find. Be clear about the consequences. Frame upgrades as prerequisites when they genuinely are, and be equally honest when they are merely nice to have. Respect the client's budget by presenting options, not ultimatums. And document everything so that both you and the client have a shared understanding of the path forward.

The clients who trust you most are not the ones who never heard bad news from you. They are the ones who heard bad news delivered honestly, with clear options and a genuine focus on their business outcomes.

Before proceeding further in your voice deployment, make sure you understand the regulatory obligations that come with offering voice services. Parts 17 through 20 of this series cover FCC registration, STIR/SHAKEN, and the Robocall Mitigation Database. These are not optional and the consequences of non-compliance are severe.

Next up: Network Preparation: VLANs, QoS, and the Foundation Work