Use live records
Begin with the current client, class, plan, payment, product, message, or studio state.
Client management
Put acceptance before the first booking.
Require clients to accept your studio’s waiver before their first booking.
- 1,284clients
- 642active 30 days
- Today 71check-ins
Illustrative studio data shown
A profile should reveal the person
Keep the useful context close to every interaction.
Bookings, attendance, payments, plans, notes, tags, and contact details form a much clearer picture when they stay with one client record.
Require clients to accept your studio’s waiver before their first booking. The product detail matters because it supports a real member, staff member, and studio moment.
Why it matters
One feature. Three connected outcomes.
Require clients to accept your studio’s waiver before their first booking. Clovo keeps the surrounding context available before, during, and after the action.
For members
- A shorter pathThe intended action stays clear and close to the live studio experience.
- One accountWhere members are involved, the result stays attached to their existing Clovo relationship.
For studio teams
- Current contextStaff see the feature beside the client, class, payment, plan, product, or task it affects.
- Clear controlThe studio keeps the relevant setup and operational decision inside Clovo.
For the record
- Useful historyThe outcome remains available for service, reporting, or follow-up.
- Less reconciliationConnected records reduce duplicate entry and side-channel admin.
One client, one connected history
See the relationship without stitching records together.
The current client view brings operational details and history together so staff can understand the person before acting. Require clients to accept your studio’s waiver before their first booking.
- Start from the current Clovo studio record.
- Show the status and context staff need to decide.
- Keep the member-facing result in sync where relevant.
- Preserve the outcome as part of the useful history.
Illustrative product detail shown
Illustrative studio activity shown
Useful at the front desk
Make the next conversation better informed.
The studio can work from current context while still controlling export, archive, deletion, waiver, and privacy-sensitive actions.
- See the latest action and current state.
- Understand who or what the action belongs to.
- Give the next staff member a useful handover.
- Use the history for service, reporting, or follow-up.
Feature by feature
What liability waiver connects.
The exact controls reflect the studio configuration, member context, and staff permissions involved.
01What it handlesLiability waiver
Require clients to accept your studio’s waiver before their first booking.
- Current feature state
- Relevant studio context
- Connected operational record
02Where it appearsWhere it appears
The capability appears in the relevant clients workflow, with the surrounding Clovo record close by.
- Dashboard or staff surface
- Member surface where relevant
- Live studio information
03What staff controlWhat staff control
The studio retains the configuration, audience, timing, eligibility, or operational decision that applies to the feature.
- Studio-owned settings
- Permission-aware actions
- Visible current status
04What stays connectedWhat stays connected
Clovo preserves the useful relationship between the action and the client, class, payment, plan, message, product, or studio event behind it.
- One source of truth
- Useful activity history
- Context for the next action
Designed for everyday studio work
Start with the action. Keep the context.
Liability waiver works as part of Clovo’s connected booking, payments, member experience, and studio operations platform.
Apply studio rules
Respect the configuration, eligibility, timing, and permissions that apply.
Show the status
Make the current result understandable without reconstructing a separate workflow.
Update connected views
Keep staff and member surfaces aligned where the feature appears in both.
Preserve the outcome
Retain useful history for the next service, operational, reporting, or follow-up moment.
Stay in one platform
Reduce duplicated data, disconnected tools, and manual reconciliation around the action.
Common questions
Liability waiver, without another admin project.
What does liability waiver do in Clovo?
Require clients to accept your studio’s waiver before their first booking.
Where does liability waiver appear?
It appears in the relevant Clovo studio workflow and stays connected to the member, class, plan, payment, message, product, or operational record involved.
Can studio staff control liability waiver?
Yes. The available controls sit inside the studio’s Clovo workspace and reflect the current configuration and staff permissions.
Does liability waiver work with the rest of Clovo?
Yes. The result remains part of the same connected platform, so staff do not need to reconcile a separate tool or duplicate the surrounding studio data.
The whole workflow is included
Put liability waiver to work.
Clovo brings booking, payments, member experience, and studio operations together in one platform built for boutique fitness.