Yes. It can answer routine after-hours calls using the practice's opening hours, callback rules and urgent-care message. Clinical emergencies and symptoms follow the escalation instructions supplied by the practice.
Yes, when the connected booking system and identity checks support the requested action. The receptionist should only confirm a booking or change after the system accepts it.
Yes, if those options and live availability are exposed by the connected system. AiDial can ask for the caller's preference and offer only the suitable times configured by the practice.
Yes. New patients can follow an intake and first-appointment process, while existing patients can use booking, change, recall or message workflows. Protected actions can include an identity check before any patient-specific information is discussed.
AiDial does not assess or diagnose symptoms. It follows the practice's urgent-call wording and transfers, records a priority message or directs the caller to the approved emergency pathway.
AiDial supports booking workflows including Cliniko and Amelia, plus calendar-based workflows such as Google Calendar. The exact booking action is verified against the practice's software and API access before launch.
Where SMS or another follow-up channel is configured, the receptionist can send an appointment confirmation or a link requested during the call. The practice approves the wording, recipient rules and consent basis.
Usually, AiDial can sit behind the existing clinic number through forwarding or routing during selected hours. A separate number can also be assessed for a campaign, after-hours service or dedicated queue.
No. It can provide practice-approved administrative information, manage suitable booking actions and take messages. Diagnosis, treatment guidance, medication questions and post-procedure concerns go to clinical staff.
Health information is sensitive information under Australian privacy law. The call flow should collect only the details needed for the booking, message or handover and document who may access retained call records.
The practice supplies the consent wording and decides what happens when a caller declines. The call can follow an approved alternative such as transfer, continue without recording or end the automated workflow.
Identity checks can be added where the connected system and practice rules support them. If the patient cannot be matched safely, the receptionist should take a message or transfer the call rather than change the booking.
AiDial can capture the requested appointment details, notify reception or offer a transfer. It should not claim that an appointment has been created, moved or cancelled until the booking system confirms the action.
Project-level redaction can mask supported contact details and identifiers such as Medicare numbers where the relevant patterns are configured and tested. The practice also chooses what is retained and how long it remains available.
Changes are supplied through the agreed update process and tested before use. This can cover new practitioners, appointment types, opening hours, fees, preparation instructions and escalation contacts.
No. It handles repetitive phone work and gives reception staff a clearer result to act on. Staff remain essential for patients at the desk, exceptions, clinical judgement and sensitive conversations.