If you just need to work with Timekit out-of-the-box, please refer to our glossary
In Timekit terms, a booking is a request to occupy a time-slot in a calendar.
It is important to understand the difference between a booking and an event as Timekit defines them.
An event is what gets placed in a calendar. A booking is what keeps track of the progess of a booking request in a workflow.
We'll get more into details about the workflow later on in the article [Intro to booking graphs], but for now lets just imagine a workflow that consists of these steps:
- A customer requests an appointment with you, at a given time-slot.
- You either confirm or decline the request.
- You might have to cancel the appointment.
These steps are what we call a confirm/decline workflow. The event, consisting of the given time-slot and probably more meta-data like where the appointment will take place and what the subject is etc, stays the same throughout this workflow.
What changes is the state of the booking.
It is important to know that your calendar will not be blocked at the requested time-slot, before the booking is confirmed. If you need your calendar to be blocked immediately when the request is send, you need to use a different workflow.
For a deeper look into our supported workflows, please refer to the Introduction to booking graphs
Before you dive directly into our tutorial on how to create a booking, please make sure you've first of all created a resource.