For members
A shorter path
The intended action stays clear and close to the live studio experience.
Give every studio update a place members can revisit.
Clients can revisit announcements in the app, with read and unread status kept in sync.
Illustrative studio data shown
Studio news stops scrolling away.
Members can come back to an announcement long after it was sent.
One feature. Three connected outcomes.
Clients can revisit announcements in the app, with read and unread status kept in sync. 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.
Communication continues the studio voice
Reach members with context, not noise.
Messages feel more useful when they relate to a real booking, purchase, achievement, announcement, or invitation from the studio the member already knows.
Clients can revisit announcements in the app, with read and unread status kept in sync. The product detail matters because it supports a real member, staff member, and studio moment.
The message beside the moment
Send communication that has a reason to arrive.
Clovo can connect the message to the member action or studio event that makes it timely and understandable. Clients can revisit announcements in the app, with read and unread status kept in sync.
- 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
One studio voice
Keep announcements and outcomes visible after delivery.
Members retain an in-app record while staff can understand the audience, trigger, and current outcome.
- 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 announcement inbox connects.
The exact controls reflect the studio configuration, member context, and staff permissions involved.
What it handles
Clients can revisit announcements in the app, with read and unread status kept in sync.
- Current feature state
- Relevant studio context
- Connected operational record
Where it appears
The capability appears in the relevant communication 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.
Announcement inbox 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.
Read here, read everywhere.
Announcements sit in the same app as bookings, with status kept in sync.
Common questions
Announcement inbox, without another admin project.
What does announcement inbox do in Clovo?
Clients can revisit announcements in the app, with read and unread status kept in sync.
Where does announcement inbox 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 announcement inbox?
Yes. The available controls sit inside the studio’s Clovo workspace and reflect the current configuration and staff permissions.
Does announcement inbox 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 announcement inbox to work.
Clovo brings booking, payments, member experience, and studio operations together in one platform built for boutique fitness.