Dental Phone Systems for Denver Practices: VoIP, Call Routing and What to Check

Three phone demos are on the calendar, the front desk has opinions, and the main line patients have dialed for years still sits with the carrier that mails a paper bill. Someone asked what happens on a snow day; nobody wrote it down.

Everything below is the checklist behind that sentence. This page does not rank vendors and does not recommend one. It tells you what to put in front of every vendor you are already talking to, what your network has to provide, what the two federal rules say in their own words, and how a Denver practice keeps its phones answered when the power or the roads give out.

Why do Denver dentists search for phone systems, and what are they actually choosing?

A Denver dentist searching for a phone system is choosing five things at once: a cloud calling service, its connection to the practice management software, a call-routing design for a dental week, a port of the current number, and the office network under the phones. The demo shows the first; the other four decide whether it works.

Ask the front desk what a new system has to get right and the answers come from their week: whether the chart is already on the screen when the line rings, whether the Saturday hygiene schedule has someone answering or a voicemail greeting, whether the confirmation texts went out from the practice number or from a number patients do not recognize, and what happened to the call that came in at 7:40 on a Tuesday while the opening checklist was still running.

That is why the search phrases are what they are. Owners type "phone systems for dentists Denver" and "dentist office phone systems Denver" rather than the name of a product, because what they want is a dental call-handling setup, and the product is only one part of it. The local search results are led by a provider's services page and a round-up or two; what is missing from them is the list of things to check, which is what this page is.

Two pages on this site sit beside this one. The site's page on dental VoIP phone systems is the main page on this topic here; this article does not restate it. Everything else a Denver office runs on, the network closet, the backups and the people you call when a workstation dies, is covered in our Denver dental IT guide, a planned page that goes live alongside this one. Read this page as the phone chapter of that guide, written so that you can hand it to the office manager and the three vendors you have on the calendar.

What should a dental phone system do that a business phone system does not?

A dental phone system does three things a business phone system does not: it looks up the caller in your practice management software and shows the chart as the call lands, it texts and confirms appointments from the practice number with the result recorded on the patient, and it routes calls around a dental week of Saturdays and emergencies.

It helps to separate the connection to your practice management software into three levels, because vendors describe all three with the same word and a sales demo rarely tells you which one you are buying.

• • Caller identification from the phone's own contact list. The handset shows a name because someone typed it into the phone system's directory. Nothing is read from Dentrix, Open Dental or Eaglesoft. This is what a general business system gives you.
• • Chart lookup. The system matches the caller's number against the practice management database and opens that patient's record on the front-desk screen before anyone says hello. This is the behavior most dental vendors demonstrate, and it is the one most front desks mean when they say "it integrates".
• • Chart update. The system writes something back into the record: a note that the call happened, a voicemail transcription attached to the patient, an appointment confirmation changed to confirmed because the patient replied to a text. This is the level that saves retyping, and it is the one to ask about by name.

Ask each vendor which of the three levels applies to your software, and ask them to show it on your software, not on the one in their demo environment. A practice on Dentrix Ascend, Curve or Denticon in the cloud is usually looking at a different connection than a practice with a Dentrix or Eaglesoft server in the closet, and a vendor that supports one well may support the other thinly. The national VoIP guide for dental offices walks through the features themselves in more depth; this page stays with what to check.

The second difference is texting. Patients reply to texts from the practice number; they do not reply to texts from a toll-free number they have never seen. The text has to come from the main line, the reply has to land where the front desk works, and the confirmation has to change the appointment status in the schedule rather than in a separate inbox that someone checks at lunch. Those are three separate questions to ask.

The third difference is the week itself, and that is the subject of the routing section below. Before that, here is how the features sort by the size of the practice, because a solo office and a three-location group do not need the same things and should not pay for them.

Use the column that fits you to strike out the features you are being sold and do not need. The vendor's job is to show you the ones in your column working on your software.

What does the phone system need from your Denver office network?

