What it would be
A Google OAuth connection from the dashboard, with the receptionist reading free and busy time directly and creating the event itself. The booking rules would not change: a time must exist to be offered.
Calendars
On requestMost shops don’t need this. Google Calendar already works today through Cal.com or Calendly. This page is for the shop that doesn’t want a booking layer between the receptionist and Google, and is willing to have us build that connection.
On request. Not live. There is no Google sign-in in the dashboard today. If you need this, we scope it with you. Google Calendar through Cal.com or Calendly is live now.
A Google OAuth connection from the dashboard, with the receptionist reading free and busy time directly and creating the event itself. The booking rules would not change: a time must exist to be offered.
Nothing, for most shops. Cal.com or Calendly handles availability, event types, and required questions already. The direct build only removes that layer.
Which calendars count, how visit length is set without an event type, and how Google’s app verification is handled for an app that reads calendars.
It would behave like today’s calendars: real free time only.
The same. A late caller would be offered the next free windows.
What scoping would involve. These are not steps you can follow today.
Policy, cost, or one fewer vendor. It shapes what we build.
Which Google calendars hold your availability.
We would book test visits against your calendar with you.
Yes, through Cal.com or Calendly, which connect to it.
It is on request: we build it for a client who needs it. There is no public date.
Adapter work is scoped separately at setup. It is not a hidden charge once you are live.