Organizing fitness classes combining round robin and seats. #14861
Labels
booking-page
area: booking page, public booking page, booker
docs
area: docs, documentation, cal.com/docs
event-types
area: event types, event-types
Low priority
Created by Linear-GitHub Sync
🚨 needs approval
This feature request has not been reviewed yet by the Product Team and needs approval beforehand
🎨 needs design
Before engineering kick-off, a designer needs to submit a mockup
teams
area: teams, round robin, collective, managed event-types
ui
area: UI, frontend, button, form, input
I wanted to share my experience with cal.com and some issues I have met with the solution and support.
Here is the use case.
Two (and later more) physiotherapists work in the same building. Each of them is free to manage its own availability. One of their activities is to organize EMS (electrostimulation while you do fitness) sessions for groups of 3. They can organize scheduled classes but also enable people to book collective sessions. The classes would be open when they are free between 6 and 9 pm during work weeks and on a different schedule on weekends.
I have tried several configurations and didn't manage to make it work as it would be expected.
I'll recap below all the issues I faced and how the product can be improved. I want to state that I have asked for a refund and it was processed without any pushback within 3 hours. I am not upset but I really believe in this product and the team, so here is some feedback.
Before going into the specific of the configuration issue. I want to say that having team access gated is really an issue. While I know that trial accesses are not so popular anymore, cal.com value to a user is in the details of what you can and cannot do with its most advanced booking features. It's annoying not being able to try it out. I think that being directed towards a very high level marketing pitch video can be a bit infuriating. I expect it to point to documentation but I have found the docs to be very incomplete and not very useful. There are several times when configuring the solution where the behavior of a feature would not be obvious to me and I couldn't find any information.
On these points my reco would be:
Now some of the issues I faced for the use case.
I have plenty of other stuff I noticed everywhere but having the above fixed would be nice. I have the overall feeling that the information architecture might need a bit of rethink. I didn't think much about it but I would explore separating individual and team usage more in the interface.
Please note that I have not seen any platform doing correctly this use case at the moment. I think it is an opportunity.
What I really liked : OSS, impersonating a user, good reactivity on gh and support.
The text was updated successfully, but these errors were encountered: