Dental workflow automation · Practices & DSOs

Automate recurring checks.
Review the exceptions.

Run supported insurance checks and payment posting alongside your dental PMS. Keep each outcome and the record needing staff attention in view.

Available actions depend on the payer, PMS version and enabled setup. DentalXpand provides SaaS setup and training; your team reviews exceptions and makes professional decisions.

  • Scheduled billing tasks
  • Separate PMS outcomes
  • Provider hiring and support
What would you like to make easier?

Filter by the work your team handles, then open a workflow for its trigger, action, output and staff review. Scheduled tasks run once their connections are enabled; other tasks start with a staff member or candidate.

Five workflow types: what runs automatically?
Scheduled
Configured event or schedule starts the supported routine action, such as a PMS appointment or available remittance; staff handle exceptions.
User-started
Your team confirms the input and starts the action.
Assisted
Information is prepared for your team to check.
Connected
Keeps records and handoffs together. Coordination alone does not start an automatic action.
Self-service
A candidate starts the application.

01 / LESS BILLING BUSYWORK

Dental billing automation, with exceptions in view.

An appointment can start an insurance check; an available remittance can start retrieval and posting. The PMS updates depend on the connection and actions enabled for the practice. Xpand also submits secondary claims automatically through supported routes, using the primary response. It does not submit primary claims. Confirm the remittance source, enabled PMS actions, any required approvals and the secondary-submission route during setup.

Scheduled

Check returned benefits before the visit

Scheduled insurance verification and PMS updates.

Review missing or unclear returned benefits before estimating patient costs.

Confirm payer/PMS action scope for your setup.

View workflow details
Starts when
Patient scheduling triggers configured verification · Appointment in a supported connected PMS, patient and payer details
Xpand does
Checks supported insurance sources and updates enabled benefit fields, PDF and note outcomes.
Output
Returned benefits, enabled PMS fields, PDF and provider note
Staff reviews
Missing or unclear benefit details and separate failed outcomes.

Steps and setup scope

  1. A scheduled patient starts the configured workflow
  2. Xpand checks supported insurance sources and organizes returned benefits
  3. Enabled PMS benefit fields, breakdown-of-benefits PDF and short provider note are updated
  4. Missing or unclear details go to the appropriate reviewer; separate failed outcomes can be retried
  5. Optional user-started route: upload the Auto Verify queue and start Verify All

Sample output · Insurance verification

Benefits
Returned fields organized
PMS fields
Updated when enabled
PDF / note
Separate supported outcomes recorded
Exception
Missing frequency limit flagged for follow-up

Illustrative outcome record. Payer support, enrollment, identifiers and PMS/version action scope apply. Completed required actions are skipped; missing benefits need follow-up before estimates.

See benefits verification
Scheduled

Remittances without repeated downloading

Automatic ERA/EOB retrieval, matching and supported payment posting.

Review the match and posting results instead of repeatedly downloading the same remittance files.

Confirm payer/PMS action scope for your setup.

View workflow details
Starts when
Configured retrieval when remittance files are available · Available ERA/EOB from a configured connected insurance source
Xpand does
Retrieves available remittances, matches patient/claim and runs enabled payment, PDF and note actions. Confirm any required review or approval steps for the configured workflow.
Output
Matched patient/claim and separate enabled payment, PDF and note outcomes
Staff reviews
Unclear matches and each failed or incomplete write outcome.

Steps and setup scope

  1. Retrieve available ERA/EOB files from configured connected sources; optional single-file or bulk upload is also supported
  2. Match the remittance to the patient and claim and cross-check the details
  3. Complete enabled PMS payment, PDF attachment and note actions, skipping required actions already updated; confirm payment, PDF and note outcomes separately before retrying failed actions
  4. Flag unclear or unmatched records for the appropriate reviewer; retry failed outcomes separately

Sample output · Automatic ERA/EOB retrieval, matching and supported payment posting.

Match
Patient and claim identified
Payment
Enabled write outcome recorded
PDF / note
Separate outcome statuses recorded
Exception
Unclear match flagged; failed action retained for retry

