How to Choose a Business Voice Provider: The Questions Nobody Tells You to Ask

March 3, 2026

Every buyer’s guide says the same things. Here are the questions that actually separate good providers from the rest — and what the answers should sound like.

The Guide You’ve Already Read

You’ve googled “how to choose a VoIP provider.” You’ve read the articles. They all say the same things: compare pricing, check uptime SLAs, look at features, read reviews, make sure they have a mobile app. There’s usually a comparison table with checkmarks.

That advice isn’t wrong. It’s just useless. It’s like telling someone buying a car to check that it has wheels and an engine. Every provider has features. Every provider claims 99.99% uptime. Every provider has a mobile app. Comparing those things tells you almost nothing about what it’s actually like to be their customer.

Here are the questions that actually matter — the ones nobody else tells you to ask. We’re obviously biased (we sell this stuff), but we think these questions are worth asking any provider you’re evaluating, including us.

“Did You Build Your Platform, or Are You Reselling Someone Else’s?”

This is the question the industry really doesn’t want you to ask.

There’s an entire ecosystem of white-label VoIP reselling. Companies buy platform access from an upstream provider, slap their own brand on it, and sell it as “their” phone system. The marketing material looks great. The website has a custom logo. But under the hood, it’s someone else’s technology, someone else’s servers, and someone else’s engineering team.

Why does this matter to you? Because when something goes wrong — and something will eventually go wrong — a reseller files a support ticket with their upstream provider and waits. A company that built their own platform walks down the hall and talks to the engineer. The difference in response time, flexibility, and depth of understanding is significant.

It also matters for customization. Need a call flow that doesn’t fit the standard template? A platform owner can build it. A reseller can only offer what their upstream platform supports. Need a pricing structure that doesn’t fit the standard tiers? Same story.

Ask the question directly: “Did your company build the technology I’ll be using?” If the answer involves words like “powered by” or “partnered with,” you’re probably talking to a reseller. That’s not automatically a dealbreaker — some resellers provide excellent service. But you deserve to know.

“Where Does My Voice Traffic Actually Go?”

Here’s a related question that goes a level deeper.

A lot of providers — including some that built their own software — run their infrastructure on commodity cloud platforms like AWS, Azure, or Google Cloud. These are phenomenal platforms for web applications. They were not designed for real-time voice.

Voice is UDP traffic. It’s latency-sensitive, jitter-sensitive, and doesn’t get a second chance. A voice packet that arrives late is useless — you can’t replay it. Commodity cloud platforms optimize for throughput and reliability of data, not for the precise timing that voice demands. You can run VoIP on AWS. It’ll work most of the time. But “most of the time” isn’t what you want from your phone system.

Ask your provider: “Can you give me an IP address of your platform so I can see where it’s hosted?” Then look it up. If it resolves to a major cloud provider, you know what you’re dealing with. If it resolves to infrastructure the provider owns or leases specifically for voice, that tells you something different.

This isn’t about being anti-cloud. It’s about knowing whether your voice traffic is riding on infrastructure that was designed for it. We’ve written more about this in our call quality guide.

“What Happens When My Usage Doesn’t Fit Per-Seat Pricing?”

Every buyer’s guide tells you to compare per-seat prices across providers. $20/seat here, $25/seat there, $30/seat at the fancy place. Pick the cheapest one that has the features you need. Simple.

Except per-seat pricing assumes every person in your organization uses the phone the same way. They don’t.

Think about your business. You probably have one or two people who are on the phone constantly — the receptionist, the dispatcher, the intake coordinator. You have people who take a moderate number of calls. And you have people who barely touch the phone — the bookkeeper, the warehouse guy, the developer who communicates exclusively through Slack.

Per-seat pricing charges all of them the same amount. A business with 20 employees where only 5 are heavy phone users is paying for 20 identical seats. That math gets worse in industries like construction (12 field techs who take 3 calls a day), healthcare (exam room phones that ring twice a week), or schools (hundreds of classroom phones that exist for safety).

Ask your provider: “Can you price this based on how we actually use phones, not just how many people we have?” If the answer is “no, it’s $X per seat, pick a plan” — that’s their answer, and you can decide if the simplicity is worth the cost. But at least you asked.

“Who Configures the System — Us or You?”

Every provider talks about how “easy” their self-service portal is. And honestly, most portals are pretty good these days. You can probably figure out how to add an extension or change a voicemail greeting.

But here’s what the portal doesn’t handle well: the initial setup. Designing your call flow. Building an auto-attendant that routes callers intelligently. Setting up ring groups, after-hours routing, holiday schedules, failover rules. Configuring phones with the right settings, the right line appearances, the right speed dials. Testing everything before you go live.

This is the part that takes actual expertise, and it’s the part that most providers leave to you. They’ll give you a portal and a knowledge base and maybe some onboarding webinars. But at the end of the day, you or someone on your team is becoming a part-time telecom administrator.

Ask: “Will you configure everything for us? Will you build the call flows, program the phones, and ship them ready to plug in?” And then: “What happens when we need a change six months from now? Do we submit a ticket, or can we call someone who knows our account?”

The difference between “here’s a portal, good luck” and “tell us how your business works and we’ll build it” is enormous in practice. It’s the difference between buying furniture from IKEA and buying furniture that arrives assembled.

“What Happens During the Number Porting Transition?”

Every provider says “we support number porting.” It’s a checkbox on the feature list. What they don’t tell you is what the transition actually looks like.

Porting is the process of moving your phone numbers from your old provider to your new one. It’s straightforward in theory: fill out some paperwork, wait a few days, the numbers move over. In practice, it’s the most anxiety-inducing part of switching phone systems, because your phone numbers are your business identity. They’re on your website, your business cards, your Google listing, your contracts. A botched port — even a few hours of downtime — means calls from your customers go nowhere.

Ask your provider specific questions:

“How many numbers have you ported?” There’s a difference between a provider who has ported thousands of numbers and one who has ported millions. Experience matters because every carrier has different quirks, different timelines, and different ways to reject a porting request.
“What happens during the cutover? Is there a gap?” A good provider keeps your old service running until the exact moment the port completes, so there’s no window where calls drop into the void.
“Who handles the paperwork and follows up with the losing carrier?” You should not be the one calling AT&T to ask why your port was rejected because someone put “Street” instead of “St.” on the LOA.
“What’s your success rate, and what do you do when a port gets rejected?” Rejections happen. What matters is how fast your provider identifies the problem, fixes the paperwork, and resubmits.

We have strong opinions about porting because we’ve done a lot of it. But regardless of who you choose, ask these questions. The answers will tell you a lot about how much operational experience the provider actually has.

“What Does Support Actually Look Like?”

“24/7 support” is on every provider’s website. It tells you nothing. Here’s what to ask instead:

“If I call support, am I talking to someone who knows my account?” At a large provider, you’re talking to a tier-1 agent who’s looking at your account for the first time. At a smaller provider, you might be talking to someone who configured your system and knows your auto-attendant by heart. Both models work, but they’re very different experiences.
“Can I call a human, or is it chatbot-first?” A lot of providers have moved to AI chatbots and ticket systems as the front door. That’s fine for password resets. It’s not fine when your phones are down and you need someone to fix it now.
“What’s your actual response time for urgent issues?” Not the SLA number on the website. The real one. Ask for examples. Ask what happened the last time a customer had an outage.

“What Am I Actually Paying For?”

The advertised price is rarely the full price. Per-seat pricing often excludes:

Regulatory and compliance fees ($2-5/seat/month)
E911 fees ($1-2/seat/month)
Number porting fees (per number)
International calling (per minute, often expensive)
Call recording storage (sometimes extra on lower tiers)
Additional phone numbers beyond the included count
Hardware costs (phones themselves, shipping)

Ask for a complete quote — not just the per-seat rate, but the total monthly bill for your specific setup including all fees. Then compare apples to apples. A provider that quotes $20/seat but adds $7 in fees is really charging $27/seat. A provider that quotes $25/seat all-in is cheaper.

Better yet, find a provider who doesn’t moose-take complexity for transparency. A quote should be a number, not a math problem.

The Meta-Question: How Does This Conversation Feel?

This one isn’t really a question you ask. It’s something you notice.

When you’re talking to a provider during the sales process, pay attention to how the conversation goes:

Are they asking about your business, or pitching their product? A provider who starts by understanding how you use phones will build you a better system than one who starts by listing features.
Are they honest about what they can’t do? Every provider has limitations. The ones who acknowledge them are the ones you can trust about everything else.
Do they explain things clearly, or hide behind jargon? If you can’t understand what they’re selling you, you won’t understand what went wrong when something breaks. Our glossary exists because we think telecom jargon is a problem, not a feature.
Are they trying to sell you more than you need? If you’re a 10-person office and they’re pitching you a contact center platform with AI sentiment analysis, that’s a sign they’re selling a product, not solving your problem.

The sales process is a preview of the relationship. If they’re responsive, clear, and honest before you’re a customer, they’ll probably be the same after. If they’re slow, vague, and pushy before you sign… well, it doesn’t get better.

Want to see what these questions look like with real answers? Drop us a line. We’ll answer every question on this list — honestly, including the ones where the honest answer isn’t “yes.” No pressure, no 47-slide deck. And if we’re not the right fit, we’ll tell you that too.