Skip to main content
Every slot on your booking page has to clear several layers before a visitor ever sees it. Understanding those layers explains why a time you expected to be open sometimes isn’t.

​
The layers

1

Your weekly schedule

The base. You set the hours you’re open for each weekday, say Mon–Fri 09:00–17:00. Nothing outside those windows is ever bookable.
2

Date overrides

Exceptions to that base for specific dates. A holiday, a day off or a Saturday you’re making an exception for.
3

Your connected calendars

Every calendar you’ve connected is checked. A busy event overlapping a slot, even by a minute, removes it. This is what prevents double bookings.
4

Buffer times

Padding around existing bookings. With a 15-minute buffer after, a meeting ending at 10:00 pushes the next bookable slot to 10:15.
5

The service being booked

Its duration decides how the open time is sliced up and it can carry its own buffers and its own date overrides on top of your account-wide ones.
A slot has to survive all of them. One conflict anywhere and it’s gone.

​
How the open time is sliced

Tikk takes what’s left after those layers and cuts it into slots the length of the service being booked. A 90-minute gap offers three slots for a 30-minute service and none at all for a 2-hour one. There’s also a minimum of 15 minutes’ notice: slots starting sooner than that don’t appear, so nobody books you for something starting in four minutes.
Slots are worked out the moment someone opens your page, never cached ahead of time. If you accept a meeting in another calendar right now, the matching slot is gone from your booking page immediately.

​
Timezones

Your weekly schedule and date overrides are stored in your timezone. Visitors see every slot converted to their own local time, so neither of you has to do the arithmetic. Tikk takes your timezone from your browser and records it whenever you save Settings → Profile.
That means a long trip can move it. If you save your profile from a machine set to another timezone, your stored hours don’t move with it. 09:00 stays 09:00, now in the new zone. After relocating, open your schedule and check it still says what you meant.
Setting all of this up is covered in Set your availability. If you’re reading slots programmatically, see List Availability.