VoIP phone service is how most businesses make and receive calls today — and for good reason. Compared to traditional landline service, it costs less, scales faster, and comes with features that a PBX hardware install could never match without significant additional investment. But not all VoIP services are built the same, and the decision involves more than picking the lowest per-user price.
This guide explains what VoIP phone service is, how it actually works, what the cost structure looks like in full (not just the advertised rate), what to look for in a provider, and how to avoid the most common mistakes businesses make when switching.
What is VoIP phone service? VoIP (Voice over Internet Protocol) phone service routes voice calls over the internet rather than traditional copper telephone lines. Instead of a dedicated circuit between caller and receiver, voice audio is digitized, compressed into data packets, and transmitted over IP networks — the same infrastructure that carries web traffic and email. For a business, this means phone numbers, extensions, voicemail, IVR menus, and call recording are managed through a cloud platform rather than on-site hardware, and agents can make and receive calls from any internet-connected device. For more on how the full system fits together, see our guide to what a business phone system is.
How VoIP phone service works
When a caller dials your business number, the call travels over the public switched telephone network (PSTN) until it reaches your VoIP provider's network. At that point, the provider's Session Border Controller (SBC) — the network gateway at the VoIP edge — accepts the inbound SIP session, applies any configured security policies, and hands it off to the cloud routing engine.
The routing engine checks which number was dialed, what time it is, what routing rules apply, and where to send the call: a specific extension, a ring group, a call queue, or an auto attendant IVR menu. Once the destination is determined, the call is delivered to the receiving device — a desktop softphone app, a mobile app, a browser tab using WebRTC, or an IP desk phone. The audio itself is transmitted as Real-time Transport Protocol (RTP) packets, encrypted with SRTP for security.
The key technical requirements on your side are straightforward: a stable internet connection (100–320 Kbps per concurrent call depending on codec), a router configured to prioritize voice traffic via Quality of Service (QoS) settings, and devices running the provider's app or a compatible SIP client. No dedicated telephone lines. No on-site PBX hardware required.
For more on the infrastructure behind hosted cloud calling, see our cloud phone system guide.
VoIP vs. traditional landline: what actually changes
| Dimension | VoIP phone service | Traditional landline |
|---|---|---|
| Infrastructure | Internet connection; provider's cloud platform | Physical copper lines; on-site hardware |
| Cost per user | $15–$40/user/month (cloud plan) | $50–$80+/line/month (POTS/PRI) |
| Scaling | Add users in the admin portal in minutes | Requires new line orders; weeks to provision |
| Mobile & remote | Native — any device, any location | Tied to physical location |
| Features | IVR, recording, SMS, analytics included | Basic call handling; features require PBX hardware |
| Reliability dependency | Internet connection quality | Physical line integrity |
| Number porting | Fully portable — keep your existing numbers | Portable under LNP rules |
Types of business VoIP phone service
"VoIP phone service" covers several distinct products with different use cases. Understanding which type you are actually buying matters before you compare providers.
Hosted VoIP / cloud PBX. A fully managed phone system delivered as a subscription. The provider hosts the routing software (PBX), manages the carrier network, and provides a web-based admin portal, desktop apps, and mobile apps. You configure extensions, call flows, and features through a browser — no on-site hardware required. This is what most businesses mean when they say they are switching to VoIP. See our cloud phone system guide for a detailed breakdown of how this model works.
SIP trunking. A different product for a different situation. SIP trunking replaces your physical telephone lines — the PSTN connection between your existing on-site PBX hardware and the outside world — with an internet-based equivalent. If you have a recent PBX hardware investment you do not want to abandon, SIP trunking modernizes the line costs without replacing the routing system. It is not a substitute for a hosted VoIP system; it is a complement to an existing one.
Virtual phone service. Entry-level VoIP services that add a business phone number and basic call routing to existing devices. Designed for solo operators and micro-businesses that need a professional number without a full hosted PBX. Typically limited to basic call forwarding, voicemail, and a simple auto-attendant — not suitable for teams that need call queues, extensions, and analytics.
UCaaS (Unified Communications as a Service). An expanded version of hosted VoIP that bundles voice calling with video conferencing, team messaging, and file sharing in a single platform. UCaaS pricing is higher than voice-only VoIP service ($25–$50/user vs. $15–$25/user for voice-only) but consolidates multiple communication tools. The right choice depends on whether your business currently pays for separate video and messaging tools that would be replaced.
What VoIP phone service costs — the full picture
The advertised per-user price is a floor, not a ceiling. Here is what the total monthly cost actually includes.
Base plan per user: $15–$40/user/month. Entry-tier plans from major providers (RingCentral, Nextiva, Dialpad, Vonage) sit in this range for basic voice, voicemail, and standard apps. Features like advanced IVR, call recording with extended retention, analytics dashboards, and SMS may require a higher tier.
Taxes and telecom surcharges: add 15–25%. Federal and state telecommunications taxes, the Universal Service Fund (USF) surcharge, and local taxes apply on top of the base plan. A $25/user plan for a 10-user company advertises as $250/month; the actual invoice runs $290–$315 before add-ons.
E911 fees: $0.20–$2.00/line/month. Emergency services fees are non-negotiable and billed separately by most providers. Small dollar amount per line but worth including in budget comparisons, especially for multi-location businesses with many lines.
Number porting: $0–$40 per number. Some providers include porting at no charge; others bill per number. For a business with 10 existing numbers, this is a one-time switching cost of $0–$400 depending on provider.
International calling: variable per minute. "Unlimited calling" plans apply to US and Canada calls. International calls are billed per minute — rates vary by destination and provider. If your business calls internationally at meaningful volume, model per-minute international rates at your actual usage before comparing base plans.
Add-ons: $5–$25/user/month each. AI transcription, extended call recording retention, advanced analytics, and CRM integrations are frequently positioned as included features in marketing but licensed as paid add-ons in practice. Identify every feature you require before requesting quotes, then ask providers specifically whether each feature is included at your tier or metered separately.
When comparing providers, request a fully-loaded quote: base plan + taxes + fees + every add-on you need. Then compare those numbers. Comparing advertised per-seat prices is comparing marketing, not cost.
Key features to evaluate in a business VoIP service
Not all VoIP services include the same capabilities. Before comparing pricing across providers, confirm that each one includes the following at the plan tier you are evaluating.
Auto attendant (IVR). An automated system that answers calls and routes callers to the right destination without a receptionist. At minimum: multi-level menus, custom recordings, time-based routing (business hours vs. after-hours). For a deeper look at what IVR does and when AI replaces it, see our IVR system guide.
Call queues. When all team members are busy, callers should hear queue position and estimated wait time rather than an immediate busy signal. Queue behavior — max depth, overflow routing, music on hold, callback option — should be configurable by admins without contacting support.
Call recording. Essential for compliance in many industries and for training in all of them. Confirm: where recordings are stored, how long they are retained on your plan, whether pause-on-demand for PCI DSS is supported, and whether recording is on by default or per-user.
Business SMS on your VoIP number. Two-way text messaging on the same number used for voice calls. Confirm that A2P 10DLC registration is included — required for business texting since 2023. Confirm no surprise per-message fees. For more on how this works, see our guide on VoIP text messaging for business.
Desktop and mobile apps. Your team needs to make and receive calls from laptops and smartphones using their business number. Verify full feature parity on mobile — not just basic calling. Verify the app supports the operating systems your team actually uses.
Number management self-service. Adding numbers, managing extensions, and initiating number ports without opening a support ticket. Self-service number management indicates platform maturity and will save significant time when your team grows.
Analytics and reporting. Call volume by time of day, missed call rate, queue wait times, average handle time. These tell you whether your routing is working. If analytics require a paid upgrade, factor that into the comparison.
Integrations. Pre-built connectors for your CRM (Salesforce, HubSpot, Zoho), helpdesk (Zendesk, Freshdesk), and any other business application your team uses during calls. Confirm whether the integration is native (built by the VoIP provider) or a third-party connector — native integrations are more reliable and easier to troubleshoot.
VoIP call quality: what affects it and how to fix issues
VoIP call quality depends on your network, not just the provider. Understanding the difference between a provider problem and a local network problem saves significant time when issues arise.
Jitter. Variation in the delay between packet arrivals. Jitter above 30ms causes choppy or robotic audio. Fix: QoS prioritization on your router to give voice packets priority over other traffic.
Latency. Total round-trip delay in audio transmission. One-way latency above 150ms causes noticeable delay and conversational overlap. Fix: use a provider with data centers geographically close to your locations; avoid routing voice traffic over VPNs unnecessarily.
Packet loss. Percentage of voice data packets that fail to arrive. Above 1–2%, audio gaps appear. Fix: a dedicated, QoS-prioritized internet connection for voice; wired ethernet connections rather than Wi-Fi for desk-based agents.
Bandwidth. Budget 100–320 Kbps per concurrent call (G.711 codec at the high end; G.729 compressed codec at the low end). For a 10-person team where all 10 might be on calls simultaneously, plan for at least 3.2 Mbps of bandwidth dedicated to voice.
Most VoIP call quality complaints that reach provider support trace back to the customer's network — jitter, latency, or missing QoS — rather than the provider's infrastructure. Run a pre-deployment network quality test before switching.
Reliability: what the SLA actually means
Every VoIP provider advertises high uptime. The numbers look similar but carry different risk profiles.
99.9% vs. 99.99% uptime. 99.9% allows 8.7 hours of unplanned downtime per year. 99.99% allows 52 minutes. For a business where the phone is a revenue channel — sales, inbound orders, customer support — the difference between these two targets is significant. Look for 99.99% SLA commitments backed by geographic redundancy (multiple data centers with automatic failover), not a single-facility guarantee.
SLA remedy terms. Read the SLA document itself, not the marketing copy. Service credits that require filing a claim within a narrow window, getting provider approval, and are capped at one month's fee are very different from automatic credits applied when the threshold is missed. The credit structure tells you how seriously a provider takes its uptime commitments.
Your internet as the weak link. Even a provider with 99.99% infrastructure uptime cannot protect you from your ISP going down. Configure automatic call forwarding to mobile numbers as an ISP failover — most hosted VoIP platforms support this but require setup. For more on how to build resilience into a VoIP deployment, see our guide on VoIP failover and redundancy.
Security considerations
VoIP calls carry sensitive business conversations, and the admin portal controls your entire phone system. Security due diligence is not optional.
Encryption. TLS for SIP signaling (call setup and teardown) and SRTP for media (the audio packets) should be enabled by default on any provider you consider. Ask specifically whether SRTP is on by default or requires activation — some providers treat encryption as an optional configuration.
Multi-factor authentication. Admin portal access should require MFA. Unauthorized access to a VoIP admin portal enables toll fraud — international calls to premium-rate numbers that can generate thousands of dollars in charges before detection.
Toll fraud detection. Ask what automated detection the provider includes for anomalous call volume — after-hours international calling patterns, sudden spikes in per-minute usage — and how quickly they respond when fraud is detected.
SOC 2 Type II. A six-month or longer independent audit of the provider's security controls. For any regulated industry — healthcare, finance, legal — this is a minimum requirement. Request a current SOC 2 Type II report.
HIPAA BAA. Healthcare businesses must confirm that the VoIP provider will sign a Business Associate Agreement. A provider that declines is not compliant for healthcare use.
Choosing a VoIP phone service provider: what to ask
- Uptime SLA: Is the commitment 99.99% or better? What geographic redundancy backs it? What remedies apply automatically when the target is missed?
- Fully-loaded pricing: What is the total monthly cost including taxes, E911 fees, all required features, and add-ons — not just the base plan?
- Feature tier clarity: Which features — recording, analytics, IVR depth, SMS, AI — are included in the plan I am evaluating vs. metered or paid add-ons?
- Number porting: Is porting included at no charge? What is the realistic timeline for my current carrier specifically?
- Encryption: Is SRTP for media and TLS for signaling enabled by default, or do I need to activate them?
- Integration quality: Are integrations with my CRM and helpdesk native or third-party connectors? What data syncs? Who maintains the integration when either platform updates?
- Support availability: What are actual support hours? What is the response time for a critical outage (all calls down)?
- Contract terms: What is the minimum commitment and early termination fee? Is month-to-month available, and at what premium?
- Pilot availability: Will the provider allow a trial on live traffic before a full contract? Resistance here is a signal.
Making the switch: number porting and go-live
Your existing business numbers are a business asset — they appear on your website, marketing materials, and in your customers' contacts. Keeping them when switching to VoIP is guaranteed under US law (Local Number Portability, established by the FCC). Carriers cannot refuse a valid port request.
What you need to port. Your new VoIP provider will ask for: the phone numbers to port, your account number with the current carrier, the billing name and service address on the account, and sometimes a PIN. You will sign a Letter of Authorization (LOA). The information on the LOA must exactly match your current carrier's records — mismatches are the primary cause of port rejections and delays. For a full walkthrough of the porting process, see our number porting guide.
Timeline. After your current carrier accepts the port request, a Firm Order Commitment (FOC) date is issued — typically 3–10 business days out for US local numbers. Start the port 3–4 weeks before your planned go-live. Do not cancel existing service until the FOC completes.
Go-live planning. Run both systems in parallel until porting is confirmed complete. Configure call routing and IVR menus before the port date, so everything is working before the numbers cut over. Test with internal calls first, then external calls before announcing the switch.
