← Back to library

Gate after-hours dental phone triage and booking

u/anassy1 describes six linked modules for one dental practice: a round-the-clock phone agent for new, moved and canceled appointments that alerts the dentist on Telegram for emergencies; call tagging by intent and sentiment; a patient CRM; Cal.com and Supabase booking sync; reminder calls; and follow-ups after visits, all run through n8n.

  • OutcomeCalls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/anassy1 on r/AiAutomations
View original
Works with
n8nElevenLabs AgentsChatGPTClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Your clinic misses calls during busy hours or after closing
  • No-shows and lapsed patients are a steady loss
  • You already keep the schedule in a system with an API

Not for: Clinical advice or triage beyond flagging an emergency; Practices whose privacy rules don't allow call recordings with the chosen vendors

What do you need, and what do you get?

You need

  • A voice agent platform and phone number
  • Your booking system or calendar with real availability
  • An emergency contact channel for the dentist
  • Patient records you are allowed to process

You get

  • Bookings, changes and cancellations synced to one schedule
  • Per-call intent, sentiment and one-line summaries
  • Next-day reminder calls and 90-day recall outreach

How does it work, step by step?

  1. Connect the real schedulePoint the voice agent at the booking system so it can only offer slots that exist.
  2. Define emergenciesList symptoms that mean alert the dentist now, and route those calls to a Telegram or SMS alert.
  3. Classify every callAfter each call, tag intent and sentiment and store a one-sentence summary in the patient record.
  4. Keep one patient recordMatch returning callers by phone and update them; create a profile for new ones.
  5. Remind and recallEach morning, call patients booked for tomorrow and mark them reminded; weekly, contact patients with no visit in 90 days.

The prompt

Our own prompt, inspired by u/anassy1 on r/AiAutomations and written to work in n8n, ElevenLabs Agents, ChatGPT and others. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
You answer calls for {clinic_name}. Available slots come only from this tool result: {availability}. Visit types and lengths: {visit_types}.
On each call: identify the caller by phone number, find out whether they want to book, change, cancel or ask a question, offer up to three real slots, and confirm the choice back to them. If the caller mentions any of {emergency_signs}, stop booking, tell them you're alerting the dentist, and send an alert with name, number and symptom. Never give medical advice. After the call, output intent, sentiment and a one-sentence summary.

Inspired by u/anassy1 on r/AiAutomations: I built a full AI automation system for a dental clinic.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Health data rules differ by country; check consent for recordings and which vendors may store transcripts.
  • Mark reminders as sent in the database immediately, or a retry can call the same patient twice.

Our take

What makes this build useful is that it treats the voice agent as one module among six rather than the whole product. The money in a dental practice is lost in unanswered calls, forgotten appointments and patients who drift away, and each of those has its own small, testable job here. Sync to the real booking system is the piece to get right first, since an agent that offers a slot that doesn't exist is worse than voicemail. The emergency path deserves equal care: write the trigger list with the dentist, test it with role-played calls, and make sure an alert reaches a person at night. The reminder and recall jobs are low risk and high value, and they work even if you keep a human on the phones. Before going live, check what your patients consent to, where recordings are stored and how long. Start with after-hours calls only, review transcripts weekly, and widen coverage once the logs look clean.

Where the time goes back: Missed calls, reminder calls and recall lists stop depending on how busy the front desk is.

FAQ

Does it replace the receptionist?
The author pitches it that way; we'd use it for overflow, after-hours calls and reminders, with staff owning exceptions.
What does the AI decide on its own?
Booking within available slots and classification. Emergencies go straight to the dentist.

Source and credit

Inspired by u/anassy1 on r/AiAutomations. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I built a full AI automation system for a dental clinic.
Creator
u/anassy1 on r/AiAutomations
Published on
Reddit
Original date
Mar 31, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Catch the emails your AI inbox assistant never processed

Run your AI email triage workflow as usual, label every message it handles, and add a second, independent workflow that once a day searches the inbox for recent mail without that label and sends you the list, alongside retries on the model steps and a production-status sign-in so the trigger does not silently expire.

Credit: Huzaifa_Aamish

Under an hour
Operations & AdminWorkflow✓ AI dry run

Confirm padel court times from a chat channel

Customers book, change or cancel courts by chatting, while a deterministic workflow assigns courts and prevents clashes.

Credit: u/PriceNew5674 on r/n8n

An afternoon+