Calendar-backed booking, Google Calendar and Outlook
Bookings that live directly in the operator's Google Calendar or Outlook, with no separate scheduling system to keep in sync.
What shipped
The recal adapter wires booking directly into a calendar, Google Calendar or Microsoft Outlook. Availability comes from the calendar; a confirmed booking goes back to the calendar. There's no second schedule to keep aligned.
Why we built it
Plenty of service operations already live inside a calendar. The professional blocks off slots, adds personal appointments, reshuffles the day, all in the Google Calendar or Outlook they already use. Asking them to keep a second booking system in sync with that calendar is how slots get double-sold and how frustration sets in.
recal treats the existing calendar as the source of truth. If a slot is free on the calendar, it can be booked; when it's booked, it becomes an event on that same calendar. The professional keeps working the way they already do.
How it works
Availability is read from the connected calendar, honoring the events that already exist. A confirmed booking creates the matching event. Because reads and writes happen in the same place, there's no window where two customers see the same slot as free.
A foundation for other adapters
This release also adds calendar-connection types to the SDK core. They aren't only for recal: any future adapter that needs to talk to a calendar builds on the same typed foundation instead of reinventing the connection.