Courses and progression
Level, prerequisites and the logical next session: an enrolment that respects progression avoids a badly placed member and an instructor handling the gap live.
Mindbody
There is a spot left in the class, but the member does not hold the right credit. The credit rule is checked before saying yes, and activation happens site by site.
7 days, 20 answered calls, no card
Where your enrolment lands
The enrolment is written into Mindbody once the site is activated; otherwise the request is written into Zenvox, with the discipline, the stated level, package status and the spot wanted. The platform keeps the truth of its classes and credits: a spot is given only if your credit rule allows it, and the waitlist takes over when it does not.
On access, appointments, classes, clients, purchases and resources are documented. Activation happens per site, with roles and a commercial contract to confirm — nothing here should be assumed free. The vendor release notes show plainly that cancellation permissions get tested rather than inferred.
Mindbody holds the classes, enrolments, credits and resources of studios and gyms; one spot is left in the six o'clock class, but the package expired or the level does not match the instructor prerequisite.
Read, create, update, cancel
The status below comes from vendor documentation and from what has not been proven: live access, costs and credit behaviour.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Classes, capacity, instructor, client and purchases are documented. That read is what allows answering there is a spot left, but your package does not cover it, instead of enrolling somebody wrongly. |
| Create | To qualify | Enrolment is documented. Credit, capacity and waitlist behaviour remain to be tested: the last spot can go during the call, and an enrolment is confirmed after a successful write, not before. |
| Update | To qualify | Changing class touches credit and level. Permissions and multi-service behaviour are flagged by the vendor as version-specific: they get verified on your site, not in general. |
| Cancel | To qualify | Cancelling follows your credit policy and frees a spot the waitlist wants. Until the behaviour is proven free of inconsistent state, it is passed on and handled by the studio. |
What is included, what needs an add-on
Answering during a class, identifying discipline, level and member, stating the cancellation policy and passing the request on belong to your services base. Progress tracking and package handling are named add-ons.
The authorisation, and what holds the truth
A studio sells access rights as much as classes. Authorisation therefore covers both.
- Activation happens per site, with defined roles; Zenvox asks for no password
- Access and its cost are confirmed in the contract: nothing is presumed free or included
- An enrolment is confirmed to a member after a successful write, not on the strength of a spot seen on screen
- The instructor validates level and prerequisites; the manager applies credit exceptions
- The waitlist is offered when a spot cannot be granted, rather than a flat refusal
Five in the afternoon, the studio is mid-class. The call is taken by Zenvox; nothing is written into the platform.
MemberHi, I would like to join the six o'clock class tonight.
ReceptionistLet me take your name and a callback number. Which discipline and which level, and do you have an active package or credits?
ReceptionistI am passing your request to the studio with all of that. If no usable spot is left for your package, I put you on the waitlist rather than leave you with nothing.
The studio receives a complete request: member, discipline, level, package status, class wanted. Nobody was enrolled in a class their credit did not cover, and the spot stays open for a member who can take it.
When the connection is not there
The platform keeps its classes and credits, and the receptionist works in Zenvox native mode.
- The request is created inside Zenvox with discipline, level, class wanted and the package status as stated
- Your online enrolment link is texted out when one exists
- Your cancellation and credit policy is read out in your own words
- You find the call, its transcript and its reason in the app
- The day enrolment becomes qualified, it is added without redoing your setup
Questions about this connection
Does she enrol a member whose package has expired?
No: a spot is given only if your credit rule allows it, and the waitlist takes over when it does not. The read is what allows answering that a spot is left but the package does not cover it, instead of enrolling somebody wrongly.
When is the enrolment confirmed to the member?
After a successful write, and not on the strength of a spot seen on screen. The last spot can go during the call, and credit, capacity and waitlist behaviour remain to be tested.
How does activation happen?
Per site, with defined roles, and access and its cost are confirmed in the contract: nothing is presumed free or included. Zenvox asks for no password.
Are the permissions the same everywhere?
No, and the vendor flags it itself: permissions and multi-service behaviour are version-specific points, verified on your site rather than in general. Cancellation permissions get tested rather than inferred.
What about the member level?
The instructor validates level and prerequisites, and the manager applies credit exceptions. An enrolment that respects progression avoids a badly placed member and an instructor closing the gap live.
Where to next
See the practice concerned, or the full list of software studied.
Mindbody