A cloud phone system needs an internet circuit with a second path for when it fails, a switch that powers the handsets, a separate voice lane with priority so a radiograph upload cannot interrupt a call, wired drops at the front desk and in any operatory with a phone, and battery backup on the switch, firewall and carrier equipment.

Nobody sells you this part, which is why it is the part most often missing when the phones sound bad. The handsets are only as good as the network under them, and a dental network already carries practice management traffic, imaging traffic and whatever the guest Wi-Fi is doing. Greg Davis, the CEO of a network vendor, put the dependency plainly in Dental Economics in 2023: "When your connectivity goes down, your ability to efficiently serve patients ceases." Vendor's words, but nobody who has run a front desk through an outage disagrees.

The table below is what to ask your IT provider to confirm, in writing, before the phone vendor's installation date. Where a requirement depends on your specific handsets or circuit, it says so rather than inventing a number.

If any row in that table is new to your current provider, the design work belongs with a provider that builds dental networks for both imaging and voice. The site's dental office network design page covers network design; the longer explanation of how a dental network is laid out, closet to operatory, is in dental office network setup, step by step.

A note on wireless. Handsets on Wi-Fi are convenient to install and inconvenient every day after that. Use the mobile app on a phone for the people who move; put every fixed handset on a wire.

How does porting your existing Denver number work, and what can go wrong?

Porting moves your number from the current carrier to the new service. Under 47 CFR § 52.35, the FCC gives carriers one business day to finish a simple port and four business days for a non-simple one. What goes wrong is usually on the practice's side: a mismatched account record, or the old service cancelled before the port completes.

Here is the regulation verbatim, worth keeping with your porting paperwork: "All telecommunications carriers required by the Commission to port telephone numbers must complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested by the new provider or by the customer." For a non-simple request the deadline stretches to four business days. The regulation also fixes the moment the clock starts: "An accurate and complete Local Service Request (LSR) must be received by the current service provider between 8 a.m. and 1 p.m. local time for a simple port request to be eligible for activation at midnight on the same day." Its definition of intermodal ports covers "Ports involving interconnected VoIP service", and that is exactly the move a Denver office makes when it leaves a landline carrier for a cloud phone system.

Two things the rule does not do. It does not define "simple" by a number of lines, so do not accept a vendor's assurance that a practice "under some count" is automatically a one-day port; ask the vendor which category your port falls into and why. And it governs carriers, not vendors: the new phone vendor submits the request, the current carrier acts on it, and the practice's job is to make the request accurate the first time.

"Accurate" is the whole game. The current carrier matches the port request against its customer record: the exact business name as the carrier has it, the service address as the carrier has it, the billing telephone number, the account number and, for many carriers, a PIN or an authorized signer. A practice that moved suites in 2019 and never updated the carrier's address, or that is billed under the dentist's old professional corporation name, will have a port rejected for a mismatch and the clock starts again. Get a copy of the current carrier's customer service record before the first vendor demo, and read it against your own paperwork.

The second failure is cancelling the old carrier early. A number that has been disconnected cannot be ported, because there is nothing to port. The old service is cancelled after the new system has answered calls on the ported number for a full clinic day, never before.

The checklist below gives every porting step an owner, which is the part that goes wrong when everyone assumes the vendor is handling it.

For a new office, the sequence is reversed: there is no number to port yet, and the question is how early to order the main line so that it is printed on the signage and the insurance credentialing in time. That belongs with the other opening-day timing decisions, which are the subject of the Denver dental startup IT article. The porting checklist above still applies the day a startup inherits a number from a practice it buys.

What do Kari's Law and RAY BAUM's Act require of a multi-line dental office?

Most dental office phone systems are multi-line telephone systems, and for those the rule implementing Kari's Law and RAY BAUM's Act, 47 CFR § 9.16, requires three things: 911 dials directly without a prefix, someone is notified when 911 is dialed, and a dispatchable location goes with the call. Confirm all three with your vendor and counsel.

