Dental Office Internet Is Down: What to Check and Who to Call

When your dental office internet is down, the first useful question is not which box to restart. It is what has actually stopped working. A single operatory losing Wi-Fi, a cloud scheduling platform becoming unavailable and the entire practice losing outside connectivity can look similar from the front desk. They require different investigations.

This guide helps an office manager gather useful facts, reach the right support team and coordinate the practice while technicians investigate. It does not require administrator access or changes to the network. Use your practice’s existing downtime procedure for patient care decisions; the steps here concern technology and communication.

Start by identifying the scope of the outage

Describe the observation before deciding the cause. “All front-desk computers cannot open two unrelated websites” gives IT more useful information than “the router is broken.” Staff do not need to diagnose a firewall, DNS service or internet circuit. They need to report a consistent pattern.

Check with a colleague using another approved practice computer. Ask whether the same task fails there. If a second device works, note whether it uses a wired connection or Wi-Fi. Do not connect an unfamiliar personal device to the clinical network simply to conduct a test.

Compare the same task on more than one device

Use a normal, non-sensitive task such as loading the practice website or another familiar public page. A cached page can appear even when the connection is unavailable, so one successful page is not conclusive. Tell IT which tasks were tested and when. If the issue affects only one application, record its exact error and whether other online services remain available.

Microsoft’s Windows connectivity guidance distinguishes device, connection and application symptoms. In a managed dental environment, let your provider decide which corrective steps are appropriate; consumer reset instructions can alter settings that clinical systems rely on.

These are investigation paths, not diagnoses. Multiple faults can happen together. If imaging alone is affected, the dental imaging integration troubleshooting guide is a more relevant next read than continuing to treat the problem as an internet outage.

Check visible status without changing the environment

Look for simple observations your team can report safely. Does the workstation show a disconnected cable or unavailable wireless network? Is there a building power issue? Are network devices showing their usual lights? If equipment is in a locked or restricted room, leave access to an authorized person.

Record observations rather than improvising repairs. Avoid factory-reset buttons, moving cables between switch ports, changing Wi-Fi networks, disabling security software or rebooting a server. A change that restores browsing on one computer may disconnect a phone, interrupt an imaging transfer or remove evidence needed to understand the outage.

When a restart may be appropriate

A technician may ask an authorized staff member to restart a specific device. Confirm its label, what it supports, who is affected and the expected sequence first. “Restart the modem” is not enough when several similar boxes sit in a cabinet. Record the action and the time, then report whether the original symptom changed.

Server shutdowns deserve separate handling. The existing dental server shutdown guide explains why an office-wide restart should not become a default response to every connectivity problem.

Contact IT and the internet provider with one shared account of the incident

Use the outage channel agreed with your IT provider. If the normal web portal or office phone depends on the failed connection, use the documented alternative. An existing Legend client can find the client support entry point; a general assessment request is not a substitute for the support procedure in an active incident.

Tell the support team what is affected, when it began, whether patients are currently scheduled and who can be reached through a working channel. Do not wait for a perfect report before escalating an office-wide interruption. Send the initial facts, obtain a ticket reference, and add observations as they become available.

Decide who owns the ISP call

Your agreement may place internet service provider coordination with IT or with the practice. Confirm the owner rather than assuming both parties have called. The ISP may need the service address, account identification and an authorized contact. Share those through the appropriate support channel, not in a public discussion or unsecured worksheet.

Ask for the ISP’s incident reference and whether it has confirmed a wider service interruption. Record an estimated restoration time as an estimate, including when it was provided. Do not turn it into a promise to staff or patients. If IT and the ISP disagree about the cause, ask them to compare observations directly and identify the next test owner.

Response, updates and escalation expectations should come from your agreement. Our dental IT support SLA guide explains how those responsibilities differ from a guaranteed repair time.

Keep patient-hour communication coordinated

Choose one practice contact to maintain the incident log and share updates. Staff should report new symptoms to that person or the named ticket owner rather than open several disconnected tickets for the same outage. Individual patient-care decisions remain with the responsible clinical team.

Use a short internal update format: confirmed impact, what still works, current investigation owner and the next update checkpoint. Say “IT is investigating; no restoration time is confirmed” when that is the evidence. Silence often leads different teams to create incompatible workarounds.

Identify dependencies before promising normal service

Local practice-management functions might continue while online claims, payments, messaging or remote access fail. Other environments rely on an internet connection for most work. Phones may share the same connection. Even a locally hosted application can depend on an online login or integration.

Ask the team to list affected workflows, not just affected computers. Use the practice’s approved downtime process for any temporary recording and reconciliation. Do not export patient records to personal email, messaging apps or unmanaged storage to work around the outage.

Legend’s Dental IT Support service overview explains the relationship between workstations, software, imaging, networks and vendor coordination. That broader picture helps identify who should participate when a single outage crosses several systems.

Use a backup connection only if the practice has an approved plan

A secondary circuit or cellular connection may help, but its presence does not prove every workflow will function. Capacity, signal, routing, authentication and vendor restrictions can affect what is available. The practice should already know which systems the fallback connection is intended to support.

If an approved failover plan exists, ask IT to confirm whether it has activated and which tasks staff can use. Do not assume that attaching a personal hotspot to an operatory workstation reproduces the practice network. A temporary connection also needs the practice’s normal safeguards and technical approval.

For future prevention, use the Dental IT Failure Map to review single points of failure. The network design service page is the appropriate destination for discussing the design of resilient connectivity. Those planning tasks should follow the incident investigation rather than compete with it.

Verify recovery with a workflow checklist

An ISP reporting “service restored” is an important signal, but it is not the final practice test. Ask IT when staff can resume verification. Check the workflows that actually failed, including those that depend on third-party services.

Do not repeatedly submit a payment or claim just to test connectivity. The responsible application user or vendor should first establish whether the interrupted transaction completed. Reconcile any temporary records through the approved workflow so restored access does not leave a second administrative problem.

Keep intermittent issues open long enough to describe them

If the connection works briefly and then fails again, record each occurrence and the tasks affected. “Still intermittent at the front desk after the ISP restoration notice” is useful evidence. Ask the ticket owner what observation period or follow-up checks are appropriate; there is no universal duration that proves every environment stable.

Close the incident with one prevention decision

Request a concise closure record: confirmed cause if known, changes made, verification completed and any unresolved follow-up. If the cause remains uncertain, say so. A guessed root cause can lead the practice to buy equipment that does not address the actual failure.

Choose a specific next action with an owner. It might be testing an existing secondary connection, correcting an outdated ISP contact, documenting which phones depend on the circuit, or improving the outage communication process. Avoid turning the closure meeting into an unrelated technology shopping list.

For the broader support model behind these responsibilities, read the Dental IT Support Complete Guide. If you want Legend to review recurring connectivity disruptions, request a practice IT assessment with the incident history available. Keep patient details out of the initial request.

Put the outage checklist where staff can find it

An online guide is useful before an outage, but may be unreachable during one. Print the checklist below and keep the practice’s approved contact list with its downtime procedure. Review it when the ISP, phone system, IT provider or office manager changes.

The checklist is a record of observations and coordination. A checked item does not certify that the connection is safe or that every clinical system is ready. The support team and authorized practice staff still need to confirm recovery.