DentalAI

AU-native dental operations

DentalAI keeps patient work moving around the PMS.

Booking, intake, reminders, recall, feedback, and staff follow-up workflows for independent Australian dental practices.

Book demoView pricing
  • Clinician approval remains required before patient-facing AI clinical content.
  • Go-live readiness keeps PMS, delivery, billing, and clinical signoff blockers explicit.
  • Public claims stay tied to published legal and security artefacts.
Recall queue
Hygiene gaps grouped for staff review
Ready
PMS connection
Vendor roundtrip remains a go-live gate
Blocked
Clinical approval
Draft content held until dentist signoff
Required

Operational scope

Designed for reception-heavy workflows clinics already run.

Patient lifecycle

Booking, intake, tablet check-in, reminders, feedback, recall, no-show follow-up, and appointment visibility.

Staff console

Protected dashboard, patient search, tasks, templates, settings, audit, and readiness checks for clinic teams.

Production gates

Tenant isolation, security headers, signed webhooks, MFA, billing activation, and provider smoke checks stay visible.

Pricing

Simple annual platform pricing for owner-led clinics.

DentalAI clinic platform

~AUD 25k

Indicative annual price for an independent Australian dental practice, subject to scope and go-live readiness.

What must be true before live use

  • Praktika vendor access: BLOCKED BY VENDOR ACCESS
  • Dental4Web vendor access: BLOCKED BY VENDOR ACCESS
  • Postmark live smoke credentials: BLOCKED BY CREDENTIALS
  • Clinical advisor recall signoff: BLOCKED BY SIGNOFF

Trust surface

Security and compliance overview

DentalAI is built around Australian-hosted deployment choices, tenant-scoped access, MFA for staff, auditability, signed patient links, and clinician-in-the-loop controls.

Current versions

  • privacy-policy-2026-05-06
  • collection-notice-2026-05-06
  • dpa-2026-05-06
  • ai-intended-use-2026-05-06
  • acceptable-use-2026-05-06

Legal pages

Privacy, collection notice, DPA, AI intended use, acceptable use, terms, and security overview pages are publicly visible.