Choosing an IT Company for a Pediatric Dental Practice (2026)
The appointment texts to parents went silent on the last Thursday before school started, the busiest week of the year. The texting vendor blamed the practice software, the software vendor blamed the server, and the IT company had never heard of the texting tool.
This guide is for the owner or office manager of a pediatric practice who is choosing an IT company, or wondering whether the current one is doing the job. It sets out what the agreement should cover, where a vendor's job stops and the IT company's starts, what a clinic day of good support looks like, the warning signs, how to switch without losing your integrations, and what to ask before you sign. The owner page on IT support for pediatric dental practices covers how Legend plans and supports these offices; this article covers how to judge any provider, Legend included.
The right IT company for a pediatric dental practice takes written responsibility for the computers, network, Wi-Fi, server or cloud connection, backups and logins a children's office runs on, and for the connections between them: the practice software, the texting platform, the check-in tablets, the phones, the small sensors and the screens that keep children settled.
- A pediatric IT agreement should name the texting platform, forms and check-in tablets, entertainment network, small sensors, payer portals and a change freeze on school-break weeks, not only computers and a server.
- Vendors support their applications and devices; the IT company owns everything they run on and connects through, and should hold the ticket when a vendor says "not ours".
- The check-in tablets and the waiting-room screens are the two items most often left to nobody: put both in writing as managed devices and a separate network.
- Switching takes about four weeks: inventory every administrator account, move it into the practice's name, cut over on an evening outside peak weeks, then test texting, forms, imaging and phones with the front desk.
- The monthly report should show backup and restore dates, patch status per computer and tablet, connector uptime, tickets by system, account changes and changes made inside your frozen weeks.
In this guide
- Which systems make a pediatric support agreement longer than a general one?
- Which faults belong to the vendor, and which to the IT company?
- How should a pediatric clinic day run when the IT side is done well?
- How can you tell an IT company has never supported a children's office?
- Can a pediatric office change IT companies and keep texting, forms and imaging working?
- How should your IT agreement change when you open a second pediatric office?
- What to ask your IT provider: questions for a children's practice
- What to verify before you sign
- Which lines belong in a pediatric owner's monthly IT report?
- Legend Networking and children's dental offices
- Frequently asked questions
- The bottom line
Which systems make a pediatric support agreement longer than a general one?
A pediatric support agreement should name the systems a children's office depends on and say who is responsible for each: family records and guardian access in the practice software, the texting platform, forms and check-in tablets, the entertainment network, small sensors and handheld X-ray units, Medicaid and CHIP payer portals, and a change calendar built around school-break weeks.
General dental IT agreements list computers, server, network, backup, security and "support". A pediatric office runs every one of those plus a layer of tools that exist because the patient is a child and the person booking is a parent. The table below is the scope a pediatric owner should expect to see in writing. "Who owns it" says who fixes the thing itself; "IT's part" says what your IT company is responsible for around it.
| What a pediatric office runs | Why it is different from a general office | Who owns it | IT's part | In the agreement? |
|---|---|---|---|---|
| Family records and guardian access in the practice software (Dentrix, Eaglesoft, Open Dental, Archy) | One responsible party, several children, one payment; the person on the paperwork is not the person in the chair | The software vendor supports the program; the practice decides who sees what | User accounts, roles, workstation sign-in, removing access on a last day | Yes: account and role administration |
| Reminder, recall and two-way texting platform | Parents confirm by text for several children; a stopped text queue empties a school-break day | The texting vendor | The service or connector on the server, the internet link, the phone number plan, and finding which of the three broke | Yes: name the platform and the connector |
| Online intake and consent forms, check-in tablets | Guardians fill in forms on their phones or on a tablet in the waiting room | The forms vendor | The tablets themselves: enrolment, locked-down mode, updates, remote wipe, their place on the network | Yes: tablets as managed devices |
| Phones and call queues | Back-to-school and summer weeks bring the heaviest call volume | The phone vendor or carrier | The network the phones sit on, the switch ports and power, the failover internet, the integration with the practice software | Yes: phone network and integration |
| Open bays with chairside screens and sensor computers | Several chairs, screens and sensor computers share one room and one stretch of Wi-Fi | Equipment dealer for chairs and mounts | Wired drops per chair, access points sized for the device count, the clinical computers | Yes: per-bay network |
| Ceiling TVs, streaming boxes, kids' tablets, game stations | A screen that streams cartoons all day sits a few feet from the sensor workstation | The practice buys them | A separate entertainment network with content filtering and no route to the charts; firmware updates | Yes: entertainment network |
| Parent Wi-Fi | Every parent's phone joins the network during the busiest hour | – | Guest network with no route to clinical systems, a sign-in page, bandwidth limits | Yes: guest network |
| Small-format sensors and handheld X-ray units | Size 0 sensors, more USB connections at more chairs, charging and docking spots | The imaging vendor or dealer | Drivers, USB and hubs, the imaging bridge, image storage and its backup | Yes: imaging workstations and storage |
| Medicaid, CHIP and commercial payer portals | More portals and more logins at one desk than most general offices | Each payer | Per-person logins, multi-factor sign-in, a password manager, a list the practice owns | Yes: identity and access |
| Sedation and patient-monitoring equipment | Offices that offer sedation keep monitors in treatment rooms, and some models connect to the network | The medical equipment vendor | Only the network port or Wi-Fi segment it uses, kept apart from guest traffic; nothing clinical | Yes, as a network item only |
| Dolphin or another orthodontic system in a combined office | Two practice systems share one network, one imaging store and one support team | The orthodontic software vendor | Workstations that run both, both databases in the backup and restore test | Yes, if orthodontics is offered |
On the guardian row, the federal rule text sits in 45 CFR 164.502(g): a covered entity must "treat a personal representative as the individual for purposes of this subchapter", and paragraph (g)(3)(i) begins "If under applicable law a parent, guardian, or other person acting in loco parentis has authority to act on behalf of an individual who is an unemancipated minor". How that applies to a stepparent, a grandparent or a divorced parent in your state is a question for your compliance adviser. The IT company's job is narrower: make sure the roles your adviser and your software vendor set up are the ones each team member actually signs in with, and that nobody shares a login to get around them.
Two things in the table are often missing from agreements. First, the check-in tablets: the forms vendor runs the form, but somebody has to enrol, lock, update and, if one walks out of the building, wipe the tablet. Second, the entertainment network: TVs and streaming boxes are bought by the practice, installed by an audio-visual contractor and then belong to nobody. Put both in writing. If you are building a new office, the dental office network setup guide covers the drops, closet and Wi-Fi that make the per-bay rows possible. If your office also offers orthodontics, the companion piece on choosing an IT company for an orthodontic practice covers the second practice system and its imaging.
Which faults belong to the vendor, and which to the IT company?
A vendor answers for its own program or device; the IT company answers for everything that program runs on and reaches through. In a pediatric office most faults sit on that line: a texting queue that stops because a server service stopped, a tablet that dropped off Wi-Fi and cannot load forms, a sensor with no image after a Windows update.
The owner page has a short "who to call first" table by symptom. This one is by system, and it says what the IT company should already know about each one before the first ticket.
| System | The vendor's support covers | The IT company should own | What the IT company should know in advance |
|---|---|---|---|
| Practice software (Dentrix, Eaglesoft, Open Dental, Archy) | The program, its database engine, feature questions, the family and ledger modules | The server or cloud connection, Windows, the workstations, backups of the database, user accounts at the operating-system level | Open Dental's requirements page says "We recommend having a dedicated server to protect data" and lists Windows 10 as formerly supported with support suspended on October 14, 2025 |
| Reminders and two-way texting (Weave, Solutionreach, RevenueWell, Lighthouse 360, Open Dental eServices) | The messaging platform, templates, the texting number, delivery to carriers | The service that links the platform to the practice software, the machine it runs on, the internet connection | For Open Dental, the manual says the eConnector "is used by, and required, for all eServices" and to "Only install the eConnector on one machine". If that machine is off, every eService stops |
| Online forms and check-in (Yapi, Modento, Open Dental eClipboard, vendor forms) | The forms, their content, filing into the chart | The tablets as managed devices, their Wi-Fi segment, browser and app updates | Open Dental's manual says kiosks "can be a computer or Windows tablet, or a device running the eClipboard Feature": a Windows tablet is a workstation the IT company must patch |
| Phones and call queues | Handsets, the hosted phone platform, call routing, voicemail | Switch ports, power to the phones, quality on the network, the failover internet, the screen-pop integration with the practice software | Where the phones get power, and whether a failed switch takes the phones and the front desk down together |
| Sensors and handheld X-ray units (DEXIS, Carestream, Vatech, Planmeca) | The device, calibration, repairs, the imaging program | Drivers, USB ports and hubs at each chair, the imaging bridge, image storage and its backup, Windows updates that break drivers | Which Windows update ran the night before the sensor stopped |
| Screens and entertainment | The TV, streaming box or tablet | The entertainment network, its content filter, the rule that keeps it off the clinical network | How much bandwidth the bays use when every screen is streaming |
| Payer portals and clearinghouse | Enrolment, claim status, the portal itself | The browser, the sign-in device, multi-factor sign-in, the password manager, the owner list of accounts | Which portals the front desk uses, and who holds each account |
| Orthodontic system in a combined office (Dolphin) | The program and its imaging | Workstations that run both systems, both databases in the backup, the bridges between them | Which system owns the schedule, the ledger and the images |
If a vendor and your IT company both say "not ours", the IT company should still own the ticket until it is resolved, because only they can see the server, the network and the Windows logs at once. How these connections are built, and why they break, is the subject of the dental software integration guide; imaging faults have their own walkthrough on troubleshooting imaging integrations. A wider map of which party answers for each system in any dental office sits in the piece on dental office technical support.
How should a pediatric clinic day run when the IT side is done well?
In a pediatric office, good IT support is mostly invisible: systems are checked before the first family arrives, changes happen outside clinic hours and never in school-break weeks, the texting and forms connections are watched as closely as the server, and when something breaks mid-morning the IT company owns the ticket until a parent at the desk would not notice.
Here is a family-shaped day and what the IT company should be doing at each point. None of this is a response-time promise; it is a description of the work.
| Time of day | At the front desk and in the bay | Behind the scenes |
|---|---|---|
| Before the doors open | The team arrives, the first families are due in 30 minutes | Overnight monitoring has already checked that the server, the backup job, the eServices connector and the internet are up; a failed overnight update is known before the front desk finds it |
| First wave of check-ins | Three families arrive together, tablets out, phones ringing | Nothing is being changed. Tickets about a tablet, a slow screen or a payer portal go to someone who knows the office's layout and systems without being told |
| Mid-morning | Open bay full, sensors in use at every chair, TVs streaming | A sensor fault is treated as an imaging-workstation problem first (drivers, USB, the update that ran last night), then handed to the imaging vendor with the facts already gathered |
| Lunch | The only quiet hour | Small changes that cannot wait for the evening are made now, with the front desk told first |
| Afternoon | School lets out; the second wave | Texting delivery and the phone queue are watched; if confirmations stall, the IT company checks the connector, the internet and the practice software before anyone blames the vendor |
| Close | The last family leaves | Patching, firmware updates and reboots happen now, outside peak weeks, with a check in the morning |
The second half of good support is the calendar. A pediatric office cannot absorb a bad update during a school-break week, so the agreement should name the weeks in which nothing changes.
| Recurring duty | How often | What a pediatric owner should see |
|---|---|---|
| Windows and application patching | Monthly, outside clinic hours | A note of what was patched and a morning check; a change freeze on the weeks you give them (spring break, summer start, back-to-school, winter break) |
| Backup check and restore test | Backups watched daily; a restore of the practice database and the image store tested on a schedule you agree | A dated record of the last restore, with the method, for both the database and the images; a combined office includes the orthodontic database |
| Account review | Quarterly, and on every departure | Who holds each practice-software, payer-portal, texting and forms login; multi-factor sign-in on; shared logins replaced |
| Tablet and screen fleet check | Quarterly | Every tablet enrolled, updated and locked to its purpose; every TV and streaming box on the entertainment network |
| Operating-system lifecycle | Yearly | Windows 10 support ended on October 14, 2025 (Microsoft lifecycle page); a current list of any computer still running it and the plan to replace it |
| Network review | Yearly, and before any bay is added | Access points sized for the devices actually in each bay, the four-network split (clinical, staff, guest, entertainment) still in place, cabling tested |
When Wi-Fi in the bay drops every afternoon, the cause is usually one of the items in the last row; our guide on dental office Wi-Fi that keeps dropping walks through them.
How can you tell an IT company has never supported a children's office?
The clearest signs are an IT company that has never asked for your school-break calendar, treats the check-in tablets and waiting-room TVs as "not our equipment", lets the front desk share a payer-portal login, cannot say which machine runs your texting connector, and bounces a stalled text queue back to the vendor without looking.
Each sign below has a cost in a pediatric office and a question that tells you whether a provider will do better.
| Warning sign | What it costs a pediatric office | What a good answer sounds like |
|---|---|---|
| Updates run whenever the vendor releases them | A broken sensor driver or a rebooting server on the first morning of spring break | "Send us your district's break dates each year; nothing changes in those weeks unless you ask" |
| "The tablets are the forms vendor's problem" | A tablet that fails to load forms at check-in, or one that leaves the building with a saved session on it | "The tablets are managed devices: we enrol, update, lock and can wipe them" |
| "The TVs are on the office Wi-Fi, it's fine" | Streaming traffic competing with X-rays, and a consumer device one hop from patient data | "The screens live on their own network with a content filter and no route to the clinical side" |
| One shared login at the front desk for a payer portal | A locked account on a billing day, and no record of who did what | "Every person has their own login with multi-factor sign-in, kept in a password manager" |
| Nobody can say where the texting connector runs | A stalled queue on a 60-family day and three vendors blaming each other | "It runs on the server, it is monitored, and it is in our documentation" |
| Backups are "running" | A restore that has never been tried on the image store | "Our last restore test of the database and the images ran on this date" |
| The provider has never set up an open bay | Wi-Fi sized for a floor plan instead of twelve devices in one room | "Here is a bay we built: a drop per chair, access points for the device count" |
| The provider has one pediatric client, or none | Your office teaches them the specialty on your clock | Project pages or references from pediatric practices |
| Tickets are closed when the vendor is called | The problem is still yours | "We own the ticket until the fault is fixed, whoever fixes it" |
If three or more rows describe your current provider, work through how to choose a dental IT company, then compare the best dental IT companies, before you decide whether the fix is a conversation or a switch.
Can a pediatric office change IT companies and keep texting, forms and imaging working?
Switching IT companies in a pediatric office is a handoff of accounts and knowledge, not a change of phone number. Collect every administrator login the practice does not own, document which machine runs each connector, schedule the cut-over outside school-break weeks, and have the new company test texting, forms, imaging and phones before the old one leaves.
Most switches go wrong at the same place: an account the outgoing company set up in its own name. Start with the inventory, then follow the sequence.
| Account or asset | Why a pediatric office needs it in its own name | Where it usually hides |
|---|---|---|
| Domain name registrar and DNS | Email, the website and the patient portal links in reminder texts depend on it | Registered by the first IT company or the website designer |
| Microsoft 365 or Google Workspace global admin | Every staff mailbox and every multi-factor enrolment | Set up under the IT company's partner account |
| Firewall and switch administrator | The four-network split lives here; without it the new company rebuilds it blind | Only the outgoing technician's login exists |
| Wi-Fi controller | Guest, entertainment and clinical networks, and the access-point map for each bay | Cloud-managed under the IT company's account |
| Practice software vendor portal and database administrator password | Updates, support cases, the database itself | Known to one technician |
| Texting and reminders platform administrator | The texting number, templates, the connector's credentials | Created by whoever installed it |
| Forms and check-in platform administrator; tablet enrolment account | Tablets stop loading forms the day the management account is closed | The vendor's portal, under an IT email address |
| Imaging software administrator, sensor licences, dealer contacts | Re-pairing a sensor or moving the image store needs them | The imaging dealer and the outgoing IT company between them |
| Phone system administrator | Call queues, after-hours messages, the integration with the practice software | The phone vendor's portal, under an IT login |
| Payer-portal account owner list | Which person holds each Medicaid, CHIP and commercial login | Nowhere, which is the problem |
| Backup console and encryption keys | Without the keys the backups are unreadable | The outgoing company's console |
| Content filter and streaming accounts for the screens | The entertainment network's filter and the TV apps | Set up at install and forgotten |
| Documentation: network map, machine list, which computer runs each connector | The new company's first week depends on it | Often never written |
The sequence a pediatric office should expect from the incoming company:
- Weeks 1 to 2: discover and document. The new company inventories every computer, tablet, screen, network, connector and account against the table above, while the old agreement is still running. Nothing changes yet.
- Weeks 2 to 3: take ownership of accounts. Registrar, Microsoft 365 or Google Workspace, firewall, Wi-Fi, backup console, vendor portals and the texting and forms administrators move into accounts the practice owns, with the new company added as an administrator and the old one still present until the end.
- Week 3: pick the cut-over window. A weekday evening or a Saturday outside any school-break week, agreed with the front desk, with the texting vendor, forms vendor and imaging dealer told the date.
- Cut-over evening: monitoring and backups first. The new company's monitoring and backup agents go on; the first full backup runs, and a trial restore of the practice database plus the image store is completed, before anything else is touched.
- Cut-over evening: connectors and devices. The eServices or texting connector, the forms tablets, the sensor workstations and the phones are checked one by one against the inventory.
- Next clinic morning: live test with the front desk. A test reminder text to a staff phone, a form loaded on each tablet, an image captured at each bay, a call through the queue, a sign-in to each payer portal by the person who owns it.
- Week 4: remove the old company. Its administrator accounts are disabled everywhere on the inventory, the password manager is reviewed, and the final documentation is handed to the practice.
Contract and notice-period steps for any dental office are covered in the guide on a no-downtime switch of dental IT providers. Weighing a managed agreement against what you have now? The overview of managed IT services for dental practices sets out what a monthly plan covers and what is quoted separately.
How should your IT agreement change when you open a second pediatric office?
A second pediatric office should run on the same standard as the first: one practice software instance with clinics or one cloud tenant, one texting platform with a number per location, the same four-network split and per-bay design, the same tablet and screen build, and one IT company responsible for both, documented before the doors open.
The temptation is to let the second office grow its own habits: a different forms vendor because the new office manager prefers it, a consumer router for the TVs because the contractor had one, a second texting number nobody linked to the practice software. Each one becomes a support boundary nobody owns. Ask your IT company for three things before the lease is signed: a written room template from the first office (drops per chair, access points per bay, screens on the entertainment network), a decision on where the practice database lives for two sites (server at one office, a server at each, or cloud), and a plan for who in the new office holds which payer-portal and vendor logins. New offices follow the dental startup IT sequence from floor plan to day one; a group heading past its third office should read about DSO IT support, where standardisation becomes the main job.
What to ask your IT provider: questions for a children's practice
Put these to any IT company you are weighing up, Legend included, and ask for the answers in writing. They sit alongside the general 20 questions for any dental IT contract before signing; these are the pediatric ones.
About the scope
- Which of the systems in the scope table are named in your agreement, and which are "best effort"?
- Who manages the check-in tablets: enrolment, updates, locking and remote wipe?
- Is the entertainment network, including the content filter and the TV firmware, in your scope?
About the calendar
- Will you hold a change freeze on the weeks we give you each year, and what counts as an emergency exception?
- When do patches and reboots run, and who checks the office the next morning?
About connectors and vendors
- Which machine will run our texting or eServices connector, and is it monitored?
- When a vendor says "not ours", who owns the ticket and how do we see its status?
- Have you worked with our forms vendor, our texting platform and our imaging system before, and in which offices?
About access
- How will each team member get their own login to the practice software, payer portals and texting platform, and how fast is access removed on a last day?
- Where will the list of every account and its owner live, and will the practice hold the administrator passwords?
About recovery
- When would you run the first restore test of our database and our image store, and where will each result be recorded?
- If the server fails on a school-break Monday, what is the plan for the schedule, the texts and the phones that day?
About pediatric experience
- Which pediatric offices have you set up or supported, and can we see the project pages or speak to one?
- Have you built an open bay before, and how did you size the Wi-Fi for it?
What to verify before you sign
Answers are easy to give; these are the things to check.
- Pediatric offices they have actually built or supported. Ask for project pages, photographs or a reference from a children's practice, and look for open bays, screens and tablets in the work, not only servers.
- A written scope that names your systems. The practice software, the texting platform, the forms vendor, the imaging system and the phone system by name, with a column that says what the IT company does for each.
- A pricing structure you can read. What the monthly amount covers, what is quoted separately (hardware, cabling projects, software licences are the usual items), and how the price changes with chairs, tablets, networks and a second office.
- Account ownership in the contract. A clause that every administrator account is registered to the practice, and that all passwords and documentation are handed over on exit.
- A dated change-freeze clause. Your school-break weeks written into the agreement, not into an email.
- A signed business associate agreement before access is granted. Your compliance adviser confirms what each vendor and provider must sign; the IT company should expect to sign one.
- Exit terms. Notice period, what is handed over, and in what format, so a future switch follows the inventory above rather than a dispute.
- An onboarding plan around your calendar. Discovery, account transfer, cut-over and live test placed on dates that avoid your peak weeks, with the vendors named who will be told.
Which lines belong in a pediatric owner's monthly IT report?
The monthly report should let an owner see, without a technical reading, that the backups and restore tests ran, that every computer and tablet is patched and still supported, that the texting connector stayed up, which tickets came in and how they ended, who holds which account, and what changed on the network.
If the report is a count of "tickets closed", ask for these lines instead.
| In the report | Why the owner of a children's practice cares | When it is going well |
|---|---|---|
| Backup success by day, and the date and method of the last restore test | A pediatric office cannot rebuild a week of family records by hand | Every day accounted for; a restore of both the database and the image store inside the schedule you agreed |
| Patch status per computer and tablet, with the operating-system version | Tablets and bay computers are the ones that drift | No computer on an operating system past its vendor's end-of-support date, or a dated plan for each one that is |
| Uptime of the server, internet and the texting or eServices connector | The connector is the piece nobody else watches | Outages listed with cause and duration, not a percentage |
| Tickets by system (software, imaging, texting, forms, phones, network, accounts) with how each ended | Shows whether faults are bounced to vendors or resolved | Each ticket closed with a cause, including the ones a vendor fixed |
| Changes made and when | Confirms the change freeze was honoured | Nothing inside your named weeks except a logged emergency |
| Account changes: added, removed, multi-factor status | Staff turnover is high at the front desk | Every departure matched by a removal in the same month |
| Network and Wi-Fi notes per bay | Open bays degrade quietly as devices are added | Device counts per access point, and any bay flagged before it becomes a complaint |
| Open recommendations with a cost class | Lets you plan a bay, a tablet refresh or a server replacement | Items carried month to month until decided, not re-discovered in a crisis |
A provider that already produces these lines can show you a redacted example. One that cannot may still be a good technician, but you will be the one holding the picture together. Many of the lines map to the computers themselves: our guide on which computers to buy for a dental office covers the refresh decisions the patch-status line will raise.
Legend Networking and children's dental offices
A children's practice weighing Legend Networking is looking at a Dallas company with 22+ years in dental IT, having served over 3,500 practices since 2004. Its record also counts 1,500+ dental startup buildouts. Tickets go to in-house engineers; first-level triage is never outsourced. Calls to 1-800-794-1588 reach a helpdesk staffed 24/7, 24/7 monitoring watches the systems overnight, and onsite visits are dispatched by appointment in served dental markets while the rest of the work stays remote-first nationwide, from the Dallas headquarters and NOC.
For practice software, Legend supports the IT environment around Dentrix, Eaglesoft, Open Dental and Archy. For imaging, the list is DEXIS, Carestream, Vatech, Dolphin Imaging and Planmeca/Romexis. Each vendor keeps its own application or device. Legend's part is the computers, network, server, backups and accounts underneath, the same line the vendor-boundary table above draws.
The pediatric work is on Legend's own project pages. You can see a new pediatric practice in Illinois with technology installed and configured as it approached opening, a Florida pediatric startup whose documented scope covers network infrastructure, firewall protection, computers, wireless, surveillance and audio, a Texas pediatric practice opening whose project gallery shows the open treatment area and a Wisconsin pediatric practice's network, technology, video entertainment and ongoing support. The owner page lists every pediatric office on Legend's project pages by state, and the Dallas–Fort Worth examples of open bays and shared roofs are in our guide to specialty practice IT in Dallas–Fort Worth.
This guide comes from Ian Lynch, whose 22 years in dental IT sit behind his current job: overseeing Legend's NOC, onsite dispatch and client technology roadmaps for practices like the four above. Legend's 173 Google reviews average 4.8. To check what Legend covers where you practise, start at dental IT support in your city; for the national plan, read dental IT support.
Frequently asked questions
Which systems should a pediatric office's IT company look after?
It covers the computers, network, Wi-Fi, server or cloud connection, backups, security and user accounts a children's dental office runs on, plus the connections to the practice software, the reminder and texting platform, the forms and check-in tablets, the phones, the sensors and the screens. The vendors support their own applications and devices; the IT company supports everything they run on.
Does a pediatric dental office need a dental-specific IT company?
A general IT company can keep computers running, but a pediatric office depends on connections a general provider has rarely seen: the texting connector on the server, the imaging bridge at every chair, the forms tablets and the per-bay Wi-Fi. A dental-specific company arrives knowing those systems, so your team does not spend clinic hours teaching them.
Who fixes it when our reminder texts stop going out?
Three parties can be the cause: the texting vendor, the practice software and the connector or internet link between them. Your IT company should own the ticket first, because it can see the server service, the network and the Windows logs at once, then hand the vendor a fault with the facts already gathered rather than a guess.
Should the IT company or the forms vendor manage our check-in tablets?
The forms vendor runs the form and files it into the chart. The IT company should manage the tablet as a device: enrolment, a locked-down mode that shows only the check-in screen, updates, its place on the network and remote wipe if one leaves the building. Put that split in writing, because it is the item most often left to nobody.
How often should the restore of our backup be tested?
Agree a schedule with your IT company and ask for a dated record each time, covering both the practice database and the image store, and the orthodontic database in a combined office. A backup that has never been restored is an assumption. The owner should be able to read the last restore date in the monthly report without asking.
Who should hold the administrator logins for our texting, forms and payer portals?
The practice. Every administrator account for the texting platform, forms vendor, imaging software, phone system, firewall, Wi-Fi and Microsoft 365 or Google Workspace should be registered to the practice, and the IT company added to each as an administrator. Each payer-portal login belongs to a named person with multi-factor sign-in, recorded on a list the practice owns.
What is a realistic timeline for a children's office moving to a new IT company?
Plan about four weeks: two for discovery and documentation while the old agreement still runs, one to move accounts over to the practice and pick a cut-over evening outside school-break weeks, and one for the live test with the front desk and the removal of the old company's access. The cut-over itself is usually one evening and the next morning.
Does a pediatric dental office need a server, or can everything run in the cloud?
Both work. Cloud practice software removes the server but makes the internet connection and its failover the first item in the agreement; a server keeps imaging fast in the bay but needs a backup, a restore test and a replacement cycle. Open Dental's own requirements page says "We recommend having a dedicated server to protect data" for offices that run it on site.
Can our pediatric office still run Windows 10 computers?
Microsoft's lifecycle page says "Windows 10 will reach end of support on October 14, 2025", and Open Dental lists Windows 10 as formerly supported with support suspended on that date. A computer still on Windows 10 should appear in the patch-status line of your monthly report with a replacement plan, and no new tablet or bay computer should be bought with it.
What should a pediatric practice do before opening a second location?
Ask the IT company for a written room template from the first office, a decision on where the practice database lives for two sites, a texting number plan per location and a list of who in the new office will hold each payer-portal and vendor login. Bring the IT company in before the walls close, so the drops, access points and screens are planned per bay.
The bottom line
Bring the scope table, the warning-sign list and the account inventory to your current provider and to any company you are considering, and ask for written answers. If you would like a second reading of your own office first, ask Legend for a Free Dental IT Assessment, which returns a written set of findings, with prioritised recommendations, covering computers, software, network security, backups and performance. The specialty page on IT support for pediatric dental practices explains how Legend plans and supports these offices, and the national dental IT support page sets out what a plan covers. Call 1-800-794-1588 or book the assessment online.

