The best daily insurance verification routine is short and starts with your connections. Fix any broken insurance portal login first, then review what's ready, then rerun what failed. In FlexVerification, connection alerts tell you when a login breaks, and the Verification Report shows exactly what's waiting.
Here's something that's often learned the hard way at the front desk: when verification "stops working," it's almost never the software and almost never your team. It's a password that expired on a Tuesday, or an MFA code going to the phone of someone who left in the spring. Nobody notices until a patient is standing at the desk with a coverage question you can't answer. The fix isn't working harder. It's knowing sooner.
Broken insurance portal logins stop automated verification without warning. When a password expires or an MFA setting changes, checks for that payer fail quietly, and teams often find out when a patient is already at the front desk.
Falling back to phone calls is expensive. A manual dental eligibility check takes an average of 12 minutes per patient, according to the 2024 CAQH Index. One broken connection for a big payer on a busy day can turn into an afternoon on hold.
Insurance portal logins usually break for one of five reasons. Check these first:
If we could give every office one piece of advice, it would be this: never tie an insurance portal login to one person's cell phone. That single habit prevents more lost afternoons than any software can.
Connection alerts are FlexVerification's warnings that an insurance portal login needs attention. They show up in three places:
| Signal | Who sees it | Where |
| User Alert | Admins and staff with connection permission | Flex alerts |
| Orange dot and settings banner | Admins and staff with connection permission | FlexVerification settings |
| Connection indicator | All users | The patient profile |
That last one? It's the best one! The person checking in a patient is usually the first to need the answer, so they should be the first to know when the answer might be stale.
Admins and any staff member an admin gives permission to can fix a broken connection in FlexVerification. That permission is new, and it matters more than it sounds: in most offices I've worked with, one person "owns" the portal logins. When they're on vacation, broken connections just wait.
With the new user setup, staff members with that permission also receive the connection alerts. The people who run verification every day can keep their portals healthy themselves, so verification keeps running smoothly.
A good daily verification routine takes a few minutes each morning and follows the same order every day:
The order is the whole point. Connections first, because everything else depends on them. Review before rerun, because those patients are ready now. Do it at the same time every morning, before the phones get busy, and it stops feeling like a project.
The VerifySync Status column tells your team what to do next for each verification:
| Status | What it means | What to do |
| Review Now | The payer response is in and ready to review | Open VerifySync, compare side by side, inject the fields you choose |
| Rerun | The check should run again before you rely on it | Rerun the verification, after fixing any connection issue |
The column formerly called "Type" is now called "Eligibility."
Reviewing benefits first keeps your Open Dental data accurate. VerifySync shows what's in Open Dental next to what the payer returned, and only the fields your team selects are updated. You get the speed of automation and keep the judgment calls with the people who know your patients. For the full tour, see the new and improved FlexVerification.
What is a connection alert in FlexVerification?
A connection alert is a FlexVerification warning that an insurance portal login needs attention. Admins and staff with connection permission see a User Alert, an orange dot and a banner in settings, and every user sees an indicator on the patient profile, so the login can be fixed before verifications stop.
Who gets FlexVerification connection alerts?
Admins, and any staff member an admin gives permission to manage portal connections, get the User Alert and see the orange dot and banner in FlexVerification settings. All users see a connection indicator on the patient profile, so whoever is checking in a patient knows when an insurance portal connection needs attention.
Can non-admin staff fix a broken insurance portal login?
Yes, if an admin gives them permission to manage portal connections. With that permission they also receive connection alerts, so the staff who handle verification can fix broken logins themselves instead of waiting for an admin.
What should we do first when an insurance portal connection breaks?
Update the login in FlexVerification settings, checking for an expired password, MFA change, locked account or deactivated user. Then rerun any verifications that failed while the connection was down.
How often should a dental office check its verification queue?
Daily works for most offices. In FlexVerification, a daily Flex Alert tells your team when verifications are ready, and the Verification Report shows what needs review or a rerun.
What does Rerun mean in the FlexVerification Verification Report?
Rerun means the verification should run again before your team relies on it. Fix any related connection issue first, then rerun the check and review the result in VerifySync before injecting anything into Open Dental.
Verification doesn't go wrong all at once. It goes wrong quietly, one expired login at a time. Ten calm minutes every morning, with alerts that tell you what broke, is how front desks stay ahead instead of catching up.
Ready to see how FlexVerification can simplify your insurance verification? Book a Demo.