The rule's words matter here, because a vendor's "we're compliant" is not a configuration you can check. The dialing requirement reads that the configuration must ensure "a user may directly initiate a call to 911 from any station equipped with dialing facilities, without dialing any additional digit, code, prefix, or post-fix, including any trunk-access code such as the digit 9". If your front desk still dials 9 for an outside line, 911 must work without it.

The second requirement falls on whoever installs or manages the system, who has to "configure the system to provide MLTS notification to a central location at the facility where the system is installed or to another person or organization regardless of location". In a practice, that is usually the front desk and the office manager's mobile, so that someone knows a 911 call was placed from the sterilization room before the ambulance arrives at the wrong door.

On location, the rule sets two dates that have both passed. "An on-premises fixed telephone associated with a multi-line telephone system shall provide automated dispatchable location no later than January 6, 2021." On-premises non-fixed devices, which is what a softphone on a laptop or a mobile app is while it is used in the office, were given until January 6, 2022, with the rule allowing a manual update or an alternative location method where an automated one is not technically feasible. "Dispatchable location" is the rule's term; ask your vendor to show you what each handset will send to the dispatcher, and whether it includes your suite number in a multi-tenant building on Colorado Boulevard or in a medical office park in Lone Tree.

What to check, in order:

1. 1. Pick up every handset, including the cordless one that lives in the lab, and confirm 911 dials without a prefix. Do not place a live test call without arranging it with your vendor; ask them how the test is done.
2. 1. Confirm who receives the notification and how: a screen alert at the front desk, a text to the office manager, both.
3. 1. Ask the vendor to print the dispatchable location for every handset and every softphone license, then read it against the building's actual suite and floor.
4. 1. Ask what happens when someone takes the mobile app to a second location, or home on a snow day, and whether the location updates.
5. 1. Put the answers in the contract file, dated, with the vendor's name on them.

This is a regulatory section, and the page states the rule rather than interpreting it. Ask your vendor to walk you through its configuration and ask your attorney whether anything about your building or your softphone use needs more. The HIPAA compliance support page on this site covers the privacy side of the phone system, which is a different question and comes later on this page.

How should calls route in a Denver practice — hours, after-hours, emergencies, multiple locations?

Calls in a dental practice should route by the time of week and the reason for the call: a person answers in clinic hours with overflow to a second ring group, lunch and Saturdays have their own paths, after-hours callers hear a short greeting with a separate emergency route, and a second location is reached by transfer, not redialing.

Routing is the design decision that the demo never shows, because the demo happens during business hours with one person answering. Build the table below with the office manager before any vendor demo, then ask each vendor to configure it in front of you. A vendor that cannot build your table in the demo will not build it better after you sign.

A few design notes from building tables like that one.

Keep the menu short. A dental caller wants a person; an auto-attendant with more than three options loses them. The menu's job is to separate emergencies from everything else after hours and billing from scheduling during the day.

Make after-hours emergency routing a route, not a recording. The emergency option should ring a clinician's mobile app, with a second person after it and an alert when neither answers, so that a weekend abscess does not sit in a voicemail until Monday.

Treat the group question as a design question. The search phrase "which phone systems are best for multi-location dental groups?" has no product answer; the answer is a routing design in which each location keeps its own number and greeting, calls transfer between offices without redialing, overflow goes to whichever desk is free, and one administrator sees every location. The IT side of that standardization, from a common network build per office to central visibility, is covered on the dental IT support for DSOs and multi-location groups page.

Separate your patients' line from your IT provider's line. Your phone routing is for patients. Separately, you should know when the people who fix the phones' network will answer you. Legend Networking publishes these hours: Help desk Mon–Fri 7 AM–7 PM CT, Saturday 8 AM–2 PM CT; 24/7 critical/emergency line. Translated to the Front Range clock, the help desk picks up from 6 AM to 6 PM Mountain on weekdays and from 7 AM to 1 PM Mountain on Saturdays. Those are hours for reaching Legend, not a feature of any phone system.

