Intake forms
An intake form collects answers as part of booking — not before it, not hopefully after it. Attach a Gather Grove Forms form to a class, a package, or a service, and nobody can complete that booking or purchase without answering your questions in the same sitting. Unlike an application gate, nothing is reviewed and nobody waits: the visitor answers, books, and is confirmed in one pass. You are simply guaranteed the answers before they arrive.
It’s built for the “I need to know a few things before we meet” pattern: a discovery call’s “what brings you here?”, a first-visit health questionnaire, a private session’s goals and history, dietary notes for a retreat package.
The Pro line, precisely. Intake forms are a Professional feature, and the form itself lives in Gather Grove Forms (1.10 or newer). Booking supplies the requirement and the enforcement; Forms supplies the form, the stored answers, and its entries screen. Without Forms active, an intake-required offering falls back to whichever behavior you chose in Settings → Booking — blocked (default) or open as if no intake were set — so a deactivated plugin never silently books something you meant to ask about first.
Application gate vs. intake form
The two look similar — both attach a form to an offering — and they solve different problems. Use both on the same offering if you need both.
- Application gate: decides who gets in. Answer → wait for approval → then book. For offerings where fit matters.
- Intake form: informs the session. Answer → booked, in one pass. Nobody is screened; the studio just always has the answers.
Setting it up
- Build the form in Forms as usual — any render mode, any fields. Include an email question if you want answers connectable to a person by address.
- On the class, package, or service edit screen, pick it under Intake Form (the rows sit just below the application-gate fields).
- Optionally set an Intake Page URL — a page of yours embedding the same form standalone. It’s the landing spot for flows that can’t show the form inline (see below), and a place you can link people to directly.
What the booker sees
The booking form, appointment picker, and package purchase window each grow a “Before you book” step carrying your form inline. The booker answers right there; a checkmark confirms the answers are in; the booking then completes normally. If they somehow reach the confirm button without answering (an old open tab, say), the server refuses politely and the step re-opens — answers first, always.
Guests are fully covered: no account is needed to answer or to book. And a logged-in client who already answered — say they filled in the form on your intake page earlier — isn’t asked twice: the step arrives pre-completed.
Fresh answers per booking
Each completed booking consumes its submission. Book the same discovery call again next month and you’ll be asked again — which is the point: “what brings you here now?” deserves a current answer. The submission is also recorded against the booking, so answers and appointments stay connected.
Where the requirement is enforced
Everywhere a booking or purchase can actually complete: class drop-ins, appointments, enrollments, package and membership purchases (including purchase-and-book), and the direct course-checkout links. A shared URL is not a side door — flows with no place to show the form inline redirect to your Intake Page URL instead, which is why setting one is recommended whenever a package or an enrollment class carries intake.
When the person isn’t at the keyboard
Walk-ins recorded by an instructor, admin manual bookings, gifted bookings, and automatic membership enrollments never block on intake — the attendee isn’t the one clicking. The booking goes through flagged “Intake pending” in its notes, so the front desk knows to collect the answers before or at the visit. (This mirrors how required waivers treat the same situations.)
Reading the answers
Submissions are ordinary Forms entries — read them in Forms → Entries, get them by email notification like any other form, and export them like any other form. The entry records which offering it was answered for.
Good to know
- One form can serve several offerings. Answers are matched to the offering they were filled in for, so a shared “new client questionnaire” on three services doesn’t let one service’s answers satisfy another’s.
- Failed payments don’t burn the answers. If the card declines or the seat fills, the submission stays valid for the retry.
- Keep intake forms short. It stands between the booker and a confirmed booking — three to five questions is the sweet spot; save the twenty-question deep dive for an application gate or a follow-up email.
Applies to Gather Grove Booking v1.278.2. Last synced November 11, 2026.