Service schedules

Define when a service can be booked — recurring hours, exceptions, and team scope.

Schedules control when a service offers slots. Configure them in the wizard Availability step using the Schedule composer.

Schedule types

Type	Use when
Recurring	Weekly pattern (e.g. Mon–Fri 9–17)
One-off	Single day event or temporary window

Team and location scope

Each schedule must include at least one team. That team (or those teams) must be able to work the hours you define.

Locations work as follows:

If the service has one location, the schedule can apply to it automatically.
If the service has several locations, pick at least one location on the schedule unless you intentionally want all service locations (leave locations empty only when that matches your setup).
When many teams and locations exist, Delivery filters what appears in the schedule composer.

The scope step shows a short checklist (required team, required locations when applicable, assignment warnings). Location chips can show which assigned teams work there.

Slots only generate where team hours, location hours, and schedule overlap.

Duration and buffers

Customer-facing duration comes from the selected service option (variant) in Offer.
Preparation and cool-down time on variants adds invisible padding before or after the slot.

How slots are computed

The system builds bookable slots automatically from:

Location availability
Team and employee availability
Service schedules you define here

When multiple teams can serve the same slot, customers see availability until all eligible teams at that time are booked.

Editing schedules

Changes apply to future availability. Existing bookings are not moved automatically — reschedule them from the calendar.

Troubleshooting

No slots — verify team selected on schedule, hours overlap, no time-off blocking employee.
Slots outside business hours — compare schedule to team business hours.