Getting started, booking setup, customer management and restricted staff check-in.
Book Your Slot is a general-purpose WordPress booking, registration and reservation plugin for appointments, classes, workshops, demonstrations, events, tours, timed entry, collection slots and other workflows where people need to reserve a place, time or optional item.
Activate the plugin, open Book Your Slot in WordPress and complete the guided setup. Your normal defaults live in My usual settings. Individual bookings can deliberately use different settings without forcing you to repeat the same configuration everywhere.
Create an item in Events & bookings, work through the focused Basics, Booking, Times, Optional items and Messages & consent sections, then open it for bookings when ready. Use Put on website to publish the booking form on the page where customers should reserve.
People capacity and optional-item capacity are separate. A booking can still have places available even when an optional item is fully reserved, and timed sessions can have their own availability.
Book Your Slot keeps customer history across repeat bookings while preserving the details and consent record that applied to each booking. Marketing permission is optional and separate from the booking itself.
Create scanner-only users from Book Your Slot → Staff. Staff sign in through the front-end check-in portal rather than WordPress admin, then scan a customer QR code or enter the booking reference. They can validate, check in and mark a reserved item as collected. Named staff actions remain attributable in the audit trail.
The free core is being designed as a useful booking system in its own right, including core booking, customer and check-in workflows. Future Pro capabilities are planned around advanced automation, integrations, scheduling complexity, reporting and higher-value operational features. Pro pricing is not being advertised until the commercial entitlement and subscription lifecycle is complete end-to-end.
The current free core receives managed Stable updates without requiring a paid entitlement. Future paid capabilities can use separate entitlement checks rather than withholding core maintenance and security updates.
