INTEGRATION · PLANNED
PostKnock + Dentrix
Dentrix runs the practice; PostKnock runs the lapsed-patient win-back. Native sync for inactive patients, treatment-plan reminders, and birthdays would replace the monthly CSV pull most offices already do by hand.
What Dentrix is
Dentrix is Henry Schein's flagship dental practice-management system. It owns the patient ledger, scheduling, charting, and insurance billing for tens of thousands of US dental offices. Most practices live in it all day.
Why postcards on top of Dentrix
Dentrix's built-in recall is calendar-bucketed and email-only. Email open rates for dental are stuck around 20%. Postcards land in the mailbox at 100% open rate, and a coordinated postcard + front-desk call reactivates patients that pure email recall has been chasing for two years. Dentrix handles the records; PostKnock handles the doormat.
How a PostKnock + Dentrix integration would work
Contact sync
Pull-based, scoped to lapsed-patient queries. PostKnock would query Dentrix's eCentral or G7 connector nightly for patients with last-visit-date older than your configured threshold (commonly 6, 12, or 24 months). Active recall, scheduled, and recently-seen patients are filtered out so you never card a patient who's already on the books. Direction is one-way (Dentrix → PostKnock) for the MVP. Two-way "appointment booked" feedback is on the roadmap.
Trigger types
- →Lapsed patient (>12 months) — Auto-enroll into the 3-wave reactivation playbook
- →Treatment plan unscheduled (90+ days) — Send a treatment-plan reminder postcard plus a follow-up call
- →Birthday month — Birthday postcard with a soft offer (free whitening with cleaning)
- →New patient welcome (first visit completed) — Thank-you postcard with referral ask
Data fields mapped
| Dentrix field | PostKnock field |
|---|---|
| Patient ID | External ID (preserved for dedupe) |
| First Name / Last Name | First / Last |
| Address (preferred) | Mailing address (validated against USPS) |
| Last Visit Date | Custom field: last_visit_date |
| Recall Type | Tag for segment filters |
| Provider | Custom field: provider (for personalization) |
| Birthday | Custom field: birthday (used by birthday triggers) |
Status
Planned. Build prioritization is driven by customer demand. The more votes a connector gets, the sooner we ship it.
Vote — tell us your use caseFAQ
Can I export from Dentrix manually today?▼
Yes. Use the Letter Merge or Patient Reports module to export inactive patients as CSV (Last Visit Date older than your threshold). PostKnock auto-maps standard column headers including First Name, Last Name, Address, City, State, Zip, and Last Visit Date — no template configuration needed. This is what almost every Dentrix office on PostKnock does today.
Will the native integration sync two-way?▼
MVP is one-way (Dentrix → PostKnock) so we don't have to write back to your patient ledger. A two-way mode that posts "Patient booked from postcard" back to Dentrix is on the roadmap, behind explicit opt-in.
What does the integration cost?▼
Nothing. Native integrations are included on every plan. You only pay the standard per-postcard price. There is no per-connector fee, no setup fee, no "integration tier."
Is this HIPAA-compliant?▼
PostKnock is built so postcard copy contains no PHI by default — the recipient name on the address side is the only identifier. We sign a BAA on Pro and above. Read our healthcare compliance approach for the full breakdown.
How do I cast a vote to prioritize this?▼
Email integrations@postknock.com with your use case (above), or click the Vote button on this page — the mailto link prefills the subject.
Use PostKnock today, native sync later
Export your contact list from Dentrix as CSV, upload to PostKnock, and ship a postcard wave this week. When the native integration goes live, your account is already set up.
Start Free