What happens to the phones when Xcel cuts power or the snow closes the office?

A cloud phone system keeps working through an office closure as long as calls have somewhere to go: the mobile apps and softphones of people working from home, a temporary greeting, and the emergency route unchanged. In the office, the switch, firewall and carrier equipment on a UPS keep the handsets alive as long as the batteries hold.

Denver gives a phone planner two specific, dated reasons to build for closures rather than hope.

The first is Xcel Energy's public safety power shutoffs. Colorado Politics covered Xcel's 29 April 2026 presentation to a Denver City Council committee, where Lyle Moore of Xcel told members: "The PSPS is something that is a last resort for us." According to that article, Xcel warns in stages. Beyond 72 hours, the utility raises its situational awareness and talks with emergency managers. Between 72 and 24 hours it carries out "72-hour outreach to critical customers and medically vulnerable" and "at 48 hours, outreach to customers in the area of concern"; inside the last 24 hours come "final notifications", sent less than four hours before the power is cut. Colorado Politics also noted that December 2025 brought two shutoffs west of the city, which followed a National Weather Service red-flag warning for the Front Range labelled a "particularly dangerous situation"; together they hit "more than 135,000 customers, with 12,000 residing in Jefferson and Boulder Counties alone", plus a warning sign for the city itself: "although Denver has not yet experienced a public safety power shut-off, the Mile High City came close in December". There is an earlier precedent: on April 6, 2024, Xcel cut power ahead of wildfire risk to about 55,000 customers, as Boulder Reporting Lab recounted in July 2025.

The second is snow. Denver's official total from the March 13–14, 2021 storm was 27.1 inches, which the National Weather Service's Boulder office called "the fourth largest storm on record since 1882". Losing a clinic day takes far less than a historic storm; all it takes is enough snow that the hygienist in Parker cannot get to Cherry Creek.

Neither event takes the phone system down if the phone system is in the cloud. What they take down is the building. So the plan is built around the Xcel notice stages, because those are the hours you actually get.

The pattern is older than cloud phones. Adrian Huang, DMD, recounted in a 2011 Dental Economics article how he opened a practice whose phones and software lived off site: "The phone was forwarded and we were able to remotely start scheduling patients from home or the library on our laptops through the cloud-based software." Fifteen years on, the forwarding is a mobile app and the library is a kitchen table, and the point stands: the phone line is the practice's continuity plan, as long as the scheduling software is reachable from wherever the people are. How to keep the schedule and the chart reachable while the building is dark is what Legend's dental backup and disaster recovery service page covers.

One thing this section does not claim: altitude. Denver's elevation is not a phone-system factor on any vendor documentation this page could find, and you should treat a sales line about it as colour. What Legend publishes for Denver practices, from managed IT to backups, is on its Denver dental IT services page.

Are call recordings, voicemails and texts patient data? What to ask about BAAs

Call recordings, voicemails and texts in a dental practice can contain protected health information, because patients say what hurts, which tooth and which medication on the phone. A vendor that stores or transmits that content is handling PHI on your behalf, so ask for a business associate agreement before you sign, and ask your attorney what else applies.

Three practical questions follow from that. Where are recordings and voicemail transcriptions stored, for how long, and who at the practice can play or read them? Does the texting feature keep message history, and does that history live inside the practice management software or in the vendor's platform? And what changes in the vendor's privacy configuration once the BAA is in place: some vendors restrict voicemail-to-email, transcription in notifications or texting under their privacy settings, so ask for that list in writing and have the front desk try the workflow that remains before you sign.

On top of HIPAA sits Colorado law. Colorado's breach notice law, C.R.S. § 6-1-716, carries the heading "Notification of security breach" and sets the deadline for telling Colorado residents who are affected, which is "not later than thirty days after the date of determination that a security breach occurred". The Colorado attorney general has to hear within that same window when the incident "is reasonably believed to have affected five hundred Colorado residents or more". Those two deadlines are quoted here and nothing more. How they apply to your office is for your attorney to say; preventing the breach in the first place comes down to safeguards, the territory of Legend's HIPAA compliance support page.

