Rules instead of follow-up questions.
You set once who may book what — the booking respects it without anyone having to ask.
Service with access conditions (screenshot to follow)
The business decides who books what.
Access conditions define which requirements a client must meet — combined by your logic.
The booking checks this in the flow — not your team on the phone.
Access conditions of a service
Characteristics maintained on the profile.
Requirements live as characteristics on the client profile — maintained, visible, current.
Rules build on these characteristics — nobody has to keep them in their head.
Characteristics/tags on the client profile
Limits the system enforces.
Limitations cap how often a service can be booked; dependencies rule out combinations that do not fit.
What is not allowed is never offered as bookable in the first place.
Limitations and dependencies
Ready to run your business differently?
One platform. One business. Everything in view.