Blog / Cloud Business Phone Systems

Questions to Ask a VoIP Provider: 12 Demo Tests and Red Flags

A 12-question checklist for VoIP sales calls and demos. Each question includes a live test, a good answer, a red-flag answer, plus the contract clauses and uptime SLA terms to check before you sign.

The best questions to ask a VoIP provider cover uptime and how SLA credits are paid, the all-in monthly cost, call quality, failover, call routing, CRM sync, texting compliance, 911 handling, security, number porting and post-launch support. Asking these questions is only a third of the job. This checklist pairs each of the 12 questions with a live test to run during the demo, the answer you want to hear, and the red-flag answer that should make you walk. It ends with the contract clauses to negotiate and a scorecard for comparing two to four vendors.

Key takeaways

  • A 99.9% VoIP uptime SLA allows about 8.8 hours of downtime a year; 99.999% allows about 5 minutes.
  • FCC rules require simple number ports, including VoIP, to finish within one business day, so a weeks-long port-out quote is a red flag.
  • Since February 2025, US carriers block unregistered 10DLC business texts, so VoIP texting requires registration through The Campaign Registry.
  • Kari's Law requires business phone systems to allow direct 911 dialing with no prefix and to notify an on-site location of 911 calls.
  • The riskiest VoIP contract terms are auto-renewal windows, early termination fees, ticket-based SLA credits and mid-term price increases.

How should you use this VoIP vendor checklist?

Use this VoIP vendor checklist in three passes: ask the question on the sales call, test the answer live during the demo, then confirm it in the contract. Most question lists stop at asking, and a sales rep's verbal answer is worth very little once you have signed a 24-month agreement.

The three-part method: ask, test live, check the contract

For every question below, write down the rep's answer word for word. Then run the live test while the demo account is open in front of you. Finally, find the clause in the order form or terms of service that backs up the answer. If the answer is not in writing, treat it as a no.

Who should be on the demo call

  • Owner or finance lead: total cost, contract terms, termination rights.
  • Sales lead: outbound caller ID, dialer speed, CRM logging.
  • Support lead: queues, phone menus, after-hours routing, voicemail.
  • IT or ops (even part-time): network requirements, security, 911 setup, porting.

If you have no IT person, the day-one plan in our guide to a phone system for small business with no IT staff covers what that seat needs to check.

What should you define before the demo?

Before a VoIP demo, define your call flows, your required integrations and texting needs, and a per-user budget that includes add-ons. A one-page sketch of how calls move through your business turns a scripted sales demo into a real test, because you can ask the provider to build your flow live.

Map your call flows

Sketch your main line, any phone menu options ("press 1 for sales"), which teams ring for each option, the order they ring in, and what happens after hours. Note your peak number of simultaneous calls. That figure drives bandwidth needs and licensing.

List integrations and texting needs

Write down your CRM, helpdesk and calendar tools, and what you need logged: call activity, recordings, texts, voicemail transcripts. If you plan to text customers, note the use case (appointment reminders, missed-call follow-ups, sales outreach), because texting compliance depends on it.

Set a budget per user, including add-ons

Base seat prices rarely tell the whole story. Set a ceiling per user per month that includes recording, AI features, texting, extra numbers and toll-free minutes. Our broader guide on how to choose a business phone system walks through typical cost categories.

What are the 12 questions to ask a VoIP provider?

The 12 questions to ask a VoIP provider cover reliability, cost, call quality, failover, routing, CRM sync, texting, caller reputation, 911, security, porting and support. Each one below includes why it matters, a live test to run during the demo, a good answer, and a red-flag answer to watch for.

1. What uptime do you guarantee, and how are SLA credits paid?

Why it matters: Uptime percentages hide large differences. By simple arithmetic, 99.9% allows about 8.8 hours of downtime a year, while 99.999% allows about 5 minutes and 15 seconds.

Live test: Ask the rep to open the public status page and show the last 12 months of incidents.

Good answer: A specific percentage in the contract, credits applied automatically, and a status page with dated incident reports.

Red-flag answer: "We're basically never down" with no written SLA, or credits that require a support ticket within 48 hours of the outage.

2. What is the all-in monthly cost per user, including taxes, surcharges and add-ons?

Why it matters: VoIP invoices often include regulatory recovery fees, E911 fees, state and local taxes, and paid add-ons that can push the real cost well above the advertised seat price.

