launching with Melbourne dental practices

Turn missed dental calls into booked appointments — not lost patients.

A managed AI receptionist that handles defined reception tasks using your approved answers, booking rules and handoff paths. Your team keeps the calls that need clinical knowledge, judgement or sensitive handling.

two-way audio · inbound and outbound
Live demo

Hear how the receptionist handles the boundary.

Book a fictional appointment, ask for a different time, then raise something outside the AI’s authority and hear the handoff response.

idle · line ready
--:--

A returned callback request for Harbour Dental, a fictional practice with synthetic availability.

+61
demonstration only · do not provide real patient or health information
Harbour Dental is a fictional practice · synthetic availability · the receptionist identifies itself as AI
How it works

Your rules define what happens on the call.

A patient is at reception. A clinician needs help. The phone rings during lunch or after closing. Taachi works both directions of the line — and when a request sits outside its authority, it follows the human fallback your practice approved.

  1. 01
    Callback queued
    Requests captured on earlier calls are queued with the context already recorded.
  2. 02
    Call placed
    Within operating hours you set, with the same AI disclosure at the opening.
  3. 03
    Rule-bound change
    Confirms or moves the appointment inside the agreed rules — no improvised commitments.
  4. 04
    Outcome passed
    The agreed outcome is passed through a scoped, tested system connection.
The receptionist can
  • 01Use business information you have approved.
  • 02Collect only the details needed for the agreed workflow.
  • 03Take permitted booking or administration actions.
  • 04Transfer or use an approved callback path.
  • 05Pass the agreed outcome through a scoped, tested system connection.
Your team controls
  • 01Appointment types and booking permissions.
  • 02Source information and policy answers.
  • 03Escalation contacts and operating hours.
  • 04Urgent, clinical and sensitive call paths.
  • 05Acceptance testing before production calls begin.
Capability

Give routine calls a defined next step.

It does not provide diagnosis or clinical advice. When a request sits outside its authority, it follows the human fallback your practice has approved.

Approved answers
Answers questions about hours, location, services and practice policies using the information you signed off.
signed off by your practice
Identifies the need
Works out what the caller is asking for before taking any action on the practice’s behalf.
Permitted bookings
Books or requests only the appointment types your practice allows, against agreed availability.
Rescheduling rules
Reschedules or cancels within the rules you define — notice periods, appointment types, clinicians.
Transfer or callback
Transfers the call or captures a callback request on the path your team approved.
No clinical advice
It does not diagnose or advise. Requests outside its authority follow the human fallback, every time.
Onboarding

Managed from workflow mapping through launch.

  1. Step 1
    Map the workflow
    Document common calls, approved answers, permissions and boundaries.
  2. Step 2
    Configure the receptionist
    Build the conversation and the permitted actions.
  3. Step 3
    Scope the connections
    Assess the required telephony, calendar or CRM actions.
  4. Step 4
    Test the difficult paths
    Including uncertainty, unavailable systems and requests for a person.
  5. Step 5
    Approve before launch
    Route production calls only after agreed acceptance checks.
  6. Step 6
    Manage changes
    Update the receptionist as approved business rules change.
Integrations

Connections are scoped, tested, then trusted.

Practice management, telephony and calendar systems are assessed case by case — the actions, access requirements and failure path are agreed before a single production call is routed.

Ask about your system
Practice management
Telephony
Calendar
CRM
SMS
Email
Reporting
Bookings
Case by case
FAQ

Questions practice owners and managers ask.

The intended opening identifies the receptionist as AI, names the practice and explains its administrative role. The final wording is approved before launch.

The workflow can clarify, then transfer or capture a callback request rather than guess. The retry and fallback path is tested for the practice.

No. Taachi is designed for defined reception and overflow tasks. People retain calls requiring clinical knowledge, judgement or sensitive handling.

An after-hours workflow can be configured with approved answers, booking permissions and fallback behaviour. It is not a promise of continuous service or human support.

Compatibility is confirmed only after the exact product, permissions, required actions and failure states have been assessed and tested.

Recording and transcription follow the approved configuration and consent process. Access, retention and deletion settings must be agreed before production use.

Practice manager · Melbourne
Every lunch hour the phone rings out and half those callers have already booked elsewhere.
Practice manager
Single-site dental practice, Melbourne

Illustrative scenarios from scoping conversations — not customer testimonials.

Test the call. Then map it to your practice.

Try a bounded dental scenario, or bring one real reception workflow to a 30-minute demonstration. We will review the approved actions, systems and human fallback without needing patient data.

Do not submit patient information, health information, passwords or system credentials.