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 Halaxy integration for the supported actions described on this page. Each client connection is configured and tested for its own workflow.
AiDial maps the Halaxy locations, practitioners, services and booking rules approved for your practice, then tests the full call flow before launch.
The configured connection can check availability and complete supported patient and appointment actions. The exact tools depend on the Halaxy workflow approved for the practice.
The configured connection can check availability and complete supported patient and appointment actions. The exact tools depend on the Halaxy workflow approved for the practice.
AiDial checks the availability exposed by the configured Halaxy booking workflow before it confirms a time with the caller.
The Halaxy connection does not add reminder campaigns, waitlists or automatic call-note writing. Those need separate supported workflows. AiDial can transfer the call or arrange staff follow-up under the configured rules.
Patient-facing reads and changes follow the identity checks and per-action rules configured for the practice. A caller is not given access simply because they know a booking detail.
No. Provider IDs, credentials and raw API payloads stay internal. Caller-facing responses contain only the information needed to continue the approved workflow.
Patient-facing reads and changes follow the identity checks and per-action rules configured for the practice. A caller is not given access simply because they know a booking detail. A single identifier is not treated as blanket permission for other actions.
AiDial sends only the patient and booking details needed for the supported Halaxy action. Internal identifiers are kept out of the spoken response.
The Halaxy connection does not add reminder campaigns, waitlists or automatic call-note writing. Those need separate supported workflows.
AiDial’s Australian-based team maps the Halaxy workflow, tests the supported actions and helps maintain the approved configuration.
Tell us how your practice uses Halaxy and which patient calls you want AiDial to handle. We’ll confirm the supported workflow, configuration and testing needed for your practice.