Calendars and availability
How dCal knows when you are free: connect your Google or Outlook calendar, set your weekly hours in schedules, choose time zones, and understand how dCal turns all of that into the open times your gue
Your booking links only offer times when you are really free. dCal works that out from two things you set up once: the hours you want to take meetings, and the calendars where the rest of your day lives.
How it fits together
Calendars
Calendars in the left menu
Connected Google or Outlook accounts. Busy times block new bookings, and confirmed bookings are written to the calendar you choose.
Schedules
Availability in the left menu
Your weekly hours, split into several ranges a day if you like, plus date overrides. A personal event can follow your working hours, use a saved schedule or have custom weekly hours of its own.
Time zones
Settings and each schedule
Your own time zone, and the time zone each schedule's hours are in. Guests see times in their own time zone and can switch to another.
Event timing
Each event in Events
Length, slot interval, buffers and minimum notice decide how times are cut out of your hours, and the booking window how far ahead guests can book.
Out of the box you already have a Working hours schedule, Monday to Friday from 09:00 to 17:00. Connecting a calendar is the step that makes your links safe to share: until then, dCal cannot see meetings you booked elsewhere.
In this section
Connect Google or Outlook, choose which calendars block times and which one receives bookings, test, reconnect or disconnect, and add an online meeting link.
Create schedules, add several ranges a day and date overrides, choose the schedule each event uses, and set custom weekly hours for one personal event.
Your time zone, each schedule's time zone, the guest's own time zone and the picker they use, and daylight saving time.
Why a time is or is not offered: busy times, pending requests, buffers, minimum notice, how far ahead guests can book, the 10-minute hold, and what happens when a calendar cannot be read.
Related
Last updated