The booking appears in Google Calendar while the caller is still on the line
GreetKeeper reads your real availability before it offers a time, then writes the event. Google Calendar is one of the few tools we write into directly.
Caller
“Hi, I saw you online. Do you have anything Thursday morning? I work from home so any time before noon is fine.”
What happened next
- Checked your Google Calendar: Thursday 9am and 11am open, 10am blocked
- Booked Thursday 9:00am, 45 minutes, on the calendar you nominated
- Invite sent to the caller's email, with your address in the location field
How GreetKeeper connects to Google Calendar
Three states, and we publish the one that is true rather than the one that reads best.
| Tool | How it connects | What that means |
|---|---|---|
| Google Calendar | Writes directly |
What Google Calendar is doing in this setup
Google Calendar is the calendar behind a Google Workspace or Gmail account. Most small businesses already run their day out of it, which is why it is the first thing people ask about.
Two things matter for phone booking. Google's API lets an authorized app both read busy times and create events, and it returns those busy times fast enough to use mid-conversation. That combination is what makes a live booking possible instead of a callback.
You keep using Google Calendar exactly as you do now. Your staff see the new event in the same app on the same phone, and nothing about your existing events changes.
Where the booking lands
The honest answer to the only question that matters: the event is created in Google Calendar itself, not in a copy we keep.
You nominate one calendar during setup. That might be a shared team calendar, or one person's. GreetKeeper writes the event there, with the caller's name in the title and the reason for the call in the description.
Before it offers a time, GreetKeeper asks Google which slots are busy. A caller is only ever offered a gap that is genuinely free at that moment. If someone books the same slot from the front desk two seconds earlier, Google rejects the write and the caller is offered the next opening instead.
The caller gets a calendar invite at the email address they gave, if they gave one. If they did not, the event still lands on your calendar with their phone number on it.
Connecting it
One sign-in and two choices. Nothing to install and no code.
Sign in with the Google account that owns the calendar
You approve the connection in Google's own consent screen. GreetKeeper asks for calendar access and nothing else, and you can revoke it from your Google account page at any time.
Pick the calendar and the hours you take bookings
If the account has six calendars, you choose which one receives bookings. You also set your real opening hours, so an 11pm caller is offered tomorrow morning rather than tonight.
Define your appointment types and their lengths
A consultation might run 30 minutes and a first visit 60. GreetKeeper uses those lengths to work out which gaps are actually usable, rather than offering a 20-minute hole for an hour-long job.
Place a test call
Ring your own number and book something. Watch the event appear in Google Calendar, then delete it. That test is the only proof worth having before you point your real line at it.
What this connection does not do
Questions about Google Calendar and GreetKeeper
Does GreetKeeper double-book if two calls come in at once?
No. Each booking is written to Google before the caller hangs up, and Google rejects a write into a slot that has just filled. The second caller is offered the next free time instead.
Can it book into more than one calendar?
You nominate one calendar for bookings during setup. If you run separate calendars per person, the usual answer is a shared team calendar that everyone can see.
What happens to the call if Google is unreachable?
The call still runs and you still get the transcript, the summary and the caller's number. GreetKeeper tells the caller you will confirm the time, rather than promising a slot it could not write.
Watch it book into your own calendar
Bring a real scenario. Two minutes, no card.