Phone Scams, Phishing and Ransomware: A Front-Desk Security Playbook for Columbus Dental Offices
At 7:40 a.m. the front-desk phone rings. A caller from "the IT company" needs someone to tap Approve on a login prompt. Minutes later, an email asks you to update a supplier's bank details before Friday's payment run.
That rule covers most of what this page sets out. For the services side, Legend Networking's page on dental IT support in Columbus describes what it offers locally, and the wider Columbus dental IT guide covers the region's utilities, growth and building questions. This phone-scam and phishing playbook for Columbus dental offices is narrower. It is for the office manager or front-desk lead in Westerville, Dublin, Gahanna or Grove City who has read about phone scams hitting Central Ohio healthcare and wants to know what the team should do differently on Monday.
It is calm and practical on purpose. You will find a table of the lures that reach a dental front desk, a callback script you can read aloud, a verification table, a first-hour card, a 12-month drill calendar and a short list of questions for your IT provider. For the national background on how ransomware and phishing reach dental practices, Legend's longer explainer is the place to go. Nothing here is legal advice.
Treat every request for a password, a login approval, a payment change or remote access as unverified until you hang up and call back on a number you already have on file. Turn on multifactor authentication for email and every portal, practise for 15 minutes each month, and keep a first-hour card at the desk.
- A large Central Ohio medical group's 2026 breach began with a phone scam; dental front desks face the same kind of call every day.
- Verify every request for logins, approvals, remote access or payment changes by calling back on a number already on file.
- Never approve a login prompt you did not start, and never read out a code.
- Turn on MFA for email first, then remote access, portals, banking and the domain registrar.
- Keep a printed first-hour card at every workstation and run a 15-minute drill each month.
- The office manager owns the habits; the IT provider owns the technology and reports in writing.
In this guide
- Why did phone scams become a Central Ohio healthcare story in 2026?
- What does a phone scam against a dental front desk sound like?
- How should staff verify a caller who says they are from IT or a vendor?
- What should a Columbus office do in the first hour after someone clicks or approves something?
- Where does multifactor authentication matter most in a dental office?
- How do you run a 15-minute monthly security drill at the front desk?
- What should a new front-desk hire learn in the first week?
- Is there anything Ohio-specific about protecting patient data?
- Does cyber insurance care about front-desk procedures?
- Who should own security habits in a small Columbus practice?
- How does Legend Networking fit into a front-desk security plan?
- What to ask your IT provider
- Key takeaways
- Sources
- Frequently asked questions
- The bottom line
Why did phone scams become a Central Ohio healthcare story in 2026?
Because a large local case started with a phone call. In October 2026 a large Central Ohio medical group reported that a phone scam in August 2026 had handed an outsider login credentials to its internal systems. For a dental office the lesson is about procedure: how staff check a caller before they act on a request.
Here is what the public reports say, without names. The medical group discovered on 25 August 2026 that someone had got into its systems. WSYX ABC6 reported in October 2026 that the group described the start as a social-engineering phone scam, sometimes called vishing (voice phishing: a scam carried out by phone call rather than email). Paubox, a healthcare email-security publisher, reported that the voice phishing attack let an unauthorised third party obtain credentials. The group did not say what was said on the call, and this page does not guess.
Two years earlier, in July 2024, a large local government in Central Ohio was hit by a ransomware attack that exposed personal information, SecurityWeek reported in November 2024. Ransomware is software that locks or steals an organisation's files and demands payment. That case is a reminder that large, well-staffed organisations in the region are targets too, and that the work of recovery lands on ordinary staff.
Neither event involved a dental practice, and neither tells us anything about who was at fault. They matter to a Powell or New Albany front desk for one reason: they show that the first step is often a person answering a phone or an email in good faith. A dental front desk does that all day. Callers are friendly, busy and in a hurry, and so are you. That is exactly the setting a scammer wants.
The good news is that the counter-measures are habits, not budgets. A callback rule, a login-approval rule, multifactor authentication and a short monthly drill cost staff time, not new hardware. The rest of this page turns them into steps.
What does a phone scam against a dental front desk sound like?
It usually sounds routine: someone from "IT", the software vendor, an insurance company, a supplier or a patient asks for a login, an approval, a change of bank details or a new email address on a record, and adds a reason to hurry. The red flag is the combination of an unusual request with time pressure and a reason not to check.
Every dental office has callers it trusts by habit. Scammers borrow those identities because the front desk is trained to be helpful. The table below lists the lures most likely to reach a Central Ohio dental office, what each one asks for, the giveaway, and the safe response. None of the lures names a real company; scammers can claim to be anyone.
Table A. Common lures at a dental front desk
| Lure | What they ask for | Red flag | Safe response |
|---|---|---|---|
| "IT support" caller | Approve a login prompt, read out a code, or install a remote-access tool | You did not report a problem; the caller is urgent; the number is not the one on file | "I'll call our IT company back on our usual number." Hang up and call it. |
| Practice-software vendor | Your username and password "to fix your account", or remote access | A vendor asking, unprompted, for your credentials is unusual | Call the vendor's support number from your contract or their website, not the caller's |
| Insurance-verification caller | Your login to a payer portal "to speed up eligibility" | A legitimate caller has no need for your portal password | Decline; offer to call the payer's provider line yourself |
| A "patient" changing contact details | Change the email or phone on a record, then send records or a reset link | Can't confirm date of birth and other details already on file; asks for records sent to a new address | Verify identity with details on file and call the number already in the chart |
| Supplier invoice or bank-detail change | Update the account a supplier is paid into | Email arrives close to a payment date; small changes in the sender address | Call the supplier on the number from a past invoice or contract before any change |
| Payroll direct-deposit change | Change an employee's bank account | Request comes by email, not in person; urgent before payday | Confirm face to face or by calling the employee on their known number |
| MFA fatigue prompts | Tap Approve on a login request | Prompts you did not start, sometimes many in a row | Deny every prompt you did not start, then tell your IT provider |
| Delivery or "account locked" texts | Click a link and sign in | A text to a work phone with a short link; urgency | Do not click; open the app or website you normally use instead |
Print this table and keep it near the front-desk phone. The safe responses all share one move: leave the channel the request arrived on and confirm through one you already trust.
How should staff verify a caller who says they are from IT or a vendor?
Hang up politely and call back on a number you already have, from your contract, a past invoice or the list at the front desk, never on a number the caller gives you. Never read out a login code or approve a prompt you did not start, and allow remote-access sessions only when your IT provider started them through a known channel.
The FBI's Internet Crime Complaint Center gives the same advice for payment changes in its September 2024 business email compromise notice: "Use secondary channels and/or two-factor authentication to verify requests for changes in account information." A callback to a number already on file is a secondary channel. It works for phone requests as well as email ones.
The hard part is not the rule. It is saying it to a confident caller. A script helps, because staff are reading a policy rather than refusing a person.
The callback script (read it aloud)
- "Thanks for calling. Our office policy is to call back on the number we have on file for any request about logins, payments or computer access."
- "Can I take your name and the company you're calling from?"
- "I'll hang up now and call the number we have for them."
- "I'm not able to approve a login prompt or read out a code over the phone."
- "If it's urgent, our office manager can call you once we've confirmed."
Then hang up, find the number on your list, and call it. If the request was real, the real company will know about it. If not, you have stopped the scam without an argument.
Your IT provider's helpdesk number should be written at the front desk, on the list next to the phone, so nobody has to search for it under pressure. For Legend clients, that number is 1-800-794-1588; the helpdesk is staffed 24/7 at that one general number.
What goes on the front-desk phone list?
The callback rule only works if the right numbers are already at the desk. Build the list once, from contracts, past invoices and vendor websites, never from an email signature or a caller ID, and keep a printed copy beside the phone as well as a digital one.
| Contact | Where to get the number | Why it is on the list |
|---|---|---|
| Your IT provider's helpdesk | Your service agreement or the provider's website | The first call for anything unusual on a computer, login or network |
| Practice-software vendor support | Your licence agreement or the vendor's website | To confirm whether a "vendor" caller is real |
| Imaging and sensor vendor support | Your purchase or service contract | Imaging callers asking for remote access are verified here |
| Phone and internet carriers | A recent bill | Fake "your line will be cut" calls are checked against the real account |
| Electric utility (AEP Ohio, Columbus Division of Power or Westerville's city utility, as shown on your bill) | Your bill | Fake "utility" calls asking for payment are checked against the real account |
| Bank and payroll provider | Your bank statement or payroll agreement | Payment and direct-deposit changes are confirmed here |
| Key suppliers and labs | Past invoices or contracts | Bank-detail changes are confirmed with a known contact |
| Practice owner and office manager | Staff records | Approvals for payment changes and first-hour reports |
Review the list every December as part of the drill calendar below, and whenever you change a vendor. Mark the date at the top so staff can see it is current. A list that is two vendors out of date sends staff back to searching online, which is where fake numbers wait.
Table C. Request type, how to verify, who approves
| Request | Verify how | Who approves |
|---|---|---|
| Approve a login prompt or read out a code | Do not. Only approve prompts you started yourself | Nobody approves for someone else |
| Remote access to a front-desk or operatory PC | Call your IT provider on the number on file and confirm they started the session | Office manager |
| Change a supplier's bank details | Call the supplier on a number from a past invoice or contract | Practice owner, in writing |
| Change an employee's direct deposit | Confirm with the employee in person or on their known number | Practice owner or payroll lead |
| Reset a staff member's password | Requested by the staff member through your IT provider's normal channel | Office manager |
| Change a patient's email or phone, then send records | Confirm identity from details on file; call the number already in the chart | Front-desk lead; office manager if records are sent |
| Share an insurance or lab portal login | Do not share. Each person uses their own login | Nobody |
| Install new software a caller recommends | Call your IT provider on the number on file | IT provider, after the office manager asks |
What should a Columbus office do in the first hour after someone clicks or approves something?
Unplug that computer from the network but leave it on, call your IT provider, change the affected password from a different device, write down the time and what happened, and tell the practice owner. Do not pay, reply or try to clean the computer yourself. Fast, honest reporting matters more than who made the mistake.
The first hour sets the tone for everything after it. People who fear blame hide mistakes, and hidden mistakes spread. Say this to the team in advance and mean it: reporting quickly is the right thing to do, every time.
The first-hour card (keep a printed copy at each workstation)
| Step | What to do | Why |
|---|---|---|
| 1. Disconnect | Unplug the network cable or turn off Wi-Fi on that computer. Do not power it off unless your IT provider tells you to | Stops spread, while keeping evidence your provider may need |
| 2. Call | Phone your IT provider on the number on the front-desk list | They can check other machines, accounts and backups |
| 3. Change the password | From a different, trusted device, change the password for the account involved, starting with email | Shuts the door if a password was given away |
| 4. Write it down | Time, what was clicked or approved, what the caller or email said, the caller's number | Your provider, insurer and advisors will ask for it |
| 5. Tell the owner | Let the practice owner know straight away | Decisions about patients, insurers and advisors are theirs |
| 6. Don't pay or reply | Do not reply to the email, call the caller back on their number, or pay anything | A reply tells the sender the address is live, and paying is no assurance that anything comes back |
Keep the card short enough to read in a panic. If something has already been encrypted, or screens show a ransom note, the next steps belong to your IT provider and advisors; Legend's guide to dental ransomware recovery explains what that process usually involves.
If you have never tested how your office would handle this, find out on a calm day, not during an incident. A Free Dental IT Assessment gives you an outside look at the office's computers, software, network security, backups and performance, with the findings written down in order of priority.
Where does multifactor authentication matter most in a dental office?
Start with email, then remote access, cloud practice-software portals, insurance and lab portals, online banking and your domain registrar. Use an app with number matching or a security key where you can, and treat any login prompt you did not start as an attack. CISA's guidance puts it simply: "Any MFA is better than none."
Multifactor authentication (MFA) means a login needs two or more proofs, usually a password and something on your phone. It is one of the habits that make a stolen password far less useful. The phone scam in Table A that asks you to "just tap Approve" exists because MFA works; the scammer needs you to finish the login for them.
Where to turn MFA on, in order
- Email (for most offices, Microsoft 365). Email resets every other password, so it comes first.
- Remote access. Any way staff or vendors reach office computers from outside.
- Cloud practice-software and imaging portals. If your system has a web login, protect it.
- Insurance and lab portals. Each person has their own login, with MFA where the portal offers it.
- Online banking and payroll. Payment changes should need a second proof as well as a callback.
- Domain registrar and DNS. Whoever controls your domain controls your email and website.
CISA ranks the methods, too. Its MFA page describes number matching (you "enter a number shown on the login screen to confirm") as a stronger option than a simple push prompt, and text or email codes as the weakest, to use "only if stronger options aren't available." Ask your IT provider which method each of your systems supports.
Passwords still matter alongside MFA. Legend's guide to password management for a dental office covers vaults and shared accounts, and its guide to HIPAA email for dental offices covers how patient information should travel by email. Your IT provider should be able to tell you, in writing, which of the six systems above already have MFA on.
How do you run a 15-minute monthly security drill at the front desk?
Pick one theme a month, spend five minutes showing a real-looking example, five minutes practising the callback script or the first-hour card aloud, and five minutes checking one setting or list. Fifteen minutes, once a month, at the start of a staff meeting, builds the reflex that a single annual training rarely does.
Short and regular beats long and rare. A new hygienist who joined in March and a front-desk temp covering in July both get the habit within weeks rather than waiting for the next annual training day.
Table E. A 12-month front-desk drill calendar for Columbus offices
The seasonal hooks are planning ideas tied to the Central Ohio calendar, not reports of real scams in those months.
| Month | Theme | 15-minute exercise | Seasonal hook (planning idea) |
|---|---|---|---|
| January | Remote logins | Check who can sign in from home and that MFA is on | Snow days, when billing staff may work remotely |
| February | Tax-form requests | Practise refusing an emailed request for staff W-2s or payroll files | Tax season |
| March | Callback script | Read the five-line script aloud in pairs | New-hire season after year-end turnover |
| April | Supplier bank changes | Walk through Table C's supplier row with a sample email | Quarterly supplier invoices |
| May | Login-approval prompts | Show what an unexpected prompt looks like; practise Deny | Spring software updates |
| June | "Utility" and "IT" callers | Role-play a caller claiming your power or internet will be cut | Summer storm season |
| July | Patient record changes | Practise verifying a "patient" who wants a new email on file | Summer schedule changes |
| August | The first-hour card | Read the card aloud; check printed copies are at every desk | Back-to-school staffing changes |
| September | Texts to work phones | Look at sample delivery and "account locked" texts | Busy autumn recall season |
| October | Insurance portals | Confirm each person has their own login and MFA | Open enrolment, when insurance calls rise |
| November | Payroll changes | Practise the direct-deposit rule | Year-end bonus and payroll changes |
| December | Review and reset | Update the front-desk phone list; note what worked over the past 12 months | Holiday cover and part-time staff |
Write the date and who attended on a single sheet. It takes seconds, and it is the kind of record insurers and advisors often ask to see.
What should a new front-desk hire learn in the first week?
In the first week, a new hire should learn the callback rule, the login-approval rule, where the first-hour card and the front-desk phone list are, how to report a mistake without fear, and their own logins with MFA set up. Shared logins and "just use mine for now" should never be part of onboarding.
Dental offices in fast-growing suburbs such as Powell, New Albany and Grove City often hire through the year, and temps cover holidays. Every new person is a new target, because a scammer counts on someone who does not yet know the office's habits. We have not measured turnover in Central Ohio dental offices; this is a planning point, not a statistic.
First-week security checklist for a new team member
- [ ] Own logins created for email, practice software and portals, with MFA set up on day one.
- [ ] Shown the callback script and Table C, and asked to read the script aloud once.
- [ ] Shown where the first-hour card and the front-desk phone list are kept.
- [ ] Told plainly that reporting a mistake quickly is expected and safe.
- [ ] Knows who the office's IT lead is and how to reach the IT provider.
- [ ] Added to the next monthly drill.
- [ ] On their last day, the office manager asks the IT provider to remove every login the same day.
Is there anything Ohio-specific about protecting patient data?
Ohio has its own data-breach notification law and a 2018 law (often called SB 220) that rewards businesses that follow a recognised cybersecurity framework; ask your attorney how either applies to your practice.
That is the whole of the Ohio pointer on this page, and it is deliberately short. HIPAA remains the baseline for a dental practice's safeguards, and the front-desk habits above are safeguards in the plainest sense. How a state law applies to a specific practice is a question for your attorney and compliance advisor, not for a blog post or an IT provider. For the safeguard side of the work, Legend's page on HIPAA safeguards and risk assessments describes its national offer.
Does cyber insurance care about front-desk procedures?
Often, yes. Many cyber insurance applications and renewals ask about MFA, staff security training and backups, and some ask how the office verifies payment changes. A dated drill log, a written callback rule and a list of systems with MFA turned on make those questions easier to answer accurately.
Read your own policy and application rather than relying on a summary; questions differ between insurers and change at renewal. Legend's guide to dental cyber insurance requirements explains the questions applications commonly include and how to prepare. Answer every question truthfully. If a control is not in place yet, tell your broker and put it on the list for the coming quarter.
Who should own security habits in a small Columbus practice?
The office manager owns the habits and the IT provider owns the technology. The office manager keeps the phone list, runs the monthly drill, handles new starters and leavers, and is the first call when something feels wrong. The IT provider sets up MFA, monitoring, backups and the technical response, and reports to the office manager in writing.
In a three-chair Gahanna office, this might be an hour a month. In a growing Dublin group, it may be part of a role description. Either way, writing it down keeps it from drifting.
A one-page security policy outline
- Callback rule. Requests for logins, approvals, remote access or payment changes are verified on a number already on file.
- Login-approval rule. Staff approve only prompts they started, and never read out a code.
- MFA list. The systems that have MFA, and the ones still to do.
- Front-desk phone list. IT provider, software vendors, imaging vendors, bank, payroll and key suppliers, with numbers from contracts.
- First-hour card. Printed at every workstation.
- Monthly drill. Theme, date and attendance recorded.
- Starters and leavers. Accounts created and removed on the right day, with the IT provider told in writing.
- Review date. The policy is reread once a year, with the drill log.
The IT side of that page is what you should expect from your provider. When you compare providers, ask each one how it supports these eight lines, and what it does when the office manager calls with a first-hour report. For the technology side of dental cybersecurity in Columbus, the city page sets out Legend's local offer, and Legend's national dental cybersecurity services page describes the services in more detail.
Security habits also connect to the rest of your IT plan. A managed plan with a monthly report shows whether MFA, backups and staff accounts are in order; the guide to managed IT for dental practices in Columbus covers what that report should contain. And the remote logins your team uses on snow days are part of the same picture, which the Columbus dental office power-outage and snow plan covers.
How does Legend Networking fit into a front-desk security plan?
Legend Networking is a dental IT provider headquartered in Dallas. Its published facts are: Served over 3,500 practices since 2004; 22+ years in dental IT (since 2004); In-house engineers; no outsourced first-level triage; Helpdesk staffed 24/7 at 1-800-794-1588; and 24/7 monitoring. Its reviews read 4.8 rating · 173 Google reviews.
Its leadership is listed as Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps. Legend's delivery model is "Onsite dispatch by appointment across served dental markets; remote-first nationwide." Day-to-day software and support issues are handled remotely; cabling, installations, equipment moves and new-office build-outs are scheduled onsite by appointment.
Its page on dental IT services in Columbus explains how it works with Central Ohio practices. For a front desk, the most useful of those facts is the simplest: one general number, staffed 24/7, which belongs on your phone list. Whatever provider you use, the playbook on this page works the same way.
What to ask your IT provider
Ask these questions in writing and keep the answers with your security policy:
- Do we have MFA on email and on every way into our office from outside? Which systems are still missing it?
- How will you contact us, so staff can tell your real calls from an impostor's?
- Will you ever ask us to approve a login prompt or read out a code? (The right answer is no.)
- What is our first-hour plan, and who do we call at 7:30 a.m. on a Monday?
- When did we last test a restore of our practice data, and what did it show?
- How do you remove a departing employee's access, and how fast after we tell you?
- Which login method does each of our systems use: number matching, a security key, or codes by text?
- What will you send us each month to show our accounts, MFA and backups are in order?
Key takeaways
- A large Central Ohio medical group's 2026 breach began with a phone scam; dental front desks face the same kind of call every day.
- Verify every request for logins, approvals, remote access or payment changes by calling back on a number already on file.
- Never approve a login prompt you did not start, and never read out a code.
- Turn on MFA for email first, then remote access, portals, banking and the domain registrar.
- Keep a printed first-hour card at every workstation and run a 15-minute drill each month.
- The office manager owns the habits; the IT provider owns the technology and reports in writing.
Sources
- WSYX ABC6, 15 October 2026, report on a Central Ohio medical group's cyberattack disclosure (accessed 2026-11-09).
- Paubox, 27 October 2026, report on the same disclosure (accessed 2026-11-09).
- SecurityWeek, 4 November 2024, report on a Central Ohio local government's ransomware notification (accessed 2026-11-09).
- FBI Internet Crime Complaint Center, Business Email Compromise public service announcement, 11 September 2024 (accessed 2026-11-09).
- CISA, Require Multifactor Authentication (accessed 2026-11-09).
- Legend Networking, Dental IT Support page: helpdesk, monitoring, engineers and reviews.
Frequently asked questions
What does a phone scam against a dental front desk usually sound like?
It usually sounds routine. A caller claims to be from your IT company, software vendor, an insurer, a supplier or a patient, and asks for a login, a code, a login approval, a bank-detail change or a new email on a record. The giveaway is an unusual request combined with urgency and a reason not to check through your normal contacts.
How should our front desk verify a caller who says they are from our IT company or software vendor?
Hang up politely and call back on a number you already have, from your contract, a past invoice or the front-desk phone list, never on a number the caller gives. Do not read out codes or approve login prompts you did not start, and allow remote access only when your IT provider confirms it started the session.
What should staff do when an email asks to change a supplier's bank details?
Make no change from the email. Call the supplier on a number from a past invoice or contract, not the one in the message, and confirm the request with someone you know. Have the practice owner approve the change in writing. Watch for small differences in the sender's address and requests timed just before a payment run.
Should a Columbus dental office use multifactor authentication for email and practice software?
Yes. Turn it on for email first, because email can reset other passwords, then for remote access, cloud practice-software and imaging portals, insurance and lab portals, banking and your domain registrar. Prefer an authenticator app with number matching or a security key over text-message codes, and deny any login prompt you did not start yourself.
What should we do in the first hour if someone clicked a phishing link?
Disconnect that computer from the network but leave it on, and call your IT provider. Change the affected password from a different device, starting with email. Write down the time, what was clicked and what the message said, then tell the practice owner. Do not reply, pay or try to clean the computer yourself.
How often should a dental office run phishing practice for staff?
A short monthly drill works better than one long annual session. Spend 15 minutes at a staff meeting: show a realistic example, practise the callback script or first-hour card aloud, and check one setting or list. Record the date and attendance. New hires and temps then pick up the habits within weeks of starting.
Why do attackers target small healthcare offices by phone?
Because a friendly, busy front desk is trained to help callers quickly, and a phone call skips the email filters that catch many scams. Small offices also tend to rely on a few people who know each other's routines, so a caller who sounds confident can seem plausible. A callback rule removes most of that advantage.
Does cyber insurance ask about front-desk verification steps?
Many applications ask about multifactor authentication, staff training and backups, and some ask how payment changes are verified. Questions vary by insurer and change at renewal, so read your own application. A written callback rule, a dated drill log and a list of systems with MFA make it easier to answer each question accurately.
Who should own security training in a small Columbus practice?
The office manager should own it, with support from the IT provider. The office manager runs the monthly drill, keeps the front-desk phone list and the first-hour card current, and handles starters and leavers. The IT provider sets up multifactor authentication and monitoring, and reports in writing. In a small practice this may take about an hour a month.
The bottom line
If you would like an outside view of where your office stands, request a Free Dental IT Assessment. You get written findings on your computers, software, network security, backups and performance, with prioritised recommendations, whether your practice is in Westerville, Dublin, Gahanna, Powell or downtown Columbus.

