Capability
A booking is a piece of work attached to a person.
Not a separate system with its own idea of who your customers are. A booking sits on the same record as the consent history, obeys the same retention rules, and lands in the same queues your team already works from.
What it is built on.
Everything below is the platform's existing machinery rather than a second implementation. That is the point of having booking inside the record system instead of beside it.
Resources and availability
What can be booked, when, and how much of it. Resource setup is a tenant-administered screen rather than a configuration file somebody has to ask us to change.
Dates in the resource's own zone
A booking uses the resource's local date and zone, so a tenancy operating in several countries can hold events dated by several calendars at once without any of them being wrong.
Requests that need a decision
Over-allocation and anything else needing a human go to a work queue as a booking request, with the same assignment, blocking and audit behaviour as every other work item.
Held back for the site
Capacity can be withheld from general availability and released deliberately, rather than being managed by somebody remembering not to sell it.
Part of the person's record
A booking linked to a person is that person's data: included in their export, removed on erasure, replaced on pseudonymisation. No separate data-rights process.
Confirmations through campaigns
Booking confirmations are triggered sends on the same engine as everything else, so they carry the same consent, suppression and one-click-unsubscribe handling.
Priced on what you actually book.
Booking is charged per bookable unit rather than per seat or per booking, because a unit is the thing you own and the thing your capacity is limited by. A pitch, a room, a court, a slot — whatever your unit is, that is what the price is counted on.
The rate tapers as the number of units rises, and there is a minimum monthly charge so a very small estate is still viable to run. Above the published band we quote, because at that size the shape of the estate matters more than the count.
- Charged per bookable unit, per month, on top of your tenancy
- The rate falls as the estate grows, in published steps
- A minimum monthly charge applies
- Above the top published band, we quote rather than extrapolate
Questions about booking
What counts as a bookable unit?
The thing your capacity is limited by — a pitch, a room, a court, a chair, a time slot against a named resource. We agree the unit with you before anything is priced, because getting it wrong in either direction makes the bill meaningless.
Does a booking show up on the customer record?
Yes, and that is the reason it lives here rather than in a separate product. It is visible alongside their consent history and their other work items, it is included in a subject access export, and it is removed when they are erased.
Can my team approve exceptions?
Requests that need a decision become work items in a queue, so they carry assignment, a blocked state that requires a named unblock action, and an append-only history of who decided what. Approval can be given to some roles and not others, like any other capability.
What about seasonal or withheld capacity?
Capacity can be held back from general availability and released when you choose. It is an explicit state rather than a convention, so it survives staff changes and shows up in the audit trail.
Related capabilities
Bring your resource list and the awkward case — the double booking, the group that splits across two units, the cancellation two hours out.