These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Float / Sensory Tank Studio
- Implementation and migration
How a Float / Sensory Tank Studio rollout works
Start with one operating day that exercises booking, attendance and tank review.
Agree the operating rules
Studio Manager names the booking decision owner, member eligibility policy, tank review owner and receipt confirmation rule.
Map source records
Identify stable member, session, booking and tank numbers. Reconcile plan balances before importing enrollments.
Configure the pilot
Load a small service catalogue, staff identities, tanks, members and plan enrollments. Schedule a representative day.
Rehearse exceptions
Test a full session, a paused member, a repeated check-in, a failed tank check and a pending payment.
Review and release
Compare the resulting booking, attendance, entitlement, check and receipt records with the studio's expected day. The responsible staff approve the operating handoff.
What the customer provides
- Service durations, capacity and prices, plus the first session schedule.
- Member and enrollment identifiers, current statuses and remaining sessions.
- Staff user identities, tank register and sanitation review procedure.
- Booking cancellation, no-show, payment confirmation and refund policies.
Changing it afterwards
Use Proto to prepare a reviewed change to services, permissions or the operating flow. Check existing bookings and enrollments before changing a plan or service. Rehearse the ordinary and exception cases again, then release the new configuration with the manager’s decision.
Set up Float / Sensory Tank Studio your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.