Illustrative outcome record, not a customer result. Availability, enrollment and enabled payment/PDF/note actions vary by source, PMS version and practice setup. A retrieved document does not prove every write succeeded. Standard plans include unlimited supported payment posting with no extra posting fee; Custom terms are by agreement. View payment posting and plan details →

Explore payment posting
Scheduled

Secondary claim details kept together

Automatic secondary claims with the primary response in context.

Carry the primary response into automatic secondary claim submission.

Confirm payer/PMS action scope for your setup.

View workflow details
Starts when
Configured automatic secondary submission · Primary insurance response and the patient/claim details needed for secondary coverage
Xpand does
Submits the secondary claim automatically through the configured supported route.
Output
Secondary submission outcome and unresolved items for follow-up
Staff reviews
Missing details, payer errors and the secondary submission outcome. No primary submission.

Steps and setup scope

  1. Use the primary response and matching claim context
  2. Prepare the supported secondary claim with required details
  3. Xpand submits the secondary claim automatically through the configured supported route
  4. Keep missing details or returned errors with the claim for follow-up

Sample output · Automatic secondary claims with the primary response in context.

Primary response
Linked to the claim context
Scope
Automatic secondary submission only
Submission
Outcome retained for follow-up
Exception
Missing data or returned error needs attention

Illustrative workflow. Xpand submits secondary claims automatically; it does not submit primary claims. Payer requirements, enrollment, connection and enabled action scope apply. Confirm the enabled production route, required enrollment and returned submission outcome for your setup.

Explore secondary claim workflow
User-started

Stop rediscovering the same claim

Claim-status checks with the next action in view.

Help billers spend their attention on unresolved balances.

Confirm payer/PMS action scope for your setup.

View workflow details
Starts when
Start batch claim checks · Claims worklist with patient, payer and service date
Xpand does
Collects supported claim-status responses and prepares follow-up results.
Output
Returned statuses and an exportable follow-up report
Staff reviews
Payer messages, denied or unresolved balances and the assigned next action.

Steps and setup scope

  1. Import the claim worklist
  2. Collect supported payer responses
  3. Prioritize exceptions and export results

Sample output · Auto AR claim checks

Paid
Response available · review payment details
Denied
Payer reason returned · assign next action
Pending
Keep next check visible
Official ERA / EOB
Separate remittance connection and matching file required

A status PDF organizes the response; it is not an official carrier EOB.

Explore claim follow-up
Assisted

Less benefit-form retyping

Structured benefits forms with the source in view.

Reduce repeated copying while keeping the source in view.

Confirm payer/PMS action scope for your setup.

View workflow details
Starts when
Prepare the benefit form · Supplied or returned benefit information
Xpand does
Organizes supplied or returned benefit information into structured fields.
Output
Structured coverage, deductible and maximum fields
Staff reviews
Source accuracy and missing details before using the form.

Steps and setup scope

  1. Add the benefit source
  2. Prepare structured fields
  3. Check details before using the form

Sample output · VOB Auto-Fill

Eligibility
Recorded from source
Deductible
Source amount retained
Annual maximum
Source amount retained
Unreturned details
Left for follow-up

Form preparation organizes supplied information; it does not create a new payer response.

See benefit form workflow

Not every record ends with a complete answer.

Keep the exception and the next action visible, so your team knows where to spend its attention.

  • Missing benefit detailConfirm with the payer before using the estimate.
  • Unclear match or failed actionFlag the record for its reviewer; retry the separate failed payment, PDF or note outcome.
  • Denied or unresolved claimReview the reason and assign the next step.
Which output do I need: benefits, claim-status report or official ERA / EOB?

Breakdown of benefits

Organizes returned or supplied coverage, deductibles, maximums and limits. Missing details remain follow-up items.

Claim-status report

Organizes a returned status and payer message for your biller. Its PDF is not an official carrier EOB.

Official ERA / EOB

Retrieved automatically from configured supported remittance sources when files are available, or supplied through optional upload. Matching and enabled payment, PDF and note actions have separate outcomes. One ERA can cover multiple claims.

