For multi-chair clinics · One patient · four coordinated handoffs
Keep busy chairs and teams working together.
Coordinate the doctor, chair and visit before the patient arrives. Carry notes, proposal stages, treatment, lab updates and payment questions through the team without repeating the handoff.
PATIENT THREADPatient 024Crown delivery · action needed
01Overlapping providers and chairs create schedule ambiguity
02Clinical and front-desk teams need different access to the same journey
03Lab, consent, billing and follow-up work can fall between role boundaries
What changes during your clinic day
ONE CLINIC DAY
Keep the handoff moving when every chair is busy.
Concurrent appointments, an urgent chair change, a shared assistant, a lab delivery and a proposal follow-up all touch the same patient journey during a busy clinic day.
×Overlapping providers and chairs create schedule ambiguity
×Clinical and front-desk teams need different access to the same journey
×Lab, consent, billing and follow-up work can fall between role boundaries
✓One selected clinic context
✓One connected patient journey
✓Explicit ownership for the next action
ONE PATIENT · FOUR HANDOFFS
See who does what during the clinic day.
Follow the booking, care and payment decisions through the people who handle them.
Front desk · resolve reschedule
Front desk checks the requested time against the doctor, chair and duration. A message does not change the booking until staff save the agreed visit.
PATIENT THREADPatient 024Crown delivery · action needed
Chair 02 · carry visit context
The assistant checks the assigned chair and lab case. A missing crown or consent is raised before the clinical handoff.
PATIENT THREADPatient 024Crown delivery · action needed
Clinician · record treatment
The dentist opens the patient's history and records findings and treatment for this visit. Other chairs continue in their own appointments.
PATIENT THREADPatient 024Crown delivery · action needed
Coordinator · own proposal follow-up
The treatment coordinator sees the proposal stage, records the patient response and owns the follow-up date. Proposal acceptance and clinical consent remain separate.
PATIENT THREADPatient 024Crown delivery · action needed
AI ACROSS A TEAM HANDOFF
Less chasing between roles.
Describe the appointment the team already agreed, then review the matched patient and fields together.
Explore AI Command“Book an appointment for Maya Sen on 22 September 2026 at 5 PM with Dr Asha Rao”
THIRTY2OS PREPARES
An editable appointment draft with the matched patient, doctor, clinic, time and duration.
Shared capacity
Plan the visit around both the provider and the chair
Appointments include doctor, chair, duration, treatment and status. Conflict checks help the front desk catch overlaps based on the information held in the schedule.
Clinic-configured chairs and appointment statuses keep the operating language aligned with the practice.
Clinical handoff
Give each visit a workspace, not a loose set of notes
The live appointment workspace supports structured clinical notes, tooth-level findings, attachments, procedure checklists and a finish plan. Sterilisation templates and logs can be configured by clinic and chair where that workflow is used.
Clear ownership
Give the treatment coordinator an explicit proposal handoff
Role permissions define who can see and manage each module. A treatment coordinator can own a patient-linked proposal, record Draft, Shared, Reviewed, Changes requested, Accepted, Treatment or Closed state, and set the next follow-up date without widening clinical access.
The action engine can surface follow-up across front desk, billing, clinical administration and labs without giving every user unrestricted access.
Front desk · clinician · billing
Give each role a clear handoff from consent to aftercare
The clinical team selects and reviews the procedure-specific consent document. Authorised staff share its secure link and check the signed state before relying on it. The lab case carries its due date, status and lab balance into the same patient context.
After care, billing shares the invoice through an eligible WhatsApp workflow while the visit’s clinic-approved post-op instructions are prepared and deliberately shared. Missing required steps can surface as source-linked actions; the queue does not send them automatically.
Rollout, responsibilities and clinic fit
ROLLOUT
Rehearse a busy hour with the whole team.
Coordinate the doctor, chair and visit before the patient arrives. Carry notes, proposal stages, treatment, lab updates and payment questions through the team without repeating the handoff.
- 01
Configure
Set up doctors, chairs, visit durations, roles and appointment statuses.
- 02
Rehearse
Run booking, live visit and treatment-coordinator handoff with real roles.
- 03
Extend
Add proposal stages, ownership, lab due dates and queue reviews to the team’s daily handoff.
PEOPLE · CHAIRS · LOCATIONS
Give each role the context it needs—and no assumed access beyond it.
Use this matrix as a discussion starter. The exact permission design must be reviewed against the clinic’s own responsibilities.
Schedule and arrival
Patient coordination
Billing and follow-up
Assigned visits
Clinical workspace
Treatment and consent context
Chair readiness
Authorised visit support
Lab and handoff status
Proposal stages and follow-up
Own the patient decision handoff
No assumed clinical-consent authority
Capacity and proposal review
Role governance
Exceptions and actions
FIT BOUNDARY
Know what still belongs to the clinic.
Conflict checks depend on complete schedule data and disciplined status use. Off-system bookings remain outside the product’s view.
IMPLEMENTATION CHECK
Make one patient journey reliable before adding more automation.
Thirty2OS connects recorded work and applies configured access. It cannot make incomplete source data, unclear ownership or off-system decisions automatically reliable.
MAP THE REAL CLINIC
Start with the clinic day you already run.
Create a workspace free for 14 days, or book a demo when you want help mapping people, chairs and locations.