The problem

Dental practices lose staff hours every week to a repetitive, unavoidable task: calling insurance companies one by one to verify a patient's benefits before an appointment — and every practice that needs this has to solve it on its own.

The solution

Benji is now a full verification portal, not just a voice agent. Every patient is checked automatically first through a live insurance data connection, which resolves the most common fields — eligibility, deductibles, annual maximum, coverage percentages — in seconds, with no phone call at all. Only when that automatic check comes back incomplete does Benji place a real outbound call, navigate the insurer's phone system, and extract the rest. Staff see everything from a dashboard: verification status, where each result came from, one-click retry or escalate-to-call, and an activity overview — with each dental office scoped to see only its own patients, isolated at the database level. The same pipeline now closes the loop with the office's own practice management software: verified results, appointment data, and claim status write back directly into it, validated end-to-end against a live integration rather than just the portal. That write-back goes deeper than a status flag — deductible, annual maximum, coverage percentage by category, frequency limits, and, when a live call turns one up, waiting periods all get written into the practice management system's own benefit records, matched against its own category and code-group definitions rather than a separate list staff have to reconcile. For verifications that needed a phone call, the call's summary is saved right on that verification's own page in the portal, so the reasoning behind the numbers is easy to find later. Before a claim goes out, Benji also checks it against document requirements the office has confirmed with specific carriers — flagging a missing X-ray or other required attachment before submission, never after a rejection. When a payment comes back from the insurer, Benji shows staff exactly what to post per procedure and writes it into the practice management system once a human confirms the numbers — no re-typing an EOB line by line. And for a claim that goes quiet without a clean electronic response, Benji can place the same kind of disclosed phone call it already uses for eligibility, this time to check the claim's status directly with the payer. On the security side, every login requires two-factor authentication and every view or action on a patient's record is logged — access controls built in from day one, not bolted on afterward.

1. 01Automatic pre-check: every patient is checked instantly through a live insurance data connection before anything else happens.
2. 02Smart escalation: if the automatic check is incomplete, Benji places a real outbound call, navigates the insurer's phone system, and extracts the remaining details — no manual dialing.
3. 03Multi-office dashboard: each dental office logs into its own portal, sees only its own patients and verifications, and can retry or escalate any result with one click.
4. 04Activity overview: a Home view shows verification volume, status breakdown, and how often the automatic check alone was enough — at a glance, not buried in a spreadsheet.
5. 05Flexible patient data: offices without a connected practice-management system can add patients manually or upload a CSV — no API integration required to get started.
6. 06Practice-management write-back: verified results, appointment data, and claim status write directly into the office's own practice management software — not a separate list staff have to reconcile by hand.
7. 07Benefit detail write-back: deductible, annual maximum, coverage percentage by category, and frequency limits get written into the practice management system's own benefit records, matched against its own category definitions instead of a separate spreadsheet.
8. 08Waiting periods and call summaries: when a live call turns up a waiting period, it gets written the same way; for verifications that needed a call, the summary is saved right on that verification's page in the portal, so the reasoning stays easy to find.
9. 09Attachment intelligence: before a claim goes out, Benji checks it against carrier-specific document rules the office has confirmed itself, flagging what's missing before submission instead of after a rejection.
10. 10Payment posting: when an insurance payment arrives, Benji shows the exact per-procedure breakdown to post — staff confirm the numbers, then it's written straight into the practice management system.
11. 11Claim status follow-up: for a claim that doesn't get a clean electronic response, Benji can call the payer directly to check its status, the same disclosed-AI approach already used for eligibility.
12. 12Account security: every login requires two-factor authentication, and a full audit log tracks every view or action on patient data.

The result

Validated end-to-end on five fronts now: the voice pipeline was proven with a real, live insurer call; the automatic pre-check pipeline was proven with real API responses from the insurance data connection — 25 of the highest-value checklist fields (eligibility, deductibles, coverage percentages, and more) confirmed working with real data; the full write-through cycle into the practice management system — from eligibility, to a scheduled appointment, to a completed procedure, to a claim created and marked sent — was tested end-to-end against a live integration, not simulated; payment posting was proven the same way, with a real payment written into a live practice-management sandbox and confirmed on both sides; and the benefit-detail write-back — deductible, annual maximum, coverage percentage by category, frequency limits, and waiting periods — was proven the same way, matched against the practice management system's own category and code-group definitions rather than hardcoded guesses. The portal itself is live, with database-level isolation verified between separate dental offices, two-factor login and audit logging active for every account, and the first practice already logging in and using it.

The portal is live and in use by our first dental office client. What's still pending before real patient data flows through it: signed HIPAA business associate agreements with each data partner in the pipeline — standard, expected paperwork for any healthcare deployment, not a technical gap. Until then, the platform runs on realistic test data. One more thing worth saying upfront: Benji creates and marks claims as sent inside the practice management system, but doesn't yet guarantee electronic delivery to the payer — that still depends on each office's existing claims-submission setup, and we're not calling it solved until it's confirmed against a live account. And the benefit detail it writes back follows the practice management system's own broad categories, not a separate entry for every procedure code — waiting periods today only cover basic, major, and periodontal. It's built to save re-typing the common numbers, not to replace judgment on an edge case. One more limit worth naming: the call summary lives on the verification's own page in the portal today, not yet as a file inside the practice management system's own imaging module — that's on the roadmap, not shipped.