Use the connected platform only for the actions, data and rules approved for your AiDial setup.
Complete supported tasks during the call and return a clear outcome without exposing internal platform identifiers.
Transfer the call or arrange follow-up when a request needs staff, permission or an action the integration does not support.
Yes. AiDial has a documented PracSuite integration for the supported actions described on this page. Each client connection is configured and tested for its own workflow.
AiDial maps the PracSuite business, practitioners, appointment types, availability channel and booking rules for the practice, then tests each enabled action.
The standard PracSuite workflow can create appointments, find an appointment for a verified patient and reschedule it. Reference-based cancel and other reference actions stay off unless the tenant explicitly approves them.
The standard PracSuite workflow can create appointments, find an appointment for a verified patient and reschedule it. Reference-based cancel and other reference actions stay off unless the tenant explicitly approves them.
PracSuite availability is exact-slot only. AiDial checks the requested date and time rather than presenting a general list or range of alternatives.
Cancellation is not part of the default PracSuite action set. Caller-supplied booking-reference actions require separate tenant permission and configuration. AiDial can transfer the call or arrange staff follow-up under the configured rules.
Existing appointments are matched with patient details such as phone, date of birth and name before a reschedule workflow can continue.
No. Provider IDs, credentials and raw API payloads stay internal. Caller-facing responses contain only the information needed to continue the approved workflow.
Existing appointments are matched with patient details such as phone, date of birth and name before a reschedule workflow can continue. A single identifier is not treated as blanket permission for other actions.
AiDial sends the patient and appointment fields needed for the supported action. The full transcript is not written to PracSuite, although approved booking custom fields may be mapped to the appointment note.
Cancellation is not part of the default PracSuite action set. Caller-supplied booking-reference actions require separate tenant permission and configuration.
AiDial’s Australian-based team maps the PracSuite workflow, tests the supported actions and helps maintain the approved configuration.
Tell us how your business uses PracSuite and which calls you want AiDial to handle. We will confirm the supported actions, setup work and testing required before launch.