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.
No. AiDial does not currently have a direct Acuity Scheduling plugin. This draft records a possible future scope and must not be treated as an available integration.
The page is intentionally unpublished because provider authentication, booking actions, tenant boundaries and failure handling have not yet been implemented and tested in AiDial.
Setup would require an approved Acuity Scheduling account connection, mapped calendars and appointment types, scoped permissions, business rules and end-to-end testing.
No. AiDial cannot currently read Acuity availability or create, change or cancel Acuity appointments through a direct plugin.
The planned scope covers availability checks, appointment creation and approved appointment changes. Final actions will depend on the provider API and completed testing.
AiDial can transfer the call or arrange staff follow-up under the project rules, but it must not claim that an Acuity action was completed.
No future action should be enabled without scoped credentials, explicit project permissions and validation of the selected calendar, appointment type and caller details.
No. Internal identifiers, credentials and raw provider responses should remain private. Caller-facing responses should contain only the information needed for the approved workflow.
Identity requirements would be defined per action before launch. A booking reference or phone number alone would not automatically authorise every appointment change.
Only fields required for an approved appointment action would be exchanged. The exact data map and retention rules will be documented if the plugin is implemented.
No. Privacy, compliance and data-residency statements must be verified against the final architecture and Acuity configuration before the page is published.
AiDial's Australian-based team would scope, test and support the configured workflow after a direct plugin has been implemented.
Tell us which Acuity Scheduling records and call outcomes matter to your team. We can assess the API, permissions and implementation effort, but this draft page does not represent an available integration.
