Keep referring dentists in the loop.
Referral updates get buried between systems.
Est. deploy 4–6 weeksSee the walkthrough
Client Communication · Dental
Route post-visit questions to the right person.
Clinical questions get mixed with billing requests.
For: Patient services leads and the team responsible for client communication in dental.
01 · The outcome
What good looks like.
The team has a routed message with the original text and urgency flag, with source evidence and an explicit approval before any external action. Track time to qualified human review against a baseline; do not assume automation improves it.
A connected workflow that uses message, recent visit reference, and practice-approved escalation rules to classify administrative questions and flag symptoms for immediate human clinical triage. It produces a routed message with the original text and urgency flag.
Where AI helps, and where a person decides.
AI can classify administrative questions and flag symptoms for immediate human clinical triage. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The patient services lead verifies the source facts and approves the final action.
Patient services lead is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Patient services lead: Capture the source and scope
- Patient services lead: Review the proposed outcome
- Patient services lead: Release only the approved version
- Patient services lead: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A patient sends a post-visit message. Connect only message, recent visit reference, and practice-approved escalation rules. The patient services lead confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to classify administrative questions and flag symptoms for immediate human clinical triage. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a routed message with the original text and urgency flag against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Patient services lead has recorded approval or a reason to hold the item.
After explicit approval, save a routed message with the original text and urgency flag in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review time to qualified human review each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=dental-postvisit-questions
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- DENTAL-POSTVISIT-QUESTIO-DEMO-001
- Trigger
- A patient sends a post-visit message.
- Owner
- Patient services lead
- Prepared output
- a routed message with the original text and urgency flag
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Time to qualified human review
Start with your tools.
Connect Practice management system, Eligibility portal, Secure messaging through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
- For healthcare uses, validate HIPAA applicability, execute required BAAs, restrict PHI to the minimum necessary, and use approved secure systems. Clinicians handle symptoms, urgent care and clinical decisions.
Try this week / no DAVID required
A useful first step.
This week, have your patient services lead time five examples of this work. Use redacted copies of message, recent visit reference, and practice-approved escalation rules to make a routed message with the original text and urgency flag manually, then list which fields required judgment.
What to measure.
- Time to qualified human review
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Send the right approved visit instructions.
Patients receive instructions for the wrong visit type.
Est. deploy 4–6 weeksSee the walkthrough
Draft status updates from approved matter notes.
Clients ask for updates that staff must reconstruct.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 4–6 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.