Vapi / Implementation guide

Vapi hygiene reactivation for dental practice groups

Dental Practice Management Groups can use Vapi, n8n, an approved Claude model and Open Dental API to offer suitable hygiene appointments to eligible overdue patients. Appointment age alone does not determine clinical suitability. Recall interval, patient status, provider requirements, identity verification and privacy controls need explicit checks; do not invent discounts or disclose care details in voicemail.

Tools: Vapi; n8n, Claude 3.5 Sonnet, Open Dental API
01

The industry-specific problem

The hygiene book may have gaps while overdue patients remain buried in recall lists. Filling a 30-minute opening with a patient needing a longer periodontal visit does not solve the scheduling problem.

02

Step-by-step workflow

  1. Read permitted Open Dental API recall and schedule fields in n8n, excluding inactive patients and suppressed contacts.
  2. Match the appointment type, duration and provider constraints to a real available slot; do not use location proximity as the only criterion.
  3. Configure Vapi for authorized reactivation outreach and neutral voicemail. Verify identity before discussing patient-specific details.
  4. Use a supported Claude model to summarize availability preferences, not determine clinical recall intervals; replace the retired Claude 3.5 Sonnet ID.
  5. Recheck the slot, book through an approved Open Dental operation and apply only practice-approved offers compatible with your rules and payer contracts.
03

Visual workflow

Open Dental recall list → eligibility + contact gate → duration/provider matching
→ Vapi identity and availability → Claude preference summary → slot recheck → booking
04

Specific configuration example

This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.

// n8n Code node: match hygiene capacity, not just an empty slot
const patient = $json;
const slots = (patient.slots ?? []).filter(s =>
  s.minutes >= patient.required_minutes &&
  s.provider_ids.includes(patient.required_provider_id));
return [{ json: {
  patientRef: patient.patient_ref,
  offerSlotIds: patient.contact_authorized && patient.recall_verified
    ? slots.map(s => s.id) : [],
  voicemailPolicy: "callback_only_no_treatment_details",
  discountAllowed: patient.practice_offer_approved === true
} }];
05

Outcome to measure

Illustrative planning metrics only. Not verified client results.

Monitor completed hygiene visits, chair utilization and inappropriate appointment types. Illustrative: eight recovered 45-minute visits fills six chair hours before no-shows and cancellations; use your actual reimbursement to model value.

06

Compared with manual work or other tools

Recall texts are inexpensive and may be sufficient for responsive patients. Voice can resolve timing objections, while staff must retain clinical eligibility and sensitive conversations.

07

Work with Imperio Automation

Ask Imperio to build an Open Dental recall workflow that respects appointment types and patient privacy.

Scope this workflow
08

Frequently asked questions

Can it offer a cleaning to every overdue patient?

No. The verified recall type, clinical instructions and visit duration control eligibility.

Can it leave a detailed periodontal reminder on voicemail?

Use the practice’s approved neutral-message policy and privacy controls.

Can discounts be generated dynamically?

Only from approved offers after checking applicable practice, payer and legal restrictions.

09

Technical and regulatory references