Connect Google Calendar
Keep approved appointment types and calendar availability aligned so your AI Agent offers times the business can actually fulfil.
Connect the calendar the business intends to maintain
Use the Google account that owns or manages the approved business calendar—not whichever account happens to be open in the browser. Confirm the calendar, timezone and owner first; authorize the connection; attach it to the intended appointment type; then test a booking, busy time and schedule change.
One calendar connection supports the booking path
The connection does not create availability by itself. It must be linked to the correct appointment type and used by an AI Agent that is allowed to book that event.
The approved business identity grants access.
The calendar supplies busy times and receives events.
Duration, schedule, timezone and booking rules apply.
The customer confirmation and calendar record agree.
Confirm the account and calendar owner
A business calendar is usually easier to maintain than a personal calendar tied to one employee. Document who owns the connection, who manages the calendar and who may renew or revoke access.
Target Google account
Identify the business account that should approve and maintain the connection.
Calendar name
Select the calendar that represents the approved service, team or location.
Timezone
Confirm the operating timezone used for availability and customer confirmations.
Event ownership
Decide who owns created events and is responsible for maintaining the schedule.
Access authority
Name the person authorized to approve, renew or revoke the connection.
Booking scope
List the appointment types, AI Agents, locations and resources the calendar supports.
Choose an account the business can maintain through staff changes. Avoid making a personal employee calendar the only owner of a customer-facing booking workflow.
Understand what two-way sync can do
When enabled for an appointment type, ConvoRev bookings and Google Calendar availability can inform each other. Actual behavior depends on the appointment, connection and synchronization state.
The customer selects a valid appointment and provides required information.
A calendar event can be created with the approved details.
The appointment type checks connected availability before offering times.
A correctly marked busy event can block that time from new bookings.
The customer-facing appointment may reflect the updated time.
Moving the event may update the connected booking when the sync remains active.
The appointment status should follow the approved cancellation path.
Removing or cancelling the event may update the connected booking.
Manual events are part of the live availability system. An event marked free may not protect the time, while an incorrectly timed busy event can hide a valid appointment slot.
Attach the connection to the intended event
Connecting the Google account is only the first step. Confirm the appointment type uses the selected calendar and that the appropriate AI Agent is allowed to book it.
Define the event, schedule, resources, required questions and confirmation rules before relying on calendar availability.
Keep the calendar accurate
The connected calendar becomes part of the customer-facing booking system. Maintain it with the same care as the service schedule and appointment rules.
Blocks appointment time
Use the correct busy status for meetings, closures, travel, preparation or other unavailable periods.
May leave time bookable
Use free status only when the event should not prevent the appointment type from offering that period.
Must agree across systems
Confirm the calendar, appointment type and displayed customer time refer to the same intended moment.
Needs an active maintainer
Assign responsibility for schedule changes, access renewal, removed calendars and staff transitions.
Test the complete synchronization path
Use synthetic customer information and inspect both ConvoRev and the target Google Calendar. Remove test events after recording the results.
A valid appointment completes with the required customer details.
The event appears on the correct calendar with the intended owner.
The confirmation contains the approved service and meeting information.
Title, customer details, location and instructions are accurate.
The customer sees an unambiguous date, time and timezone.
The calendar event represents the same instant.
The AI Agent does not offer a period blocked by a busy event.
The blocked time is absent from valid appointment options.
The approved change process updates the customer expectation.
Booking and calendar records reach the intended status.
The AI Agent does not imply that an unverified booking completed.
No partial or duplicate event is treated as confirmed.
Close the test cleanly
Record the test date, account, appointment type, timezone and observed result. Remove synthetic contacts and calendar events when they are no longer needed.
Review access when the business changes
Password or security changes, revoked permissions, removed calendars and account-policy changes can interrupt synchronization. Treat the connection as a maintained business dependency.
Staff or owner change
Confirm the business still controls the Google account and that an active person owns maintenance.
Security change
Check the visible connection state after password, sign-in or account-policy updates.
Calendar change
Verify the selected calendar still exists, remains visible and uses the intended timezone.
Service change
Retest when appointment types, durations, schedules, locations or resources change.
Diagnose the connection by layer
A booking does not appear
Check the connection state, selected Google account, calendar visibility, event-type attachment and whether the booking actually completed.
A busy time is offered
Confirm the event is on the connected calendar, uses the correct date and timezone, and is marked busy.
The time is shifted
Compare the business calendar timezone, appointment-type timezone and customer confirmation before changing the event.
Events are duplicated
Review existing connections and event ownership. Avoid adding another connection until the original path is understood.
Sync stopped after working
Look for revoked access, security changes, removed calendars, ownership changes or updated account policies.
A change did not transfer
Confirm the event remains connected and inspect the current sync state before repeating the action.
Google Calendar connection
Which Google account should I connect?
Use the approved account that owns or manages the business calendar for the deployment. Avoid choosing an account only because it is already open in the browser.
Does connecting Google immediately create appointment availability?
No. Attach the selected calendar to the intended appointment type and confirm that the correct AI Agent is allowed to book that event. Then test the resulting availability.
Does ConvoRev need my Google password?
No. Use the approved authorization flow and review the account and permissions shown in that window. Do not email passwords, recovery codes or authorization codes.
Why was a time blocked?
Check the appointment schedule, notice and buffer rules, then review busy events on the connected calendar. Confirm dates, times and timezones before changing the configuration.
What should I do when a team member leaves?
Confirm the business retains control of the Google account and calendar. Assign a new connection owner, review permissions and retest the affected appointment types.
How do I confirm synchronization is working?
Create a controlled test booking, inspect the destination event, block a time with a busy event, and test a move or cancellation. Use synthetic information and remove the test records afterward.
Send the connection and test details
Include the ConvoRev account, AI Agent, appointment type, calendar name, timezone, affected time, exact test path, visible connection state or error and what appeared in the destination. Do not send passwords, authorization codes or unnecessary private customer information.