Resource-based services
Choose team, resource, or hybrid capacity, inherit booking limits, and offer resources in widgets and the Customer Portal.
By default a service uses team capacity. Once you manage bookable resources, a service can consume a resource instead — or as well.
Capacity types
| Type | When to use |
|---|---|
| Team | Staff deliver the service; no asset is occupied (default) |
| Resource | One asset is booked — a car, room, pitch, or unit — with no team required |
| Team and resource | Both a team and an asset must be free, for example therapist plus treatment room |
Set the capacity type in the service wizard's delivery step. A warning appears if you choose a type but leave teams or resources empty.
Availability
Customer slots require every applicable layer to agree: the service schedule, team hours, resource hours and unavailable periods, and no conflicting booking on the same team or resource. See Service schedules.
Booking limits inherited from resources
Assigned resources can supply limits such as drivers, passengers, guests, adults, children, pets, tents, stay length, and check-in and check-out times. The wizard summarises matching values across the assigned resources, or shows Mixed across resources.
You may set a stricter limit on the service, but you can never widen past what the asset physically allows. To push configured service values onto the resources assigned on that save, review the before-and-after preview and confirm. It is a one-time update and does not affect resources added later.
Booking widgets and the Customer Portal
Customers choose broad totals such as guests or passengers in the widget. The booking form then collects the specific details the chosen resource requires — counts, ages, and driver information.
Enable Promote individual resources to give each vehicle, room, accommodation, or pitch its own gallery-led card that combines every matching service. Customers can switch service while keeping the chosen resource. Use the exclusion option when hybrid team-and-resource services should keep the standard service-first layout.
Continuing from a widget into the Customer Portal
When a customer moves from the booking widget into the Customer Portal to finish a booking, the choices they already made — service, option, resource, dates, and any extras with their quantities — are carried across, so nothing has to be selected twice. If a change makes an earlier answer impossible, the answer is adjusted and the customer is told.
Check-in and check-out times
Each accommodation or pitch has its own check-in and check-out window, and a standard 15:00 / 11:00 applies where none is set. A service can only make that window narrower — a later check-in or an earlier check-out — never wider. Nightly bookings are checked against the window of the resource assigned to the booking, in your workspace's time zone. Pick-up and return times for rentals follow the same rule, with 09:00 / 18:00 as the standard default. Prices are not affected by these times: nights are counted by date — see Pricing by hour, day and night.