Quick answer
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.
Before you begin
A documented reason for every question and agreement from the studio on who may view the answers.
Approved consent or waiver wording reviewed for the studio's own services and jurisdiction.
The classes, courses or appointments that should require the form identified before attachment.
You'll know it worked when
Required, optional and conditional fields behave correctly for every tested answer path.
The client sees the form at the intended point and can complete it comfortably on mobile.
The completed response attaches to the correct client and service context.
Only roles that need the information can access it, and no card data or unnecessary sensitive detail is collected.
Follow along in Junocal
Open the exact product area, then keep this guide beside 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.
Troubleshooting
Start with the symptom that matches what you can see. Check the existing record before repeating a booking, payment or import.
The form is published but clients are not asked to complete it
Check these first
Confirm the form is attached to the exact class, course or appointment they are booking.
Check whether the client already has a valid completion that satisfies the service requirement.
Next step: Attach the form to the intended service and test with a new client state before changing existing completed responses.
A conditional follow-up never appears
Check these first
Review the source question, comparison value and whether the answer format matches the condition.
Test both the revealing and non-revealing branches in Preview after saving.
Next step: Correct the condition and retest every branch, including returning to change an earlier answer.
Staff cannot find a submitted response
Check these first
Open the client's profile and the related booking rather than searching for a detached form submission.
Confirm the staff role is authorised to view form data and that the client used the expected email identity.
Next step: Locate the correct client or booking context and adjust access only if the role genuinely needs it. Do not duplicate the form to make the answer visible.
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.