For Dentrix.
AI workflows that keep the production-vs-collection loop clean.

It maps every app that touches the Dentrix core (Patient → Appointment → Insurance Plan → Treatment Plan → Ledger → Patient Communication) — QuickBooks Online / Xero for the nightly production-vs-collection handoff, Dentrix Pay (Stripe-tied) + Dentrix Exchange for the merchant-side deposit split, Demandforce / Solutionreach for the patient text cadence, Lighthouse 360 for the recall automation, the Patient Communication wizard on Ascend for the home-going message, and the Henry Schein One Tier ladder on-prem → Ascend → Enterprise / Voice → Pay + Exchange — to the moment in the Dentrix daily cadence it actually fires at. Trade-specific notes call out which Patient / Appointment / Insurance Plan / Treatment Plan triad to wire first (the Patient.Family + Patient.Individual pair, the Appointment status Planded / Completed / Unscheduled / Broken, the Insurance Plan line primary + secondary + plan-max + deductible-applied-to-date, the Treatment Plan case ID), how the Ledger production-vs-collection ladder layers on top of a Treatment Plan procedure line (the silent secondary-Insurance write-down drop and the unsigned-consent drift are the two Dentrix-specific traps), and what stays in a manual monthly entry because no integration does it well yet. The point is not 'here are the apps'; it is 'here is what each app actually writes to on the Dentrix side and where the operator needs to check the books after every sync.'

The morning Dentrix Patient / Appointment / Insurance Plan board prompt walks the front desk through a morning run — read the day's appointed Patients, confirm each Appointment has the Patient (matched to the household ledger, not the Patient 'nickname' the front desk defaults to), the Appointment slot (with operatory / hygienist / doctor cross-coverage), the Insurance Plan re-verification that the Eligibility check ran since the last visit and the deductible-applied-to-date is current, and the Treatment Plan case ID that ties the procedure line to the morning's planned work, batch-fire the morning Patient Communication text via Demandforce / Solutionreach (or the Ascend Patient Communication wizard on Ascend), and confirm the Lighthouse 360 recall pipeline is current on the prior evening's unconverted-Treatment-Plan cadence. The prompt also walks the front desk through the Insurance-Plan primary-vs-secondary trap — the Appointment that the front desk prepped against primary coverage but the Patient carries a secondary that pays after the primary is exhausted — so the morning Ledger production-vs-collection forecast is not silently under-billed. Designed for the morning the Dentrix practice wakes up to a 22-Appointment day and the front desk needs to ship the board in 20 minutes: what to confirm, what to batch-fire, and what to leave for the provider at the op.

The solo DDS on Dentrix on-prem rollout ships a four-step plan — week one on the Patient / Appointment / Insurance Plan / Treatment Plan triad that matters most (Patient.Family + Patient.Individual, Appointment status Planded / Completed / Unscheduled / Broken, Insurance Plan primary + secondary + deductible-applied-to-date, Treatment Plan case ID), day thirty on the Ledger production-vs-collection closeout enabled at the per-Appointment level with a clean Treatment Plan foundation, day sixty on the Dentrix Pay deposit reconciliation cabled to the nightly Ledger closeout, day ninety on the weekly unconverted-Treatment-Plan cadence via Lighthouse 360 (or the Patient Communication wizard once a Dentrix Ascend subscription lights up). The single-location group practice on Dentrix Ascend rolls out Ascend REST + Tier-aware API access on week one (Ascend REST enables Insurance-Plan Eligibility re-verification, Treatment Plan case-ID crosswalk, multi-provider Patient Communication templates), then layers in the Patient Communication wizard on Ascend, Lighthouse 360 recall automation, and the Dentrix Pay + Dentrix Exchange payout split reconciliation before the nightly Ledger production-vs-collection sync lands on day ninety. The multi-location DSO on the Henry Schein One ladder runs the rollout as a tier-aware adoption — Patient / Appointment / Insurance Plan / Treatment Plan / Ledger / Patient Communication across all locations, with the Enterprise / Voice tier providing the multi-location Patient Communication + Voice and the Pay + Exchange tier providing the multi-location Dentrix Pay payout reconciliation + Dentrix Exchange merchant-side fee routing per location — so each regional controller sees the right tier decision for their location. Same playbook family; the milestone shape is Dentrix-tier-specific to the practice size.

