Dental Software Support vs Dental IT Support: Who to Call (2026)
The front desk cannot open the schedule, the hygienist's sensor just stopped capturing, and the software vendor thinks it might be your network. You have two numbers and no idea which one owns this. This page answers it in the order you need: who to call first, how to tell in a minute, and what to send so the ticket is not bounced.
Call the software vendor when the error names the application and shows on every workstation: licensing, product defects, module settings, vendor updates and vendor-hosted services. Call your dental IT provider when one machine, the server, the network, a sensor, a login or a backup is involved. Not sure? Call IT, which can see the whole environment.
That boundary resolves most of the back-and-forth dental teams live with. Below is the decision tree, a responsibility matrix, the four kinds of "help with dental office software", the scenarios practices actually call about, what the vendors themselves publish about the limits of their support, and what to require from a provider that supports practice software.
Call the software vendor when the error names the application and shows on every workstation: licensing, product defects, module settings, vendor updates and vendor-hosted services. Call your dental IT provider when one machine, the server, the network, a sensor, a login or a backup is involved. Not sure? Call IT, which can see the whole environment.
- The software vendor owns the product. The IT provider owns everything the product runs on.
- Symptoms rarely announce which side they belong to, so someone must own the diagnosis.
- One workstation failing and every workstation failing are almost never the same root cause.
- Imaging bridges, sensors, and CBCT sit on the boundary and need both parties.
- The office manager should never be the person relaying technical detail between two vendors.
In this guide
- Who do you call first for a dental IT problem: the vendor or the IT provider?
- Where does the line between the vendor and IT actually fall?
- Responsibility matrix
- What does "help with dental office software" actually mean?
- The twelve scenarios practices actually call about
- When the answer is both
- Notes on Dentrix, Eaglesoft, Open Dental and the imaging suites
- What should a dental IT help desk do with a software ticket?
- Dental software support vs dental IT support vs general IT support
- What to require from a dental IT provider that supports practice software
- What to send before you call
- The IT side: what Legend supports behind your software
- Tired of Being Sent Back and Forth?
- Sources and further reading
- Frequently asked questions
Who do you call first for a dental IT problem: the vendor or the IT provider?
Call the IT provider first when the problem touches a machine, a login, a device, the network or the server, which is most of them. Call the vendor first only when the error names the application, appears on every workstation at once, and nothing changed. When you cannot tell, the IT provider owns the diagnosis and the vendor hand-off.
Here is the decision tree the office can run in about a minute. Each step is a question you can answer by looking, not by knowing anything technical.
- Is it one workstation or every workstation? One machine, one operatory, one user: call the IT provider. The cause lives in that machine, its profile, its drivers or its path to the server. Every machine at once: go to question 2.
- Does the error message name the application, the licence or a module? A dialog from Dentrix, Eaglesoft, Open Dental or your imaging suite that talks about licensing, a product error code, a module, a report or a vendor update, on every machine: call the vendor, and tell IT a ticket is open. A message about a drive, a path, a server, a database connection, a certificate or a login: call IT.
- Did anything change in the last 24 hours? A Windows update, a new PC, a new sensor, a vendor update, a password change, a moved cable, a power cut. Anything on that list: call IT first, because the change is the suspect and IT can see it. Nothing changed: go to question 4.
- Is a device in the loop? Sensor, intraoral scanner, CBCT, panoramic, printer, scanner, card reader, phone. Call IT. Device problems are driver, cable, port, permission or storage-path problems until proven otherwise, and the vendor will ask you to prove that anyway.
- Is the thing that failed a hosted service? Claims, e-prescribing, patient texting, online forms, a cloud practice management system, payment processing. Check the vendor's status page if one exists and call the vendor; ask IT at the same time to rule out the firewall, DNS and internet circuit, which takes minutes and is the usual cause when only your office is affected.
- Still unsure? Call IT. The provider that can see the whole environment opens the vendor ticket in your name, joins the call and reports back in plain language.
Two patterns sit behind every branch. Scope tells you the layer: one machine means the machine, every machine means the shared thing (server, database service, network, vendor service). Change tells you the suspect: whatever moved last is where the diagnosis starts. A provider that asks those two questions on the first call, before asking you to restart anything, is doing the job properly.
Who to call, by what you can observe from the chair or the front desk
| What you can see | Most likely layer | Call first | Tell the other party |
|---|---|---|---|
| One workstation cannot open the software; others are fine | That machine (profile, driver, mapped drive, security agent, partial install) | Dental IT provider | Nothing yet; IT escalates with logs if the install itself is damaged |
| Every workstation lost the database at the same moment | Server, database service, storage or network | Dental IT provider | Vendor only if IT finds database corruption after the service is back |
| The same product error code on every machine, nothing changed | The application | Software vendor | IT, so it can confirm the environment is healthy and the ticket is not bounced |
| Sensor, scanner or CBCT stopped capturing | Device driver, cable or port, calibration file, storage path, permissions; then the bridge | Dental IT provider | Imaging vendor joins once IT has documented what is ruled out |
| Software is slow at certain times of day | Storage, network, endpoint security scans, a backup job, an undersized server | Dental IT provider | Vendor if measurements point at the application or the database engine |
| Claims, texting, e-prescribing or online forms failing; everything local works | Vendor-hosted service, or the office's outbound path | Software vendor | IT rules out firewall, DNS and outbound filtering at the same time |
| A doctor cannot log in from home | Identity, remote-access path, MFA | Dental IT provider | Vendor only for a cloud PMS login that fails from every location |
| Printer or scanner stopped working inside the software only | Driver, default device, spooler, TWAIN or WIA source | Dental IT provider | Vendor if the device works everywhere except inside their product |
| A Windows update broke something this morning | Operating system, driver, security agent | Dental IT provider | Vendor if its product needs a patch for that update |
| Licensing, seat count, renewal or a "trial expired" message | Product entitlement | Software vendor | IT confirms deployed counts match what is billed |
| Suspicious login, locked files, ransom note | Security incident | Dental IT provider, immediately | Vendors whose hosted services may be affected, once the scope is known |
| Nobody can tell | Unknown | Dental IT provider | IT opens and owns the vendor ticket |
Where does the line between the vendor and IT actually fall?
A practice management or imaging vendor supports its own product: license keys and seat counts, defects in the software, application-level configuration such as fee schedules and module settings, its own update packages, and any hosted service it runs. Vendors also publish minimum specifications and installation requirements, and those documents are the reference point when a dispute starts. For the company-by-company view (software, imaging, scanner, phone, payment and cloud makers), see our map of dental technology companies.
A dental IT provider supports the environment: workstations and operating systems, the server or hosting arrangement, the network and internet circuits, Wi-Fi, switching and firewalls, user identity and file permissions, drivers and imaging hardware connectivity, patching, endpoint security, and backup and recovery. Our page on managed IT services for dental practices describes that scope, and the helpdesk page covers daily triage. If you want the whole picture of what a practice runs, from the server to the card reader, see the full technology stack a dental practice runs.
The vendors draw the same line in their own documentation. Open Dental's manual says plainly, on its multiple-locations page: "Reminder : Open Dental Support cannot assist with network setup. It is recommended to have a capable IT set up and maintain any network settings." Its network-and-computer-setup page opens with "We recommend working with a networking professional to set up your network and computers." Henry Schein One's Dentrix support portal separates the two cases at the front door: a "Dentrix Connection Tool" for "connection issues, i.e. unable to connect to the Server or Database errors, etc." and a "Dentrix Workstation Installer" for installing Dentrix on a new workstation. The products are built on the assumption that somebody else owns the environment.
One responsibility is easy to overlook: coordination. Somebody has to gather evidence, decide which side owns the fault, open the vendor ticket, and stay on the call. In practices where nothing gets resolved, that role is unassigned and lands on the office manager. In managed IT for dental clinics, that coordination role is usually written into the agreement, so the practice knows who stays on the call. That is also the plainest difference between dental IT support and a general IT shop: a dental provider already knows which side of the line a sensor driver, an imaging bridge or a claims module sits on.
Under HIPAA, both relationships can carry obligations. A vendor with access to protected health information is generally a business associate, and HHS addresses software vendors specifically in its published FAQ and in its broader business associate guidance. The regulatory definition at 45 CFR 160.103 turns on whether a person "creates, receives, maintains, or transmits protected health information" on the practice's behalf, and it lists "practice management" among the covered functions. The safeguards around the systems themselves fall under the HIPAA Security Rule. Keep a signed agreement on file for every party that fits the definition; which parties fit is a question for the practice's compliance adviser.
Responsibility matrix
| Problem | First call | Why | What good coordination looks like |
|---|---|---|---|
| Application will not open on one workstation | Dental IT provider | Points at that machine, its profile, drivers, or path to the server | IT checks other workstations, then escalates with logs if the install is damaged |
| No workstation can reach the database | Dental IT provider | Server, service, storage, or network scope | IT restores the service or the data path, and involves the vendor if the database itself is corrupt |
| Error naming the application, on every machine | Software vendor | Product defect or configuration | IT confirms the environment is healthy first so the ticket is not bounced back |
| Sensor, scanner, or CBCT stops capturing | Both | Bridge software is the vendor's, drivers and connectivity are IT's | IT verifies the device, driver, and share path, then joins the imaging vendor call |
| Software is slow at certain times | Dental IT provider | Usually storage, network, endpoint security, or contention | IT measures the bottleneck and shares data if the vendor must tune the application |
| Version upgrade | Software vendor | The vendor owns the upgrade package and its prerequisites | IT validates specs, backups, and a rollback point, and schedules the window |
| New workstation or operatory | Dental IT provider | Hardware, imaging, and network setup | IT builds and images the machine, the vendor supplies licensing and install media |
| Restore after data loss | Dental IT provider | Backups are infrastructure | IT restores, then the vendor validates database integrity |
| Remote access for a doctor at home | Dental IT provider | Identity and security controls | IT provides a controlled path, not an ad hoc remote tool |
| Suspicious login or ransomware indicators | Dental IT provider, immediately | Incident response is infrastructure work | IT contains and investigates, then notifies affected vendors |
| Licensing, seat counts, renewals | Software vendor | Product entitlement | IT confirms deployed counts match what is billed |
| Claims or e-services module failing | Software vendor | Vendor-operated service | IT rules out the firewall, DNS, and outbound filtering first |
| Windows update broke the software or a device | Dental IT provider | Operating system, driver and security-agent changes are environment work | IT identifies the update, rolls it back or applies the vendor's patch, then updates the patch policy |
| Printer, document scanner or card reader fails inside the software | Dental IT provider | Driver, default device, spooler, TWAIN or WIA source | IT proves the device works outside the application, then brings the vendor in if it fails only inside |
| Cloud practice management login fails | Both | The vendor runs the service; the office owns the browser, the client bridge and the circuit | IT checks the status page, DNS and the local client, then the vendor handles the account |
| Email, Microsoft 365 or the phone system is down | Dental IT provider | Identity, tenant and network scope | IT separates a provider outage from a local fault and tells the practice which it is |
| Staff cannot find a feature or a report | Software vendor (training) | Product knowledge | IT stays out of it unless a permission or a missing module is the cause |
What does "help with dental office software" actually mean?
"Help with dental office software" covers four needs, each with a different first call: training on a feature the product already has, configuration of settings the practice controls, a defect in the product itself, and a fault in the environment it runs on. The vendor owns the first three; your IT provider owns the fourth and the diagnosis when they blur.
Sorting the request before you dial saves most of the wait.
The four kinds of "help with dental office software" and who does each
| The request sounds like | What it is | Who does it | What to have ready |
|---|---|---|---|
| "How do I run the aging report / set up a new provider / post this insurance payment?" | Training | Software vendor (support or training team); the vendor's manual and webinars first | The exact screen and what you expected to happen |
| "Treatment plan fees are wrong / the schedule shows the old hours / the reminder texts stopped" | Configuration the practice controls | Software vendor walks you through it; IT is not involved unless a permission blocks it | The setting you changed, when, and who has admin rights |
| "This button has errored since the last update, on every computer" | Product defect | Software vendor; IT confirms the environment is clean so the ticket is not bounced | Screenshot, product version, whether it started after a vendor update |
| "It works at the front desk but not in operatory 3" / "it is slow after lunch" / "images are missing" | Environment | Dental IT provider; the vendor joins only if IT's evidence points inside the product | Which machines, when it started, what changed, whether imaging or claims are affected too |
Two refinements matter in practice. First, Open Dental states a limit most practices do not know about: "Up to two specific issues can be answered per call/email/chat." That is a sensible rule for a product support desk, and it means a training question and an environment question in the same call will cost you one of your two slots on something the vendor cannot fix anyway. Second, vendors sell training as a separate service; if the real problem is that nobody on the team was shown the module, the answer is a training session, not a support ticket, and your IT provider should say so rather than spend an afternoon on it.
Where IT does belong in a training-shaped request: a report that "disappeared" is often a user without the permission, a module that "went away" is often a licence that lapsed, and a feature that "stopped syncing" is often a scheduled task on a server that was rebooted. Those are environment questions wearing a training costume, and the scope-and-change test from the decision tree catches them.
The twelve scenarios practices actually call about
One workstation cannot open the application. Start with what is different about that machine: a recent Windows update, a corrupted profile, a mapped drive that no longer resolves, endpoint security quarantining a component, or a partial install. This is IT work, and the vendor is only involved if the install fails for a product reason. Open Dental's own troubleshooting manual follows the same logic: when the product "crashes immediately" on one workstation, it points at the machine's graphics libraries and the .NET components before anything in the product.
Every workstation loses the database. This is a server, service, storage, or network fault until proven otherwise. IT should check whether the database service is running, the server is reachable, the volume is full, or a switch or cable path failed. This is also where a tested backup matters most, which is why backup and recovery belongs to the same party that owns the server. Our guide to dental data backup explains what a usable backup of a practice database and image store looks like, and what to do when the dental server is down covers the first hour.
A sensor, intraoral scanner, or CBCT stops working. Imaging sits on the boundary. The bridge application belongs to the vendor; the USB controller, driver version, calibration files, image storage path, and permissions belong to IT. IT should verify the device on another workstation and confirm the storage path first, then bring the imaging vendor in with those findings documented. One dental-only MSP put the scale of this bluntly on r/msp in January 2025: the "majority of our calls are about scanners", and the device vendors "straight up tell you it's a driver issue". The office manager's version, from r/Dentistry in November 2025, was that the sensors were "giving us problems left and right". The fix is the same in both threads: a documented chain from device to driver to bridge to database, owned by one party. Our dental imaging integration troubleshooting guide carries the symptom-to-layer table, and a sensor not working after a Windows update covers the most common trigger.
The software is slow. Slowness is the most commonly misrouted issue in dental IT. Establish when it is slow, which machines are affected, and what else is running. Aging drives, a saturated network segment, an undersized server, endpoint security scanning the database directory, or a backup job running during patient hours are frequent causes. If measurements point at the application, the vendor can act on real data instead of an impression. The vendors do have their own levers: Open Dental's "Troubleshooting Slowness" page lists a database-engine upgrade, a latency test, database maintenance and a separate report server, and expects its support team to help with those. The division is clean: IT proves where the time goes, the vendor tunes what is inside the product. Why is Dentrix slow? and why is Open Dental slow? walk through the five-question trace for each platform.
A version upgrade is due. The vendor owns the upgrade. IT owns readiness: checking hardware and operating system requirements against published specifications, verifying a current backup and a rollback point, scheduling outside patient hours, and testing imaging bridges and the claims path afterward. The current server and workstation numbers for the three big platforms are in our dental software system requirements guide.
A Windows update broke something. The symptom arrives as a software or imaging failure, but the cause is an operating-system or driver change, which makes it IT's call first. IT identifies the update, decides between rolling it back and applying the vendor's fix, and then adjusts the patch policy so the next one is tested before it reaches an operatory. Our dental IT patch management guide explains how a safe policy works, and the r/msp thread above carries the practitioner's rule of thumb for new installs: "Don't update .net, twain, drivers for the first 3 months".
A new workstation or operatory is going in. IT builds the machine, joins it to the network, applies the security baseline, connects imaging hardware, and validates database access. The vendor supplies licensing and installation media; Patterson, for example, publishes a workstation installation document for Eaglesoft that walks through the installer step by step, and the Dentrix portal offers a workstation installer. Cabling, power, and switch capacity should be planned in advance; our guide to dental office network setup covers that groundwork, and which computers to buy for a dental office covers the machines themselves.
A restore is needed. Backups are infrastructure, and the measure of one is a documented test restore rather than a green status icon. Open Dental documents its own backup tool, which complements rather than replaces an infrastructure backup with offsite copies. The vendor's own page is candid about the limits: "This tool does not encrypt data, so consider an encrypted device or encryption software to ensure data is protected while in storage." and "Note: The Backup tab is unavailable for Open Dental Cloud Users." A single deleted chart or X-ray is a smaller case with its own first steps; see deleted a patient file or X-ray? what to try first.
A doctor needs remote access. This is an identity and security question. It belongs on a controlled path with multi-factor authentication and logging, reviewed when staff change. Both the vendor and the IT provider will at some point ask to connect to a workstation remotely; staff should know what a legitimate remote-support session looks like, which is the subject of ScreenConnect and remote-support tools: what dental staff should know.
A caller says they are "from support". Vendors and IT providers both call practices, and so do people pretending to be either. The office needs one rule: nobody gets remote access, a password or a payment change on an inbound call; the office hangs up and calls the known number back. Fake IT support and voice-clone scams aimed at the front desk has the script.
Multiple locations need to share data. Site-to-site connectivity and how the database is reached across sites are IT responsibilities, but supported architectures come from the vendor. Open Dental publishes guidance for multiple locations, and the same page carries the reminder that its support team "cannot assist with network setup". Design decisions should follow supported patterns rather than workarounds, with IT building the network the vendor's architecture assumes.
A suspicious login or ransomware indicator appears. Treat this as an incident immediately. Containment, investigation, and recovery are IT responsibilities, and vendors whose hosted services may be affected should be notified once the scope is understood. This is the one scenario where the order is not negotiable: IT first, by phone, before anyone touches the machine. Our dental cybersecurity services page describes the layers that make this call rarer.
When the answer is both
Plenty of problems are genuinely shared. An imaging bridge failing after a Windows update involves the operating system, a driver, and the vendor's software at once. A cloud practice management system that will not load involves the vendor's service, the browser, a local client component and the office's internet circuit.
The failure mode here is procedural, not technical. The vendor says it is the network, IT says it is the application, and the office manager relays messages between two parties who never speak to each other. Each party is answering honestly about its own layer; nobody is looking at the join.
The fix is to assign a single owner for the diagnosis, and that owner should be the IT provider, because it can see the whole environment. IT gathers evidence, opens the vendor ticket in the practice's name, joins the call, records what has been ruled out, and reports back in plain language. The practice should be told what is happening, not asked to translate it.
A useful test of whether your current arrangement works: the next time a vendor says "it's your network", ask your IT provider for the measurement that proves or disproves it (a latency test from the affected workstation to the server, a packet-loss figure, the storage-path check) and ask the vendor for the log line that points at the environment. If either side answers with an opinion instead of evidence, the ticket will bounce again.
Notes on Dentrix, Eaglesoft, Open Dental and the imaging suites
Product names below are used for identification only.
Dentrix. Henry Schein One publishes product information on the Dentrix site and operates a support portal. The portal itself splits the first step by cause: a connection tool for server and database connection errors, a workstation installer for new machines, and the resource centre for guides. Product defects, licensing, and application configuration go to the vendor; server performance, workstation health, imaging connectivity, and backups sit with the IT provider. Legend's Dentrix IT support page describes the environment side.
Eaglesoft. Patterson publishes installation documentation, including a workstation installation guide that sets out prerequisites and installation steps. Those requirements are the reference point when validating an environment before an install or upgrade. See Eaglesoft IT support for the environment side.
Open Dental. Open Dental documents its environment expectations publicly, including computer and network setup, and is explicit that network setup is not something its support desk does. Its support page also defines the scope of a contact: "Up to two specific issues can be answered per call/email/chat." An IT provider can verify that a deployment matches the supported configuration before a ticket is opened; see Open Dental IT support.
Imaging suites (DEXIS, Carestream, Planmeca Romexis, Vatech, Dolphin). Imaging vendors support their acquisition and bridge software; the sensor's USB path, the driver version, the image store and the permissions on it are IT's. Open Dental's own scanner page states the test every imaging vendor will apply to a document scanner, and it generalises to sensors: "If the scanner doesn't work outside of Open Dental, it will not work inside of Open Dental." IT proves the device works in the operating system first. Legend's platform pages for DEXIS, Carestream Dental, Planmeca Romexis, Vatech and Dolphin Imaging describe the environment side for each, and the hub for all of them is dental practice management software support.
None of this replaces the vendor's product support. A dental IT provider should make the vendor relationship work better, not stand in front of it. What each vendor publishes about its own support hours and fees is collected in our page on what dental software and imaging vendors publish about their support.
What should a dental IT help desk do with a software ticket?
A dental IT help desk should take the call whatever the cause, run the scope-and-change triage, fix what is in the environment, and, when the fault is inside the product, open the vendor ticket in the practice's name, attach the evidence and stay on it until it closes. The office should never relay between two support desks.
The hand-off, step by step:
- Intake. The help desk records who is affected, which machines, when it started and what changed. It asks before it restarts anything. (Our guide to what a dental IT help desk should do covers the request types and how a call should run.)
- Triage. Scope and change, then the decision table above. Most tickets end here, in the environment.
- Evidence. Before any vendor call, the help desk assembles the pack: the exact error, the product version, the workstation name, the server reachability and latency result, the storage-path check, whether other workstations reproduce it, and what has been ruled out.
- Vendor ticket in the practice's name. The practice owns the vendor relationship and the licence, so the ticket is opened under the practice's account, with IT's contact as the technical point. That keeps the practice's support history in one place and keeps the vendor from closing a ticket because "the customer did not respond".
- Stay on the call. IT joins the vendor session, answers the environment questions, makes the environment changes the vendor asks for, and records them.
- Closure note. A plain-language note to the office: what was wrong, which side fixed it, what was changed, and what to watch for.
What a practice should expect to see from this, in writing: ticket ownership named on the agreement, a closure note after every vendor escalation, and a monthly count of vendor-escalated tickets with the layer that turned out to be at fault. That last number is the one that tells you whether the "it's your network" claim is true for your office.
Dental software support vs dental IT support vs general IT support
Three parties can answer a dental software call: the software vendor, which knows the product but not your office; a general IT company, which knows networks but not the product; and a dental IT provider, which knows which side of the line a sensor driver, an imaging bridge or a claims module sits on. The difference shows up at the hand-off.
The general IT company's weakness is the imaging chain and the vendor relationship: it has to learn which bridge talks to which database on your time, and it has no standing with the vendor's support desk. The vendor's weakness is everything outside its installer. Our comparison of dental IT support vs general IT support sets out the six moments where the difference shows, and remote vs onsite dental IT support explains which of these calls can be fixed without a visit. Add the vendor into that picture and the division of labour is: vendor owns the product, IT owns the environment and the diagnosis, and the practice owns the relationship with both.
What to require from a dental IT provider that supports practice software
Ask for evidence, not assurances. If you are asking "what should I look for in dental IT support", this list is the software-specific part of the answer.
- Named practice management and imaging platforms the team has supported, and roughly how many practices on each.
- A description of who opens and owns vendor tickets, in writing.
- Willingness to join vendor calls rather than forwarding email.
- A documented restore test from the last quarter, with the date and the result.
- A written server and workstation specification checked against the vendor's published requirements.
- An imaging inventory approach covering sensors, scanners, and CBCT, including driver and bridge versions.
- Defined maintenance windows that sit outside patient hours.
- A business associate agreement and a description of how administrative access is controlled and logged.
- Practice ownership of tenants, domains, backup platforms, and network devices, with the provider holding delegated access.
- A clear escalation path with response expectations and a named point of contact.
- A patch policy that says how Windows and vendor updates are tested before they reach an operatory.
- A closure note after every vendor escalation that names which side the fault was on.
- A monthly count of vendor-escalated tickets by layer, so "it's your network" can be checked against your own history.
Our guide to choosing a dental IT provider covers the wider evaluation, and if you are already mid-decision, switching providers without downtime covers the transition mechanics. Response expectations are a contract matter, and our note on dental IT support SLAs and response times explains what a written one should say.
What to send before you call
A short checklist that shortens most tickets:
- The exact error text, as a screenshot or photograph of the screen.
- Which machine or machines are affected, by name or operatory.
- Whether it affects one user, one workstation, or everyone.
- When it started, and what changed just before that.
- Whether anyone has already restarted the workstation or the server.
- Whether imaging, claims, or the phone system are affected as well.
- Whether a vendor ticket is already open, and its number.
- The product and version shown on the application's "About" screen.
- Whether the problem follows the user to another workstation, or stays with the machine.
The same pack works for the vendor and for IT, which is the point: whoever you call first, the other party receives the same facts. Our dental IT support ticket checklist has a copy-and-paste template.
The IT side: what Legend supports behind your software
Legend Networking supports the IT environment behind Dentrix, Eaglesoft, Open Dental and Archy, and behind the DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging software. The helpdesk is staffed by in-house engineers; no outsourced first-level triage. Legend has served over 3,500 practices since 2004, holds a 4.8 rating from 173 Google reviews and provides 24/7 monitoring. Ian Lynch, 22 years in dental IT, oversees the NOC, onsite dispatch and client technology roadmaps.
Whoever your provider is, Legend included, ask for vendor-ticket ownership and the closure note to be written into the agreement; the list under "What to require" is the scorecard to bring. For one new practice, Timberwood Dental in San Antonio opened with Legend creating the tech infrastructure and providing daily support; the Timberwood Dental project page shows the project. Support is remote-first nationwide, with onsite dispatch by appointment across the dental markets Legend serves; see Dental IT in your city.
Tired of Being Sent Back and Forth?
If nobody in your current arrangement owns the diagnosis, ask for a review of the network, server, security, backup and vendor dependencies behind your recurring software problems. A Free Dental IT Assessment looks at the computers, software, network security, backups and performance behind those tickets and ends in written findings with prioritized recommendations. Start a conversation from the dental IT support page with the "What to require" list as your scorecard, or go straight to the Free Dental IT Assessment.
Sources and further reading
- Dentrix and the Dentrix support portal
Vendor pages checked 6 November 2026. Dentrix, Eaglesoft, Open Dental, and other product names are trademarks of their respective owners and are used here for identification only. Legend Networking claims no affiliation, endorsement, or partnership with those vendors in this article.
Frequently asked questions
Should I call my software vendor or my IT provider first?
If the problem is inside the application on every machine, such as licensing or a product error code, call the vendor. If it affects one workstation, the server, the network, imaging hardware, a login or a backup, call the IT provider, who can see the whole environment. When you cannot tell, call IT and let it open the vendor ticket.
Who should I call for dental IT support when I don't know what broke?
Call your dental IT provider. Who to call for dental IT support when the cause is unclear is settled by one rule: the party that can see every layer owns the diagnosis. IT checks scope (one machine or all) and change (what moved last), fixes what is in the environment, and opens the vendor ticket in your name if the fault is inside the product.
Does a dental IT provider replace Dentrix, Eaglesoft, or Open Dental support?
No. Product support, training, licensing and defect fixes remain with the software vendor, and your support contract with the vendor still matters. A dental IT provider supports the infrastructure the software runs on, proves which side a fault is on, and coordinates with the vendor when a problem crosses the boundary, so the practice is not the relay.
Why does my software vendor say it is a network problem?
Because it often is, and because the vendor can only see its own product. Application symptoms are frequently caused by storage, network, endpoint security or a backup job running at the wrong time. The right response is measurement rather than argument: ask IT for the latency and storage-path results from the affected workstation, and ask the vendor for the log line.
What counts as help with dental office software, and who provides it?
Help with dental office software is four things: training on a feature, configuration of settings the practice controls, a product defect, and a fault in the environment the software runs on. The vendor handles the first three, usually with a limit per contact, and your IT provider handles the fourth plus the diagnosis when the request mixes them.
Who is responsible for backups of my practice management database?
The IT provider owns the backup and recovery process, including offsite copies and documented test restores. Vendor backup tools help but are not a complete strategy; Open Dental's own backup tool page notes that it does not encrypt data and is unavailable to its cloud users. Our backup and recovery page explains the difference between a tool and a tested process.
Is my dental software vendor a HIPAA business associate?
Generally yes, when the vendor creates, receives, maintains, or transmits protected health information on the practice's behalf; that is the test in the regulatory definition at 45 CFR 160.103, which lists practice management among the covered functions. HHS addresses software vendors directly in its published FAQ, and practices should keep signed agreements on file and confirm the list with their compliance adviser.
What should happen when imaging stops working?
The IT provider verifies the device, driver, storage path, and permissions, proves the device works outside the application, and documents what has been ruled out. If the bridge or acquisition software is at fault, the imaging vendor is brought in with that evidence assembled, so the first vendor call starts from facts instead of from "it's a driver issue".
Does Open Dental support help with network setup?
No. Open Dental's own manual states that its support team cannot assist with network setup and recommends having a capable IT provider set up and maintain network settings. Its support page also limits a contact to two specific issues. Network, server, workstation and backup work for an Open Dental office belongs to the practice's IT provider.
How do I stop the back-and-forth between vendors?
Assign a single owner for diagnosis and vendor coordination in writing, as a stated expectation of your IT agreement, and have vendor tickets opened in the practice's name with IT as the technical contact. The office manager should receive a closure note after each escalation rather than relay technical detail between two support desks.
Should the vendor or IT handle a Windows update that broke my dental software?
Call IT first. A Windows update is a change to the operating system and its drivers, which is environment work: IT identifies the update, rolls it back or applies the vendor's patch, and tests imaging and claims afterwards. The vendor is involved only if its product needs a fix for that update, and IT should open that ticket with the update number attached.
Can an IT provider guarantee our software will never go down?
No. Practice software depends on hardware, networks, and vendor services that can all fail, and some of those failures are outside anyone's control in the office. What a provider can do is reduce the likelihood, shorten recovery, keep a tested restore ready, and make sure one named party owns every outage from the first call to the closure note.

