How to use a Righthand with Acuity Scheduling

Quick answer

Use Righthand to prepare an Acuity appointment-readiness list with status and intake completeness. A booking record alone may not contain everything staff need before service.

Start with a reviewable deliverable, keeping Acuity Scheduling as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Acuity documents appointment listing and distinguishes canceled appointments from no-show flags. See the official Acuity Scheduling reference. Provider capabilities and Righthand's available tools are separate checks.

Limit the packet to one service calendar and approved appointment types, including appointment IDs, duration, staff, and customer-supplied preferences. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: appointment ID, appointment type, calendar, start, timezone, canceled state, intake status. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Keep client details limited to the staff task. Rescheduling, charges, and appointment changes remain with the authorized scheduler.

Illustrative first-run brief

Use the owner-provided Acuity Scheduling snapshot or approved read-only view. Review the supplied next-day appointment list. Flag missing approved intake items and status inconsistencies. Prepare an internal checklist without contacting clients. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the scheduling lead to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

An appointment with missing intake appears as staff follow-up; a canceled record is not counted as an upcoming visit.

Match appointment ID and status to the calendar, checking no-show separately from cancellation. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

An export filtered by date may include canceled entries. Reconcile statuses before counting workload and do not rebook from an unclear record.

When canceled or no-show states are missing, preserve uncertainty and ask the scheduling owner to reconcile the appointment instead of drafting a routine reminder.

FAQ

What should the reviewer verify first?

Verify appointment ID, current status, source timezone, service duration, and approved contact preference. Cancellation and rescheduling are distinct states, not interchangeable labels.

How should a repeat run be scoped?

Keep appointment IDs, calendar identity, and cutoff fixed. Re-read state before each authorized reminder or change; a stale snapshot can retain a canceled booking.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.