Use live records
Begin with the current client, class, plan, payment, product, message, or studio state.
Web & integrations
Give connected tools one studio-safe identifier.
A unique code that unlocks third-party integrations and custom embeds.
- Livestatus
- 3 activeembeds
- Connectedstudio code
Illustrative studio data shown
The website should stay connected to the studio
Bring live Clovo actions into the places members already visit.
Embeds, studio links, and connected surfaces reduce duplicated updates by drawing from the same live studio information members use in Clovo.
A unique code that unlocks third-party integrations and custom embeds. The product detail matters because it supports a real member, staff member, and studio moment.
Why it matters
One feature. Three connected outcomes.
A unique code that unlocks third-party integrations and custom embeds. 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 source, more useful surfaces
Publish the live studio state instead of copying it.
The website and shared links can present current timetable or product information from the same Clovo records staff maintain. A unique code that unlocks third-party integrations and custom embeds.
- 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
A shorter path into Clovo
Let the member continue without starting over.
Connected destinations keep the studio, product, and intended action attached as the member moves from web to Clovo.
- 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 studio code connects.
The exact controls reflect the studio configuration, member context, and staff permissions involved.
01What it handlesStudio code
A unique code that unlocks third-party integrations and custom embeds.
- Current feature state
- Relevant studio context
- Connected operational record
02Where it appearsWhere it appears
The capability appears in the relevant web 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.
Studio code 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
Studio code, without another admin project.
What does studio code do in Clovo?
A unique code that unlocks third-party integrations and custom embeds.
Where does studio code 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 studio code?
Yes. The available controls sit inside the studio’s Clovo workspace and reflect the current configuration and staff permissions.
Does studio code 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 studio code to work.
Clovo brings booking, payments, member experience, and studio operations together in one platform built for boutique fitness.