Dental Recall Automation

Business playbook — sell this after you finish From Village to Revenue.

Business problem

Hygiene chairs sit empty while overdue patients are never contacted consistently.

Current workflow

Front desk exports a list, maybe texts manually, drops the ball when busy.

Automation workflow

  1. Practice (or Zapier) sends overdue patient hash + slot time to your node.
  2. Node sends recall SMS (Live mode) or virtual SMS (Village mode).
  3. Patient replies C to confirm (your next iteration).

Node diagram

Zapier / PMS hook
    → POST /v1/execute + client key
    → Dual-Mode LIVE
    → SMS adapter (Twilio if production)
    → CONFIRM response + execution metadata

Village buyers hit the same URL with X-Payment-Proof and never touch Twilio.

Pricing idea

$250–400 / month per location + SMS pass-through, or bundled message allowance.

ROI

One recovered cleaning often exceeds a week of the retainer.

Demo script

  1. Show @dental_recall_bot on the Town Map.
  2. Unpaid curl → 402.
  3. Mock paid Village call → virtual SMS in logs.
  4. Live key call in sandbox → still virtual; explain production gate.

Proposal bullets

  • Scope: recall texts for overdue hygiene
  • Data: hashes / IDs only on Village; live path under BAA as needed
  • Dual-Mode safety: bots cannot burn SMS
  • Support: monthly report + key rotation

Next improvements

Confirm keyword handling, booking link, multi-location keys, CRM writeback.