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

Compact weekly hours

For recurring weekly schedules you can:

Select days (Weekdays, Weekend, Every day, or individual chips).
Enter shared time blocks once — including split shifts such as 09:00–12:00 and 13:00–17:00.
Apply those blocks to the selected days.
Review a short week overview. Days with the same hours stay collapsed (“Same as Monday”). Only different days show as overrides.
Copy one day’s hours to other days when needed. If a target day already has hours, you confirm before replacing them.

Day-specific overrides (for example a shorter Friday) stay editable on their own. Changing the shared pattern does not overwrite overrides unless you choose to replace them.

One-off dates stay separate from the weekly pattern.

Operational availability overrides

Use Operational availability overrides only when a schedule must stay bookable outside normal team hours, team time off, or venue opening hours.

These are privileged settings:

Enabling an override asks for confirmation and explains the consequence.
Existing bookings are not cancelled, moved, or refunded.
Resource hours, booking collisions, buffers, and capacity still apply.
Team time off, resource hours, and venue closures are still managed on those records — this section only changes how this service schedule interacts with them.

Ordinary one-off openings and weekly day overrides are not the same as these operational overrides.

Overrides appear in the wizard Summary so you can review them before publishing. If you choose No additional Service schedule, saved overrides stay on the schedule but are ignored until you switch back to configured schedules.

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.

The occurrence list in the composer shows planned schedule times only. Use Effective availability on the same Availability step to see upcoming customer-bookable slots from the last saved Service (Team/Resource hours, time off, location hours, bookings, buffers, and capacity applied). Create mode shows this preview after the first save.

Editing schedules

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

If you choose No additional Service schedule, saved schedules are kept but ignored until you switch back to configured schedules.

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.

Service schedules

On this page