Explore claim follow-up and remittance →
Illustrative AR workspace with demo claim statuses, aging buckets and follow-up priorities
See status and the next action together.

Illustrative sample layout with fictional demo records. Review claim status, aging and follow-up priorities. Official ERA or EOB files still need a supported remittance connection and a matching file.

Explore claims and follow-up →
Illustrative Xpand AI operations brief showing a question, permitted workspace context and sources used
Keep operational questions in context.

Illustrative sample layout with demo data. The conversation shows the permitted workspace context and sources used. Available actions depend on your role and configured connections.

Explore Xpand AI and access →

02 / A STRONGER FIRST IMPRESSION

Provider hiring workflows, from application to agreement.

When a candidate moves from application to interview, offer and agreement, the recruiter needs the details already collected. These workflows link those records so each handoff starts with the candidate and practice information at hand.

Self-service

Applications scattered across inboxes

Career applications linked to the practice.

Review each application with its practice and candidate details together.

Team configuration and authorized review required.

View workflow details
Starts when
Candidate submits · Career form and practice opening
Xpand does
Links a submitted application to the provider and practice.
Output
Application linked to the provider and practice
Staff reviews
Application fit and the next hiring action.

Steps and setup scope

  1. Candidate completes the form
  2. Application enters the workspace
  3. Recruiter reviews the next step

Sample output · Public career applications

Role
Associate Dentist
Practice
Pinecrest
Application
Received
Next action
Recruiter review

The recruiting team reviews fit and decides what happens next.

Explore career applications
Assisted

Provider details entered again

NPPES lookup for public provider details.

Spend less time retyping public provider information.

Team configuration and authorized review required.

View workflow details
Starts when
Search, review and fill · Provider name or NPI
Xpand does
Looks up public registry details for a provider record.
Output
Registry details ready for your provider record
Staff reviews
The matching entry and separate identity, license and credential checks.

Steps and setup scope

  1. Search by name or NPI
  2. Review the matching registry entry
  3. Fill the provider details

Sample output · NPPES provider lookup

Source
Public NPPES registry
Details
Name, specialty and address
Match
Reviewed by your team
Next action
Continue provider checks

A registry lookup is not identity, license or credential verification.

See provider lookup
Connected

Hiring handoffs lose context

Hiring pipeline from application to onboarding.

Continue the hiring handoff with the application, current stage and next action on the same record.

Team configuration and authorized review required.

View workflow details
Starts when
Team advances the record · Application and hiring decisions
Xpand does
Keeps application, interview, offer and onboarding context together.
Output
Connected interview, offer and onboarding context
Staff reviews
Hiring decisions and stage changes, made by authorized staff.

Steps and setup scope

  1. Review the application
  2. Record interview and offer decisions
  3. Carry the agreement into onboarding

Sample output · Candidate pipeline handoff

Candidate
John Doe
Stage
Offer accepted
Next owner
Recruiting team
Next action
Prepare agreement

Hiring decisions and stage changes stay with authorized staff.

See the hiring journey
User-started

Interview details copied into emails

Interview invitations from saved details.

Keep the candidate and hiring team aligned on the next conversation.

Team configuration and authorized review required.

View workflow details
Starts when
Review and send · Saved interview and candidate contact
Xpand does
Sends the reviewed invitation through configured email.
Output
Interview invitation and email send record
Staff reviews
Recipients, interview details and message; a send record is not attendance.

Steps and setup scope

  1. Save the interview details
  2. Review recipients and message
  3. Send through configured email

Sample output · Interview invitations

Interview
Tuesday · 10:00 AM ET
Recipients
Candidate and hiring team
Delivery
Send record retained
Next action
Prepare for the interview

Delivery uses your configured email service; a send record is not proof of attendance.

Explore interview coordination
User-started

Offer updates without a clear version

Offer updates tied to the current version.

Review the saved offer terms before sending the candidate an update or reminder.

Team configuration and authorized review required.

