Pilot one booking or waitlist workflow with the existing schedule as the source of truth. Make capacity, credit use and offer expiry explicit. Keep health and class-suitability questions with qualified staff.
Find the repeated conversation
Look through the questions your London studio receives most often. Members may ask which class to book, whether a package is still valid or how to change a session. Some can be answered from approved information; others require an account lookup or a qualified person.
Choose one workflow instead of launching an assistant across every channel at once. Waitlist handling is a useful candidate when staff spend time contacting members after cancellations. The process has a clear trigger, a limited resource and a decision the system can record.
Keep the booking system authoritative
The schedule, instructor, room capacity and membership credits should remain in the system that manages them. A separate assistant can explain or request a change, but it should not maintain a competing version of class availability.
Distinguish a suggested slot from a confirmed booking. When the final space is taken, the system needs to handle the conflict clearly. Test the case where two members accept at almost the same moment. A friendly confirmation message is not enough unless the booking record has actually been created.
The member should never have to work out whether the chat or the calendar is right.
Make waitlist rules visible
Decide who receives an offer, how long they have to respond and what happens when the offer expires. Consider membership eligibility and whether a space is temporarily held. The policy needs to be understandable to both staff and members before it is automated.
For a London studio, use proper Europe/London time-zone handling for schedules and reminders. A fixed offset can become wrong when clocks change. Show the actual class date and time in the message, not only a relative phrase such as tomorrow morning.
Treat credits and cancellations carefully
A booking change may release a place, restore a credit or incur a fee under the studio’s policy. These are separate actions that need a consistent record. Explain the consequences before the member confirms, and avoid charging or consuming a credit from an ambiguous chat response.
Test expired packages, a cancelled class and a member who changes their mind halfway through the process. Staff should be able to see what completed and what did not. If a step fails, the system should not leave the member to reconcile their account manually.
Keep personal suitability with people
An assistant can explain approved class descriptions and how to contact the instructor. It should not decide whether a class is safe for an injury, pregnancy or medical condition. Route those questions through the studio’s qualified process.
Account access also needs boundaries. A member should see their own bookings and credits, not another person’s details. Begin with synthetic accounts and make identity checks part of the design before connecting a customer-facing assistant to live membership information.
Decide whether an app adds enough value
A dedicated mobile app can be useful when members return frequently for bookings, resources and account information. It is not automatically better than a well-designed mobile website or the booking platform they already use. Prototype the repeat task before building another destination.
Measure booking corrections, staff messages and waitlist offers that lead to valid bookings. Include the work required to supervise exceptions. Paus Club and Wellbey provide relevant portfolio context around membership and booking, but your studio’s rules and member habits should determine the first release.
Common questions.
Put the idea to work.
Prepared with AI assistance. This article shares general guidance and illustrative workflows, not a substitute for advice specific to your business.
Business thinking. Technical doing.
Talk about your workflow ↗
