Skip to content
Docs home

OPERATIONS · UPDATED AUGUST 2026

Forms & Intake

Booking intake forms capture what a service requires, and routing forms direct customers to the right service path.

Booking intake

Every public booking runs through an intake form: the information a service requires is collected before the booking is created, and that information becomes part of the booking record. The form is the customer's first experience of the business's standards — required fields, validation, and the questions that actually matter to the appointment all live here.

Routing forms

Routing forms let a business front a single entry point and direct customers to the right service path based on their answers. Operators create and update routing forms, and submissions are processed against the tenant's services. Routing forms are a tenant-scoped object with the same storage and permission boundaries as bookings.

Ask once, store once

Intake answers are stored on the booking, not re-entered anywhere else. The staff view sees the customer context it needs; the customer is never asked twice for the same information.

STILL READING

Something here still feels worth checking together.

This documentation describes the product exactly as it is implemented. If a behavior you expected is not here — or is here and does not match your deployment — tell the team. Implementation questions start on the contact page.