Live test: Ask for a sample invoice for your exact seat count and feature list, with every line item shown.

Good answer: A written quote that lists taxes and surcharges separately and states which features are included in the base seat.

Red-flag answer: "Pricing depends" with no sample invoice, or recording and integrations priced only on the next tier up.

3. How do you handle call quality: codecs, data centers and minimum bandwidth?

Why it matters: A codec is the method a phone system uses to compress voice into data, and it determines both audio quality and bandwidth use. HD codecs such as Opus or G.722 sound clearer, and nearby data centers reduce delay.

Live test: Call the demo number from a cell phone on a weak signal and from a laptop on hotel-grade Wi-Fi. Listen for echo, clipping and delay.

Good answer: Named codecs, US data center regions, a per-call bandwidth figure, and a network readiness test you can run before go-live.

Red-flag answer: "Any internet connection works" with no bandwidth guidance.

4. What happens to inbound calls if our internet or your primary site goes down?

Why it matters: Failover is the automatic rerouting of calls when part of the system fails. Without it, an office internet outage means customers hear a dead line.

Live test: During a live call on a desk phone or desktop app, pull the network cable or turn off Wi-Fi. Then call the main number again and confirm it rings through to mobile apps or a forwarding number.

Good answer: Geo-redundant data centers, automatic forwarding rules you set yourself, and mobile apps that keep receiving calls when the office is offline.

Red-flag answer: "Calls go to voicemail" as the only failover option.

5. How do queues, phone menus and voicemail routing work, and who can change them?

Why it matters: An IVR (interactive voice response) is the automated phone menu that routes callers by keypress or speech. Support teams change hours, menus and queues often, so editing them should not require a support ticket.

Live test: Ring the demo queue with two agents logged out. See where the call lands, and time how long it takes to reach voicemail. Then ask the rep to change the after-hours greeting while you watch.

Good answer: A visual editor any admin can use, overflow rules for empty queues, and changes that take effect in minutes. Tools built for this, such as Voicalyst's IVR phone menus and call routing, let admins edit flows in the browser.

Red-flag answer: "Our team configures that for you" with a multi-day turnaround on every change.

6. How does your CRM integration log calls, recordings and texts?

Why it matters: A CRM integration that logs inconsistently is worse than none, because reps stop trusting the data. Sales managers need activity counts, and support leads need recordings attached to the right contact.

Live test: Place a call during the demo and watch the activity appear in your CRM. Check that the recording, duration, outcome and any notes attach to the correct contact record, and how long the sync takes.

Good answer: Near-real-time sync, recordings linked on the contact timeline, and clear handling of unknown numbers. A HubSpot calling integration should show the call on the contact without manual logging.

Red-flag answer: "It syncs overnight" or "logging is available through a third-party connector."

7. Is business texting 10DLC-registered, and who handles registration?

Why it matters: 10DLC is the US system for business texting from standard 10-digit local numbers. Since February 2025, carriers block unregistered 10DLC traffic instead of only slowing it, so brand and campaign registration through The Campaign Registry is mandatory before you send.

Live test: Ask the rep to show the registration screen in the admin portal and the typical approval timeline.

Good answer: Guided registration inside the product, help with rejections, and clear opt-out handling. Our 10DLC registration guide explains what approval requires.

Red-flag answer: "Just text from any number, it's fine."

8. How do you protect outbound caller reputation?

Why it matters: STIR/SHAKEN is the caller ID authentication framework US carriers use to verify that a call really comes from the number shown. Weak attestation and high call volume make "Spam Likely" labels more likely, which hurts sales teams running outbound campaigns.

Live test: Ask what attestation level your numbers receive and how the provider handles a number flagged as spam. If you run outbound, have the rep run a short session in the power dialer and count calls per hour.

Good answer: Full attestation on numbers you own, number reputation monitoring, and a documented remediation process.

Red-flag answer: "Just buy new numbers when they get flagged."

9. How do you handle 911 for remote and hybrid staff?

Why it matters: The FCC's Kari's Law order (FCC 19-76) requires multi-line phone systems to allow direct 911 dialing without a prefix and to notify a central on-site location when someone calls 911. The FCC's dispatchable location rules under RAY BAUM's Act, effective January 6, 2020, extend location obligations to interconnected VoIP.

Live test: Ask how a remote agent updates their 911 address in the desktop or mobile app, and who receives the 911 notification.

