For members
A shorter path
The intended action stays clear and close to the live studio experience.
Give connected tools one studio-safe identifier.
A unique code that unlocks third-party integrations and custom embeds.
Illustrative studio data shown
One identifier for everything you connect.
A single code that opens third-party integrations and custom embeds.
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
One account
Where members are involved, the result stays attached to their existing Clovo relationship.
For studio teams
Current context
Staff see the feature beside the client, class, payment, plan, product, or task it affects.
For studio teams
Clear control
The studio keeps the relevant setup and operational decision inside Clovo.
For the record
Useful history
The outcome remains available for service, reporting, or follow-up.
For the record
Less reconciliation
Connected records reduce duplicate entry and side-channel admin.
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.
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.
What it handles
A unique code that unlocks third-party integrations and custom embeds.
- Current feature state
- Relevant studio context
- Connected operational record
Where 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
What 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
What 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.
Use live records
Begin with the current client, class, plan, payment, product, message, or studio state.
Apply studio rules
Respect the configuration, eligibility, timing, and permissions that apply.
Reduce duplicated data, disconnected tools, and manual reconciliation around the action.
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.
Connected tools point at one studio.
The same code ties outside tools back to your Clovo studio.
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.
Put studio code to work.
Clovo brings booking, payments, member experience, and studio operations together in one platform built for boutique fitness.