When the AI is offering appointment slots to a caller or chatter, you want it checking your real schedule, not guessing. Google Calendar integration solves that — one OAuth click and the AI knows when you’re free.Documentation Index
Fetch the complete documentation index at: https://docs.servicebooked.ca/llms.txt
Use this file to discover all available pages before exploring further.
Connect
Approve the OAuth disclosure
Before we redirect to Google, we show you exactly what permissions we’re requesting and why. Read it; click Continue.The permissions are:
- Read your calendar — to check availability before suggesting slots.
- Write to your calendar — to insert booked appointments.
- Read your email address — for record-keeping (knowing which calendar account you connected).
Sign in with Google
Google’s auth page loads. Sign in with the account that owns your business calendar, approve, and you’ll be redirected back to ServiceBooked.
What the AI does with calendar access
- Checks availability before offering slots in conversations: “I have Tuesday at 2pm or Thursday at 10am — do either work?”
- Respects your business hours: even if Tuesday at 6am is technically free in your calendar, the AI won’t offer it.
- Books confirmed appointments: when a caller agrees, the event lands on your calendar with the contact’s name, phone, and a summary of the conversation.
- Skips already-booked slots: in real-time. Two simultaneous callers can’t get offered the same slot.
Default appointment duration
Set in Settings → Business → Default appointment duration. The AI uses this when booking (“how long is a typical estimate visit?” — 30 min, 1 hour, etc.). You can override per-conversation if a customer mentions a longer-than-usual job.Buffer time
If you want a buffer between back-to-back appointments (so you have travel time), the AI respects “busy” blocks on your calendar. The simplest way to enforce buffers: create recurring “buffer” events on your calendar at the times you want padding (e.g., 30 minutes after every appointment). A native “buffer minutes” setting is on the roadmap.What gets written to your calendar
Each AI-booked appointment writes an event with:- Title: contact’s name + service (e.g., “Alex Jones — Kitchen quote”)
- Time: the slot agreed on
- Description: a summary of the conversation, the caller’s contact info, and a link back to the contact in your dashboard
- Location: blank (we don’t auto-set Google Maps locations — too easy to get wrong)
What if the customer cancels or reschedules?
If the customer reaches out (call, text, chat) and asks to reschedule or cancel, the AI handles it — updates or deletes the calendar event accordingly. Both directions sync: deleting the event from Google Calendar marks the appointment as cancelled in ServiceBooked, and vice versa.Disconnecting
Settings → Integrations → Google Calendar → Disconnect. We immediately stop accessing your calendar and revoke the tokens with Google. Existing booked events stay on your calendar (we don’t delete them); the AI just stops being able to read or write going forward.Multi-calendar / shared calendars
The integration is per-user. Each team member can connect their own Google Calendar account from their Settings → Account. By default the AI uses the org owner’s calendar; if you want round-robin booking across multiple techs, talk to support about multi-calendar configurations.Sync delay
Real-time. The AI calls Google’s API directly when checking availability, so the calendar state it sees is the live state — even an event you created 5 seconds ago is reflected.Next
If you don’t use Google Calendar, two alternatives:Cal.com
Open-source scheduler that works with any backing calendar.
Calendly
Use your existing Calendly link as a booking destination.