n-Acuity Scheduling's Intake Forms Collect the Details. What Happens to Them Next Is on You.
Acuity Scheduling lets you attach an intake form to any appointment type, built from text fields, multiple choice, checkboxes, and file uploads, and routes the completed answers to that appointment's details page for staff to read before the client arrives. Acuity also offers a HIPAA-compliant plan tier for businesses collecting health-style intake data, which requires a signed Business Associate Agreement and changes which features and integrations are allowed to touch that data.
What the intake form and HIPAA tier actually cover
Form fields staff actually see. Text, multiple choice, checkboxes, and file uploads cover most intake needs, attached to a specific appointment type so only the clients booking that service see the relevant questions.
Answers live on the appointment itself. There's no separate database of intake responses to browse. Staff opens the appointment in Acuity Scheduling to see what the client filled out.
A HIPAA tier with real restrictions. The HIPAA-compliant plan requires a signed BAA and limits which third-party integrations and video providers can be active alongside it, since any connected tool touching that data also needs to meet the same compliance bar.
Charting-adjacent, not a full EHR. Intake forms can collect a lot of clinical-style information, but Acuity Scheduling isn't an electronic health record, it's a scheduling tool with a form builder attached, so most businesses still run a separate system for actual charting.
Where intake answers get stuck
By default, every answer sits on the Acuity appointment page, nowhere else. Staff either reads it there directly or copies it by hand into whatever chart, CRM, or client-record system the business actually runs day to day, which gets old fast past a handful of appointments a day.
The HIPAA tier makes this harder, not easier, to automate the usual way. The exact general-purpose automation tools a business would normally reach for to move that data elsewhere are often the ones restricted or disabled to keep the account compliant. In practice, that's often where n-frames builds the connection through headless-browser automation instead, working through the interface the way a staff member would, rather than relying on a standard API integration that the compliance setup won't allow.
Where this tends to show up
Intake answers landed directly in the chart staff actually uses
Whatever a client fills out at booking shows up in the record system staff references during the appointment, instead of someone retyping it from the Acuity page beforehand.
Automation built to work within the HIPAA tier, not around it
A connection that respects the restrictions a signed BAA puts in place, built specifically for what the compliant plan allows, instead of forcing a choice between staying compliant and automating the handoff.
What does staff currently retype from an Acuity Scheduling intake form every day?
Tell us what it is and where it needs to land, and we'll work out what's realistic given your compliance setup.
Still copying Acuity Scheduling intake answers into your real client record by hand?
Intake forms collect the right information. Getting it into the system staff actually uses, especially on a HIPAA-compliant account where the usual shortcuts aren't available, is a different problem, and it's one we solve regularly. The same gap shows up with intake or form data on plenty of other tools too, not just Acuity Scheduling.
Let's talk