Bookings (N:1 Shared Bookings Pages): Unable to use calendar availability to regulate appointment offerings to clients

Question

|Name of Service/App Used: Bookings, Shared Bookings Pages via Microsoft 365, N:1 Service

Environment: Bookings (Web), Business type (Other), MacOS on Sonoma 14.5
Name of Service/App Used: Bookings, Shared Bookings Pages via Microsoft 365, N:1 Service Environment: Bookings (Web), Business type (Other), MacOS on Sonoma 14.5

Current Settings:

Resources I have reviewed:

Tried various combinations between "Schedule when staff are free" and/or "Default Scheduling Options" on/off across all three levels (shared booking page config, service config, and administrator config). I've also taken the Bookings module, but regardless of what I try clients remain able to schedule times with me 9am - 5pm, regardless of whether I'm available to meet with them.
Tried various combinations between "Schedule when staff are free" and/or "Default Scheduling Options" on/off across all three levels (shared booking page config, service config, and administrator config). I've also taken the Bookings module, but regardless of what I try clients remain able to schedule times with me 9am - 5pm, regardless of whether I'm available to meet with them.

Staff Availability - Article; N:1 Service - Article; Bookings - Training Module
Staff Availability - Article; N:1 Service - Article; Bookings - Training Module

Answer 1

Hello Sophie Strassmann,

Your booking staff setting and your default scheduling policy looks fine, but the service you're showing doesn't use the default scheduling policy and is therefore using it's own custom policy.

Option 1 is to activate the default policy and it will use every setting you've set there.

Option 2 is to navigate to your service -> Availability options and make sure that the service in this case has the availability you want.

Answer 2

Hello Sophie Strassmann, Your booking staff setting and your default scheduling policy looks fine, but the service you're showing doesn't use the default scheduling policy and is therefore using it's own custom policy. Option 1 is to activate the default policy and it will use every setting you've set there. Option 2 is to navigate to your service -> Availability options and make sure that the service in this case has the availability you want.