Google Calendar logoConnects LegalVoice to a firm-configured Google Calendar account. No official partnership is implied.

Google Calendar integration · OAuth scheduling path available

Connect LegalVoice to Google Calendar with explicit data and workflow boundaries.

LegalVoice can use a firm-connected Google Calendar account to check configured availability, offer returned consultation times, create confirmed events, and cancel supported bookings. The firm controls calendars, appointment rules, timezone, duration, buffers, and who receives each event.

A business team collaborating around a shared workflow in a modern office. Make intake operational
Photo by Vitaly Gariev on Unsplash
What the Google Calendar workflow supports

LegalVoice describes only the actions supported by the configured Google Calendar path. Availability still depends on the firm’s account, permissions, field mappings, and enabled workflow.

  • Read configured availability and filter out unavailable or past times.
  • Offer only slots returned by the scheduling service.
  • Create a consultation event after the caller confirms a specific time.
  • Cancel a supported booking when the firm’s workflow permits it.
What data is exchanged

The connector should move only the fields required for the approved intake or follow-up action and preserve provider identifiers and result states for review.

  • Client name and approved contact details.
  • Appointment type, start and end time, office timezone, and consultation format.
  • Configured staff calendar, event description, location, and meeting instructions.
  • Calendar event ID, booking status, and notification results.
How to configure Google Calendar

Begin with the narrowest useful connection, test it with controlled records, and enable additional actions only after the firm reviews the result.

  • Connect the firm’s Google account through the LegalVoice OAuth flow.
  • Choose the calendars, office timezone, appointment types, durations, and availability rules.
  • Review meeting format, staff ownership, buffers, and confirmation language.
  • Run a test availability check and booking before enabling caller scheduling.
Known limitations and review boundaries

A connected credential is not blanket permission to read or write every record. Provider success, partial success, and failure must remain visible to staff.

  • LegalVoice can schedule only against connected calendars and the availability rules the firm configures.
  • A displayed slot is not booked until the calendar creation call succeeds.
  • Meeting links, attendee notifications, and shared-calendar access depend on account settings and granted scopes.
Example Google Calendar workflow

This example shows the operational sequence without using customer data or promising that every firm uses the same configuration.

  • A qualified caller asks for a consultation and the agent requests availability from the connected calendar.
  • LegalVoice offers a small set of returned times in the office timezone.
  • The caller chooses one slot and the booking tool creates the event.
  • The agent confirms the consultation only after the calendar reports success.

checklist

Google Calendar launch checklist

Confirm these items before enabling the integration for production records.

Account owner Name the firm administrator responsible for the connected account and provider permissions.
Authentication Connect the firm’s Google account through the LegalVoice OAuth flow.
Data map Approve the exact objects, fields, provider IDs, and source-of-record rules.
Allowed actions Enable only the read or write actions the firm has approved and tested.
Failure handling Define who reviews rejected, partial, duplicate, expired-token, and permission-denied results.
Controlled verification A qualified caller asks for a consultation and the agent requests availability from the connected calendar.