View workflow details
Starts when
Review and send · Saved offer terms and candidate record
Xpand does
Sends a reviewed offer update or reminder using the saved version.
Output
Version-aware offer update or reminder
Staff reviews
Offer terms, recipient, version and candidate response.

Steps and setup scope

  1. Confirm saved offer terms
  2. Review the message and recipient
  3. Send the update or reminder

Sample output · Offer updates and reminders

Offer
Version 2
Recipient
Candidate on record
Message
Reviewed before send
Next action
Track the response

Your team confirms the terms and starts the message.

Explore offer communication
User-started

Chasing signatures across handoffs

Signed agreements ready for onboarding.

Keep onboarding connected to what was agreed.

Team configuration and authorized review required.

View workflow details
Starts when
Send for signature · Reviewed agreement and required recipients
Xpand does
Tracks required signatures and returns the completed packet.
Output
Completed packet after all required signatures
Staff reviews
Terms and every required signature, including countersignatures.

Steps and setup scope

  1. Review terms and send
  2. Track provider and required countersignatures
  3. Receive the completed packet

Sample output · Agreement signature workflow

Provider signature
Received
Practice countersignature
Received
Result
Signed PDF and completion certificate
Next owner
Practice onboarding lead

A provider signature alone is not completion when a countersignature is required. Connected signing service required.

See agreement handoff

Explore recruiting and onboarding for DSOs → · Search the public NPPES registry →

03 / SUPPORT THAT CONTINUES

Provider check-ins with a clear next step.

A check-in can reveal a concern, but someone still needs to act on it. Request provider feedback at scheduled checkpoints or between them, then record who will follow up and when.

Scheduled

Check-ins slip after the first day

Scheduled provider check-ins after the start date.

Give leaders a regular opportunity to hear concerns.

Team configuration and authorized review required.

View workflow details
Starts when
Runs at scheduled checkpoints · Confirmed start date and configured survey email
Xpand does
Sends configured survey invitations at scheduled checkpoints.
Output
Provider feedback available to authorized reviewers
Staff reviews
Response visibility, concerns and the follow-up decision.

Steps and setup scope

  1. Confirm the joining date
  2. Invite feedback at the scheduled checkpoints
  3. Review responses and decide follow-up

Sample output · Provider experience checkpoints

Cadence
2 weeks · 1, 3, 6 and 12 months
Invitation
Private survey link
Response
Available for authorized review
Next action
Leader decides follow-up

Scheduled invitations require enabled survey email and a confirmed start date. Explain the configured response visibility before requesting feedback.

See scheduled check-ins
User-started

A concern cannot wait for the calendar

Private provider feedback between checkpoints.

Help leaders listen between scheduled checkpoints.

Team configuration and authorized review required.

View workflow details
Starts when
Send a private check-in · Provider record and authorized leader
Xpand does
Sends an authorized private check-in and retains the response.
Output
Response available to the review team
Staff reviews
Configured visibility and the support needed; staff decide what follows.

Steps and setup scope

  1. Choose the provider
  2. Send the private survey link
  3. Review the response

Sample output · Manual provider surveys

Topics
Workload, support and practice fit
Invitation
Sent by an authorized leader
Response
Available to authorized reviewers
Next action
Review the support needed

A leader initiates the check-in and explains the configured response visibility. Authorized reviewers see responses within their assigned practice or organization scope; feedback is not an automatic employment decision.

Explore provider feedback
User-started

Lost candidates, unanswered questions

Candidate feedback after a declined application.

Give hiring teams better context for future conversations.

Team configuration and authorized review required.

View workflow details
Starts when
Request feedback · Declined or withdrawn application
Xpand does
Requests feedback linked to the declined or withdrawn application cycle.
Output
Structured reasons linked to the application cycle
Staff reviews
Reasons shared; the candidate may choose not to respond.

Steps and setup scope

  1. Record the application outcome
  2. Request feedback once per cycle
  3. Review the reasons shared

Sample output · Candidate decline feedback

Feedback
Schedule, location or compensation
Application
Linked to the same cycle
Owner
Recruiting team
Next action
Review the hiring approach

