The short version
Create a short form with clear questions, reveal sensitive or detailed follow-ups only when relevant, add the appropriate consent wording and attach the form to the service that should require it.
Plan the information you actually need
Every required field adds friction and creates information the studio must protect. Ask for data that changes how you deliver the service, meet a legal obligation or handle an emergency; leave curiosity out of the intake flow.
Use plain labels clients can answer without staff interpretation.
Make optional fields genuinely optional.
Use conditional follow-ups so irrelevant sensitive questions stay hidden.
Keep consent and waiver wording separate from ordinary profile questions.
Never request payment-card details in an intake form.
Build and attach the form
- 1
Open Forms and choose New form.
- 2
Add sections and fields in the order a client can understand them.
- 3
Configure required fields, help text and conditional rules.
- 4
Add the waiver or consent field with the exact wording your studio has approved.
- 5
Save the form and attach it to the relevant class, course or appointment service.
Test before requiring it
Preview the form as a client and test every conditional branch. Check error messages, long answers and the smallest phone size you support. Confirm that a completed response appears on the intended client record and is visible only to the roles that need it.
Answers before you get stuck
Can one intake form be used for several services?
Yes. Attach the same form wherever the questions and consent are genuinely identical. Create a separate form when a service needs materially different information.
Should every intake question be required?
No. Require only what is necessary to deliver the service safely or meet an obligation. Optional and conditional fields reduce friction and unnecessary data collection.
Did this guide solve the problem?
Make the change, or ask with your account attached
Open the relevant Junocal screen now. If your question depends on a particular client, payment or class, Juno can send it to the support inbox with the page and studio context included.