Good answer: User-editable emergency addresses, prompts when location changes, and configurable notification by email or SMS.

Red-flag answer: "911 uses the billing address on file" for everyone.

Why it matters: Toll fraud, where attackers use a compromised account to place expensive international calls, can produce large bills fast. Some US states require all-party consent to record a call, so recording disclosures matter for any team that records.

Live test: In the admin portal, find the international calling restrictions, two-factor login settings and the automatic recording announcement. For AI call summaries, ask how long transcripts are kept and whether call data trains the vendor's models.

Good answer: TLS and SRTP encryption, SSO or two-factor login, role-based admin permissions, spend alerts, configurable retention and a written commitment on model training.

Red-flag answer: "Recording consent is your problem" or no clear answer on AI data use.

11. How does number porting work in and out, and what does it cost?

Why it matters: Under 47 CFR 52.35, simple ports, including VoIP, must be completed within one business day, and non-simple ports within four business days. Carriers are limited to a standard set of 14 data fields for simple port requests.

Live test: Ask for the port-out process in writing, and ask what happens to recordings, voicemails and call logs when you leave.

Good answer: No port-out fees, a dedicated porting contact, and self-serve data export. See our guide to porting a business phone number to VoIP for the steps.

Red-flag answer: Port-out fees, "30 to 45 days" timelines for a simple port, or numbers held until the contract term ends.

12. What does support look like after go-live, and what is the onboarding plan?

Why it matters: Phone outages happen during business hours, and a support queue that answers in two days does not help a team with customers on hold.

Live test: Call or chat with the provider's support line during the trial and time the response.

Good answer: Named support hours in US time zones, phone and chat channels, an onboarding plan with dates, and a dedicated contact above a stated seat count.

Red-flag answer: "Email support only" for core plans, or onboarding that consists of a help-center link.

Which red-flag answers should end the conversation?

The red-flag answers that should end a VoIP vendor conversation are vague uptime claims, pricing with no sample invoice, slow or paid porting-out, and no process for 10DLC or E911. Each one signals either hidden cost or real compliance risk, and none gets better after you sign.

QuestionRed flagAsk instead
Uptime"We're basically never down""Where is the SLA written? Are credits automatic?"
Cost"Pricing depends""Send a 15-seat sample invoice with taxes and add-ons."
Porting out"30 to 45 days, plus a fee""Put your port-out process and fees in writing."
Texting"Text from any number""How do you handle 10DLC registration?"
911"We use your billing address""How do remote users update their 911 location?"
Failover"Calls go to voicemail""Can calls auto-forward to mobile if the office is offline?"
AI features"We don't share that""Does call data train models? How long is it kept?"

Which VoIP contract terms should you negotiate before signing?

The VoIP contract terms worth negotiating are term length and auto-renewal notice, the early termination fee formula, how SLA credits are claimed, mid-term price increase rights, number ownership and data export on exit, and minimum seat commitments. This section describes what to look for in plain English; it is not legal advice, so have an attorney review any multi-year agreement.

Term length and auto-renewal notice windows

The common trap is a 30 to 90 day non-renewal notice window that silently triggers another 12 to 24 month term. Look for wording like "renews for successive periods equal to the initial term unless either party gives notice." Ask to shorten renewals to month-to-month after the initial term.

Early termination fee formula and caps

An early termination fee (ETF) is the penalty for ending a contract before the term is up. Watch for "100% of remaining monthly fees." Negotiate a cap, such as two or three months of fees, and a right to terminate without penalty for repeated SLA breaches.

SLA credits: automatic vs ticket-based

Check whether credits apply automatically or only if you file a claim within a deadline. Look for exclusions such as "scheduled and unscheduled maintenance," which can cover most real outages.

Price increase rights mid-term

Many terms let the provider "modify fees upon notice." Ask for a price lock for the initial term, or a cap on annual increases.

Number ownership and data export on exit

The contract should state that you own your numbers and can port them at any time, including when an invoice is in dispute. Add a clause giving you 30 or more days after termination to export recordings, voicemails and logs.

Minimum seat commitments and downsizing rights

If headcount is seasonal, negotiate the right to reduce seats by a set percentage each year without penalty.

What does a VoIP uptime SLA actually guarantee?

A VoIP uptime SLA guarantees a percentage of time the provider's covered services will be available, plus the credit you receive when it falls short. The SLA does not guarantee your calls will work: it usually covers only "core services," excludes maintenance windows, and pays credits rather than compensating you for lost business.