Feedback is requested; a candidate may choose not to respond.

Explore candidate feedback
Connected

Feedback that disappears in an inbox

Provider concerns with an owner and due date.

Record who will address the concern and when they should follow up.

Team configuration and authorized review required.

View workflow details
Starts when
Leadership reviews and assigns · Provider response needing attention
Xpand does
Records the responsible leader, agreed action and due date.
Output
Visible follow-up with an owner and due date
Staff reviews
The concern and actual follow-through; a survey does not resolve it.

Steps and setup scope

  1. Review the provider response
  2. Choose the responsible leader
  3. Record an action and due date

Sample output · Survey concern follow-up

Concern
Daily schedule support
Owner
Practice lead
Next action
Discuss the workload
Due date
Recorded by the team

The team assigns follow-up and confirms completion; the survey does not resolve concerns by itself.

See concern follow-up

Explore the provider check-in workflow →

Reduce repeated copying and checks.

Review what automation changes
and what still needs staff attention.

Look at where the repetition happens: checking each patient, copying claim responses or chasing signatures. The comparison below shows what changes when the relevant Xpand workflow is set up.

The same work. A clearer way through it.
Daily frictionWith a supported Xpand workflow
Repeat patient-by-patient checksRun configured checks from the patient schedule and organize returned benefits. Use Verify All for a loaded worklist when needed.
Copy claim updates into separate notesKeep the response, follow-up history and next action together.
Chase agreement progress in emailTrack required signatures and the completed packet.
Ask who owns a provider concernRecord the responsible person and due date.

Built around your practice

One team or many locations.
Start with the work that fits.

Pick a task and identify the staff who will use it. Before setup, we check your PMS version, payer support and the actions available for that practice. That gives the first rollout a defined scope.

01 / PRACTICE OWNER

Make room in the working day.

Bring repeat checks into organized worklists. Use recovered capacity for patients and issues that need your team’s judgment.

02 / DSO LEADER

Keep the practice context.

Coordinate organization and assigned-practice work while local teams keep their responsibilities in view.

03 / BILLING TEAM

See what needs the next action.

Return to the claim’s payer response, missing details and follow-up history when deciding what to check next. The record keeps that earlier work available.

Check the fit before the rollout

Your PMS. Your payers. A practical setup plan.

Find your insurance by name or payer ID. Check each service and enrollment requirement, then confirm your PMS version and available connection scope with our team.

Check my PMS & insurance →

Who does what?

  • Your team checks input, starts user-triggered runs and reviews results from configured verification workflows.
  • DentalXpand's team handles setup and trains your staff to use the enabled workflows.
  • Assigned staff review exceptions and own the next action.
  • Administrators manage Xpand practice and page access centrally.
PMS connections, verification automation and setup requirements

Verify All and Auto AR support loaded worklists. Xpand AI can start supported verification and claim-follow-up workflows. With verification automation configured, scheduling a patient in a supported connected PMS triggers verification, supported record updates, a breakdown-of-benefits PDF upload and a short provider note for review. Open Dental, Eaglesoft, Dentrix Core, Dentrix Enterprise, Dolphin and Dentrix Ascend integrations are live; confirm the available records, actions and refresh behavior for your setup. Other integrations remain in development.

Confirm provider identities, payer support, enrollment, plan allowances and service configuration. Email and signature workflows use connected services; access to outside accounts is managed separately.

Read the PMS and insurance workflow guide → · Connection requirements · Data handling

Setup and training for the agreed workflow.

We handle setup.
Your team learns the workflow.

DentalXpand assists with setup for the software and agreed practice connections. Training frequency, format and support ownership are confirmed in your written quote. Your staff review results and exceptions before adding more workflows.

SetupTeam-assisted onboarding
Support: Mon–Fri · 8 AM–6 PM Eastern Time
  1. Bring your starting point. Practices, software, payer mix and one priority workflow.
  2. We configure the workflow. Confirm inputs, permissions, connected services and expected outputs with our team.
  3. Train, review and expand. Work through results and exceptions before adding more.
