Calendar & Scheduling · Listed — scope confirmed during implementation · Updated 2026-07-20
ClaireAI × Acuity Scheduling
Acuity validates availability and forms against the appointment type, so a firm needs to review the appointment, calendar, and data rules together before it uses a booking workflow.
What is the ClaireAI × Acuity Scheduling integration?
Acuity Scheduling's appointment API can create appointments, while its availability endpoints are used to find slots for an appointment type. By default, appointment creation validates availability and forms as though a client made the booking; administrative booking has a different validation path. ClaireAI's review identifies the firm-approved appointment type, calendar, staff or service context, duration, time zone, buffers, availability rule, and client-form fields that may be supplied. The firm decides whether it needs normal client validation or an explicitly approved administrative workflow, and who handles cancellation, rescheduling, payment, or a failed booking. This page does not promise that an appointment type accepts every field, bypasses a firm rule, sends a particular reminder, or represents a completed consultation. A labelled test against the intended Acuity configuration verifies available slots, validation, notification behavior, and staff recovery before live use.
Integration availability, setup, data flow, and implementation scope are confirmed with your firm during the sales and implementation process. Implementation work varies by firm.
Implementation review
What needs to be confirmed for Acuity Scheduling?
Evaluation path
How does ClaireAI evaluate a Acuity Scheduling workflow?
01
Match the actual appointment type
The firm ties the workflow to the Acuity service and calendar it already uses for the relevant kind of consultation.
02
Respect validation
Availability and form validation are left intact unless the firm deliberately approves a different supported process.
03
Exercise the exception path
A labelled booking and cancellation confirm the slot, data, notices, and the staff response if the request cannot be accepted.
Setup
How does Acuity Scheduling implementation start?
The implementation review confirms the vendor path, firm-approved data, and a controlled test before launch.
- 01
Document the Acuity appointment type, calendar, service or staff context, availability policy, and allowed data fields.
- 02
Confirm the booking-validation approach, notification and cancellation settings, account access, and exception owner.
- 03
Run labelled booking, rescheduling, and cancellation tests in the firm's configuration before launch.
FAQ
Acuity Scheduling integration questions, answered.
Can an Acuity workflow ignore availability or form rules?
Not by default. The firm must explicitly review and approve any supported administrative booking path.
Will every Acuity appointment send the same reminder?
Reminder and confirmation behavior comes from the firm's Acuity configuration and is verified during testing.
Can the workflow put all intake answers in Acuity?
Only firm-approved fields are included. The data boundary is defined before testing.
Related integrations
More in Calendar & Scheduling.
See Claire push a real call into Acuity Scheduling.
Book a 20-minute walkthrough. We'll run a live test call against your Acuity Scheduling sandbox.
Book a demo