Help Center
DocsAvailability Schedules
Weekly hours, date-specific hours, the does-not-repeat mode, shared versus custom schedules, and which control wins when they disagree
Every booking page has an Availability section, and it is the second thing you see.
Open a booking page from Scheduler → Booking pages and the editor shows six sections in a rail: Basics, Availability, Timing, Limits, Team, and Booking form. Availability is the second one, and its description reads “Add multiple blocks per day to model lunch breaks (e.g., 9-12 + 1-5).”
Four things sit in plain view because you have to decide them to share a working link: where the hours come from, the weekly grid itself, date-specific hours, and a one-line summary of the booking window. Everything else in the section — the booking-window controls themselves — lives behind the Advanced disclosure, which starts closed. A brand-new page you create with nothing but a title already has usable hours: Monday to Friday, 9:00 AM to 5:00 PM, with Saturday and Sunday off.
Each weekday has a switch and a list of time periods. Switch a day on and set a start and an end time. A day with no periods reads Unavailable. If every day is off, the editor says “This page currently offers no times.”
- Up to six periods per day. Click + Add another period to this day to split a day around a lunch break or a standing internal meeting. At six, the button is disabled and the sentence “Up to 6 periods per day.” appears beside it.
- Periods may touch but not overlap. 9:00 to 12:00 plus 12:00 to 5:00 is two valid periods. Two periods that genuinely cross are refused with “Time blocks on the same day cannot overlap.”
- A period has to fit the meeting. A period shorter than the meeting length is refused — for a 30-minute page, “A 30-minute meeting needs at least a 30-minute period.”
- Presets. Under Start from a preset there are three one-click starting points: Weekdays 9-5, Weekdays 8-6, and Every day 9-5.
- Copy one day to others. The overflow next to a day row offers Copy time to all (all seven days at once) and Copy to…, which opens a checkbox list of the other days and an Apply button.
Below the weekly grid, Date-specific hours handles the exceptions: “Change your availability for specific dates, like holidays.” A date listed here replaces the weekly rule for that day — it is not added on top of it.
Click + Add a date.
Decide what those dates mean.
Click Apply.
- A date-specific row that falls outside the booking window is flagged: “Outside your booking window, this date will not be offered.”
- Dates that have passed collapse behind a Show 3 past dates toggle rather than cluttering the list.
- Removing a date is a single click on the row. If the removal fails, the row comes back and a message says so.
- On a brand-new page the control reads “Save this page once to add specific dates.” — dates attach to a saved schedule.
- The cap is 200 dates per schedule. Near the cap the dialog says how much room is left (“You can add 3 more.”); at the cap the Add button is disabled and reads “Limit reached (200 dates).” Replacing an existing date uses no headroom.
A live check, at the foot of the Availability section, of what this configuration really offers.
Below the date list, a strip headed Next available times shows what a booker would actually be offered, and it re-checks as you edit. It lists up to five start times, at most one per day, walking forward through the next open days; if there is more beyond them it adds and more rather than implying that is everything. On a page with several eligible hosts the heading says so instead — “Next available across 3 hosts”.
Underneath, a seven-day line gives the reason for every day that offers nothing: Fully booked, No hours, Outside your booking window, or Too soon to book. With all seven days open that line is not drawn at all, because there is nothing to explain. If the whole week comes back empty it says so in one sentence — “This configuration offers no times in the next 7 days.” — and if the busy times could not be read it says “Times could not be checked just now.” rather than claiming the week is free.
The Repeat control at the top of the weekly grid has two settings: Repeat weekly (the default) and Does not repeat. Switch to Does not repeat and the seven weekday rows and the presets disappear — only Date-specific hours remains. Nothing is offered except the dates you add there. This is the right shape for a one-time class, an interview week, or a pop-up clinic.
Your weekly hours are not thrown away. The editor says so directly: “Your weekly hours are kept and will apply again if you switch back.” The slot preview also stops guessing on a one-off schedule — “Times are not previewed for a one-off schedule.”
The first control in the Availability section is a pair of choices under the question “Where do these hours come from?”:
| Field | Description | Type |
|---|---|---|
| Shared schedule | Reuse one set of hours across several booking pages. Pick an existing schedule from the list; editing it changes every page that points at it. | radio |
| Custom hours for this page | These hours belong to this page only. Nothing else changes when you edit them. | radio |
A shared schedule is listed with its name, whether it is the default, and how many pages use it — for example Support hours · default · used by 3 booking pages. When a page is on a shared schedule, a band above the grid states the blast radius before you type: “Editing these hours changes Support hours, used by 3 booking pages.” If the usage count cannot be read, the band is honest about that instead of guessing.
If your organization has none yet, the section says “Your organization has no shared schedules yet.” and offers Create a shared schedule — give it a Schedule name and click Create. Existing schedules are managed from Settings > Company > Scheduler under Availability schedules(“Reusable sets of hours that your booking pages can share.”), where you can rename, duplicate, Set as default, or remove one.
How far ahead people can book — inside the Availability section's Advanced disclosure.
Open Advanced inside Availability and the question is “When can people book?” with three answers:
| Field | Description | Type |
|---|---|---|
| Number of days into the future | A rolling window. Set Days ahead between 1 and 365; the last bookable date moves forward with today. New pages default to 30 days. | mode |
| Within a date range | A fixed window. Set a Start date and an End date. The days-ahead value is ignored entirely while this mode is selected. | mode |
| Up to a year ahead (365 days) | No end date. People can keep booking indefinitely; the page never closes itself. | mode |
Whichever you pick, one plain sentence underneath states the result — for example “People can book through Mar 31.”, “People can book March 1 through March 31.”, “People can book up to a year ahead.”, or, once a fixed range has ended, “This page is closed to new bookings.” With the disclosure closed, the same fact rides the section summary as “Booking window: through Mar 31”.
When the weekly grid and a date-specific entry disagree about the same day, the answer is fixed and does not depend on the order you set them in:
- A date marked unavailable blocks the day. Nothing else is consulted — not the weekly hours, not any times saved on that same date.
- Otherwise, date-specific hours replace that weekday's weekly hours. They substitute for the weekly rule, they do not extend it.
- Otherwise, a schedule set to Does not repeat offers nothing. The weekly grid is inert in that mode, so a day with no date-specific entry has no times.
- Otherwise, the weekly hours for that weekday apply.
Two more filters run after that, on the times these rules produced: the booking window drops dates outside it, and the scheduler removes any slot that is already busy — existing bookings, synced calendar events, CRM activities, and any required resource. See Booking Pages for how busy time is computed.
Your offerable time, drawn beside your real meetings.
Turn on the Bookable windows layer on the Calendar and check a booking page in the Booking pages section, and that page's offerable time is drawn on the grid in the page's own color. Click a band to open a peek titled Bookable time, which names the page and offers Create here and Share link; with scheduler.edit it also offers Edit availability and Make unavailable.
In week and day views on a desktop-sized screen with a mouse or trackpad, you can drag across an empty stretch of a day column to open that time. Releasing opens a dialog titled Add availability with two choices, Offer this time and Make unavailable instead. Confirming writes a date-specific entry — exactly what the editor writes — and the calendar confirms with “Availability added for that date.” or “Marked unavailable for that date.”
If the range you drew belongs to a shared schedule, the dialog says so before you commit — for example “This changes Support hours, used by 3 booking pages.” — and offers to switch that page to its own hours first instead. If the shared schedule is one you may use but not change, the dialog explains that only this page can be changed.
| Field | Description | Type | Default |
|---|---|---|---|
| Time periods per day | Up to 6 on any single day, in both the weekly grid and a date-specific entry. | limit | 6 |
| Date-specific hours per schedule | Up to 200. Replacing a date you already have does not consume another one; removing a date frees a slot. | limit | 200 |
| Shared schedules per organization | Up to 25. Only named, reusable schedules count — hours that belong to a single page do not. | limit | 25 |
| Days ahead | Between 1 and 365 when the booking window is set to a number of days into the future. | limit | 30 |
- scheduler.view — required to open a booking page and read its hours.
- scheduler.edit — required to change hours, add or remove date-specific entries, change the booking window, or drag on the calendar. Without it the Availability section is read-only: the hours and the resolved booking-window sentence still render, but there are no inputs.
- scheduler.admin — required to change the organization-wide scheduler settings that sit alongside availability. The workspace booking URL needs this and a workspace owner or admin role; full scheduler access on its own shows it read-only.
- A shared schedule can also be read-only for you specifically: “You can use this schedule but cannot change its hours.” You can still point a page at it and change that page's other settings.
A date I added is not being offered
Check three things in order: the date is not also marked unavailable (that always wins), the date falls inside the booking window (the row says so if it does not), and the period you gave it is at least as long as the meeting.
I changed the hours and another page changed too
The page is on a shared schedule. Switch it to Custom hours for this page to give it hours of its own, or edit the shared schedule knowingly — the band above the grid names it and how many pages it covers.
The page offers no times at all
Either every weekday is switched off (the editor says “This page currently offers no times.”), or the schedule is set to Does not repeat and has no date-specific entries yet, or the booking window has closed.
I cannot drag on the calendar
Dragging needs week or day view, a desktop-width window, a mouse or trackpad, scheduler.edit, the Bookable windows layer on, and at least one checked booking link that has a saved schedule. It is also unavailable while you are viewing a teammate's calendar.