Request a setup and training demo →
Dental workflow automation in Xpand: patient verification and returned benefit details
Patient context and benefit details together.Product preview: patient context and returned benefits in one view.Explore the insurance verification workflow →

For owners and the teams behind them

Dental workflow automation:
your questions, answered.

Understand what starts the work, what your team receives and what it takes to get going.

Explore your potential savings →
How can dental workflow automation help my practice save money?

Repeated checks and copying still take staff time, even when the biller’s decision stays the same. Dental workflow automation can free some of that time for patients and unresolved records. It becomes a cash saving only if you reduce actual spending, such as overtime, outside services or subscriptions. Use the savings calculator to compare your workload and staff costs with the plan and connected-service costs.

Which workflow should we automate first?

Choose a frequent task you can measure, such as eligibility checks or claim-status follow-up. Confirm the required input, connection and expected result, and name the person handling exceptions. Add another task after reviewing how the first one works.

Can we start verification for a whole patient list?

Yes. Once verification automation is set up, scheduling a patient in a supported connected PMS starts the check and the benefit-field, PDF and note actions enabled for that practice. For an uploaded list, staff can start Verify All in the Auto Verify queue. Xpand AI can also start supported checks for one patient or tomorrow’s patients. Claim-status checks use a separate loaded worklist in Auto AR. Required identifiers, payer support, enrollment and plan allowances still apply. Confirm the available actions for your PMS version before rollout.

Does automation replace our billers or make every decision?

Xpand is software your staff uses; DentalXpand handles setup and training. It can carry out repeat checks and prepare results, but billers still review missing benefits and denied or unresolved claims. Recruiters make hiring decisions, and leaders decide how to address provider concerns. Automation gives them less routine work to do around those decisions.

How do we check our payers and PMS before choosing a plan?

Search the payer directory by name or payer ID and review the services and enrollment requirements. Select your PMS, then confirm its version, required records and connection availability with our team. Clinical charting and scheduling remain in your existing PMS.

What happens when a payer response is missing or a claim is denied?

Keep that record in the follow-up queue. Review the returned reason or missing field and assign the next action to the right person. An automated check is not a guarantee of complete benefits, a successful appeal or payment.

Will a claim-status check also provide an official ERA or EOB?

A claim-status check returns a status and payer message, with a PDF that organizes the response. It does not replace an official carrier EOB. To retrieve official ERA data or payer EOB files, you need the separate supported remittance connection, any required enrollment and an available matching file. Xpand shows the outputs separately so a biller can tell which document is available.

Can a DSO coordinate work across multiple practices?

Xpand supports organization and assigned-practice workflows. Give staff the practices and pages their role requires, and keep owners and next steps visible. Automatic PMS collection, cross-practice batch launches and refresh timing must be confirmed for the supported connection before rollout.

Who helps train our staff and set up the workflow?

Our team assists with setup and onboarding. Training frequency, format and support ownership are confirmed in your written quote. Support is available Monday–Friday, 8:00 AM–6:00 PM Eastern Time. Bring your practice details, priority workflow and access requirements.

Can we start with one workflow and expand later?

Yes. Choose the workflow and plan capacity you need now, confirm setup and train the responsible team. Review results and exceptions before adding more workspaces or practices. Plan allowances, additional services and any capacity charges should be included in your cost comparison.

Let’s make it about your practice

See how Xpand fits
your practice's workflow.

For your demo, bring:

  • One priority workflow
  • Your practice count
  • Your PMS or payer questions

We'll demonstrate the software and explain the connections, setup and training your team would need.

A focused product walkthrough. No patient records needed.

Request an automation demo ↗

DentalXpand

YOUR TEAM. YOUR WORKSPACE.

Less scattered work. More room to grow.

Built around the way dental teams work.

DentalXpand

LET’S TALK ABOUT YOUR TEAM

Make room for better work.

Have a question or want a walkthrough? Tell us what your practice or DSO needs.

Required fields are marked with an asterisk.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Privacy policy