99.9% vs 99.99% vs 99.999% in real downtime

Uptime SLADowntime per monthDowntime per year
99.9%about 43.8 minutesabout 8.8 hours
99.99%about 4.4 minutesabout 52.6 minutes
99.999%about 26 secondsabout 5.3 minutes

What "core services" usually excludes

Core services often mean only the ability to place and receive calls. Texting, integrations, admin portals, recording and AI features may sit outside the SLA. Outages caused by your internet, carrier issues and maintenance are typically excluded too. Ask for a written list of what is covered.

How to verify a provider's track record

Ask for the last 6 to 12 months of incident history from the status page. Look at how often incidents occur, how long they last, and whether the provider publishes post-incident reports. A provider promising 99.999% with monthly hour-long incidents is not meeting its own number.

How do you score and compare VoIP vendors after the demos?

Score VoIP vendors with a weighted scorecard filled out right after each demo, then run a 14 to 30 day pilot with real calls on the top choice. Weighting keeps a slick interface from outranking a weak SLA, and the pilot tests what demos cannot: your network, your callers and your CRM data.

A weighted scorecard template

Rate each vendor from 1 to 5 on each category, multiply by the weight, and add the totals.

CategoryWeightWhat earns a 5
Reliability and failover25%Written SLA, automatic credits, failover passed live test
Total cost20%Sample invoice within budget, no surprise add-ons
Call flows and queues15%Built your flow live, admin can edit without a ticket
CRM integration15%Call and recording logged correctly during demo
Compliance (911, 10DLC, recording)15%Clear process for each, shown in the product
Support and onboarding10%Fast trial response, dated onboarding plan

Adjust weights to fit your team. Outbound sales teams may weight dialer throughput and caller reputation higher, while support teams may weight queues higher. If you are still building a shortlist, our overview of VoIP service providers covers what separates them.

Running a 14 to 30 day pilot with real calls

Put one real team on the pilot, not just test calls. Set success criteria before you start:

  • Missed-call rate: compare against your current system for the same period.
  • CRM log accuracy: spot-check 20 calls for correct contact, duration and recording.
  • Call quality complaints: track any echo, drops or one-way audio reports.
  • Admin time: note how long routine changes such as hours or greetings take.
  • Support responsiveness: log time to first response on any ticket.

If you want to see browser-based queues, a power dialer and HubSpot sync tested against this checklist, Voicalyst offers demos built around your own call flows.

Frequently Asked Questions

Can I keep my number if I switch VoIP providers?

Yes. FCC number portability rules let you move your business number to a new VoIP provider, and simple ports must be completed within one business day. Complex ports, such as many numbers or multiple locations, have a four-business-day interval. Do not cancel your old service until the port completes, or you risk losing the number.

How much bandwidth does VoIP need per call?

VoIP bandwidth depends on the codec. Uncompressed G.711 typically uses about 90 to 100 kbps per call in each direction, and compressed codecs such as Opus use less. Multiply the per-call figure by your peak number of simultaneous calls, then add headroom for video and other traffic. Ask each provider for its own per-call figure in writing.

Do VoIP providers require long-term contracts?

Many VoIP providers offer month-to-month plans, while others discount annual or multi-year terms. Before signing a term contract, check the auto-renewal notice window, the early termination fee formula, and whether you can reduce seats mid-term. A 12-month term with a 30-day non-renewal notice and a capped termination fee is a reasonable middle ground.

Is VoIP secure enough for sales and support calls?

VoIP can be secure for sales and support calls if the provider encrypts signaling with TLS and media with SRTP, enforces single sign-on or two-factor login, and offers toll fraud controls such as international calling limits. Ask how call recordings are stored, who can access them, and whether call data is used to train AI models.

Does VoIP work with 911?

Yes. Interconnected VoIP must support 911 under FCC rules. Kari's Law requires direct 911 dialing without a prefix and on-site notification when someone calls 911, and RAY BAUM's Act requires dispatchable location. Remote and hybrid staff need a way to update their 911 address in the app so responders go to the right place.

Put this into practice with Voicalyst

Voicalyst is the cloud phone system US sales and support teams set up in minutes: a business phone system with cloud telephony, AI call summaries and texting.

Start free trialBook a demo
VE

Voicalyst Editorial Team

Guides and research from the team building Voicalyst.