What does a dental phone system cost in Denver?

A dental phone system's cost has three parts: the vendor's subscription, which is the vendor's price and changes by how it is billed; the one-time items, which are handsets, installation, porting and any gateway; and the network work underneath, which is cabling, a PoE switch, a UPS and a failover circuit if you do not already have them.

This page does not print vendor prices. Every vendor publishes or quotes its own, they change without notice, and the only number that matters is the one on your quote with the billing basis written next to it. Ask whether the price is per handset, per user, per location or per practice, what the mobile app licenses cost on top, what the texting and recording features cost on top, and what the one-time implementation charge is. Then ask for the three-year total with your handset count, not the headline.

The network side is the part a practice can price before the vendor demo, because it belongs to the IT provider. Legend Networking lists three numbers for its managed IT service, quoted here as published. The plan range: Flat monthly plans $399.99–$1,200 per practice per month. What one office usually pays: Typical single-location practice $600–$900 per month all-in. The backup floor: Backup protection from $39.99 per month (storage-dependent). What sits outside those prices: Hardware procurement, major cabling projects and software licensing are quoted separately. In the terms of this page, a PoE switch purchase is hardware procurement and a large cabling job is a cabling project, so ask for each as its own quote. There is no Legend price for a phone system on this page, because the phone system is a decision you make with a phone vendor.

A note on contracts. Phone contracts in this category commonly run for a term with an early-termination charge, and the number you ported in is the number you will want to port out one day. Before you sign, read the clause that says what happens to your numbers at the end of the term, and what the vendor charges to release them.

What to verify before you sign

Thirteen questions, grouped the way the page is. Each one has an answer a vendor can show you in a demo or put in writing; if a vendor can do neither, that is the answer.

Integration

1. 1. Which of the three connection levels (caller identification, chart lookup, chart update) does your system provide for my practice management software, shown on my software?
2. 1. After an update to my practice management software, whose job is it to retest the connection, and what tells me it stopped working?

Porting

1. 1. For each of my numbers, is the port simple or non-simple under the FCC's rule, and what interval do you commit to in writing?
2. 1. Who at your company owns my port request from submission to completion, and when will I see the carrier's acceptance?

911

1. 1. Show me that 911 dials from every handset and softphone without a prefix, where the notification goes, and the dispatchable location each device will send.
2. 1. What happens to the dispatchable location when a softphone is used from home or from our second office?

Routing

1. 1. Build my call-flow table in the demo: clinic hours, lunch, Saturday, after hours with the emergency route, and the closure greeting.
2. 1. How does a second location transfer a call to the first without the caller redialing, and who administers both?

Recordings and texting

1. 1. Will you sign a business associate agreement, where are recordings and transcriptions stored, who can access them, and which features change under your privacy configuration?
2. 1. Do texts send from my main number, and does a patient's confirmation reply change the appointment status in my schedule?

Network

1. 1. What are your published network requirements (ports, bandwidth per call, QoS markings), and will you confirm with my IT provider that they have been applied before installation day?
2. 1. What happens to active calls when the primary circuit fails over to the backup path?

Contract

1. 1. What is the term, what does early termination cost, and what do you charge to release my numbers at the end?

What to ask your IT provider about the phones

The phone vendor owns the service; your IT provider owns the network it runs on. These are the questions for the second conversation.

Who is behind this page

This page is published by Legend Networking, a dental IT provider headquartered in Dallas, Texas, with 22+ years in dental IT (since 2004) and 3,500+ practices supported. Its published review figure is a 4.8 rating · 173 Google reviews. Its published model for where it works is onsite dispatch by appointment across served dental markets; remote-first nationwide. Operations sit with Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

What you have just read is a buyer's checklist, written to hold true whichever vendor you choose.