The partial-sync prompt runs the moment the operator opens Dentrix to the day's Ledger production-vs-collection closeouts — read the Dentrix sync log for the prior day, identify any Appointment where the sync shows 'Complete' on the Dentrix side but the corresponding Ledger row is missing the Insurance-Plan write-down (typically a secondary-Insurance write-down dropped mid-export while the primary-Insurance write-down landed cleanly, OR an Ascend REST write-up that never landed because the integration token expired and the connector fell back to read-only), post the missing Ledger row manually with the same Treatment Plan case ID and Patient identifier (so the nightly reconciliation script can match it), fire a one-line Patient Communication message to the Patient about the corrected Ledger line so the Patient is not surprised by an adjusted balance, flag the partial sync to the Dentrix support queue so the sync retires at the source, and post the same reconcile check the next morning as a recurring task until the partial sync resolves upstream. Trade-specific notes: a partial primary-Insurance vs partial secondary-Insurance write-down drop behaves differently per Dentrix tier — on-prem through the open-API outbound connector, Ascend on Essentials through the REST connector, Voice / Enterprise through the multi-location Audit-Table connector — so the operator sees the right rollback path for their tier.

Five, each with a one-page prompt the Dentrix operator runs the first Monday after close: (1) the partial-sync drop covered above; (2) treatment-plan-unsigned drift — the Treatment Plan was presented at the op-by-op handoff but the secondary signature step on the Patient Communication consent wizard never closed before the patient walked to the front desk, the Ledger wrote the production line as if consent was complete, and the front desk finds out a week after the patient left that the consent + signature never closed; (3) ERA / claim $0 payment + split-posting drift — the ERA from the carrier posted a $0 payment line and the Dentrix side wrote the production-vs-collection row as $0 on the Ledger while the Patient-side ledger still carries the carrier-reported contractual write-off; (4) Dentrix Pay + Dentrix Exchange split-fee drift — the merchant fee lands on the Dentrix Pay / Stripe side but the Ledger write-down carries the gross, so the nightly reconciliation picks up a phantom $0.30 per Ledger row and won't fully close at month-end; (5) cross-tier API-access gating — the integration a multi-location DSO depends on was authored against the Ascend REST contract but is now being shoehorned onto the Enterprise / Voice tier that gates differently, so the nightly Patient Communication push silently retires. Each prompt is a quick scan, not a full audit.

The multi-location DSO rollout ships as a tier-aware 30/60/90 with a QBO-side parallel — week one runs on the back-office / reporting side with the Enterprise / Voice tier so each location's controller inherits a common API-access surface, day thirty wires the per-location Patient Communication + Voice on the Enterprise / Voice tier while the QBO-side bookkeeper stands up the daily Ledgle handoff journal entry per location (or the multi-location Audit-Table connector on Voice / Enterprise lands the multi-location Ledger production-vs-collection sync, picking the right tier for the location's controller), day sixty layers in the per-location Patient / Appointment / Insurance Plan / Treatment Plan / Ledger / Patient Communication cadence on the multi-location Voice tier, day ninety lands the multi-location coordination pattern: Dentrix Pay + Dentrix Exchange reconciliation across all locations + the per-location Dentrix Exchange merchant-side fee routing on the Pay + Exchange tier + the multi-location Patient Communication cadence on the Enterprise / Voice tier. Same playbook family; the milestone map is multi-location-DSO-shaped so the per-location controller's daily Dentrix Patient / Appointment / Insurance Plan / Treatment Plan / Ledger cadence and the multi-location bookkeeper's nightly QBO production-vs-collection reconciliation stay aligned across all locations.