TL;DR:
- Bidirectional sync means your jobs appear in Google Calendar and your personal Google events appear in Exoserva's scheduling view — both directions work
- Incremental sync (using Google's syncToken) keeps updates fast: only changed events transfer, not your entire calendar every time
- Webhooks deliver real-time updates when calendar events change — no polling, no delays
- Outlook Calendar is also supported with the same sync architecture
- Timezone handling is built in — jobs scheduled in one timezone display correctly for technicians in others
Why Calendar Sync Matters for Contractors
Scheduling without visibility into technicians' personal calendars creates the most common type of dispatch conflict: assigning someone to a job during a dentist appointment, a school pickup, or a half-day they blocked off. The technician either scrambles or the job gets reassigned at the last minute.
At the same time, technicians want to see their work schedule in the calendar app they already use every day — not a separate portal they have to log into. If the job is in Google Calendar, it's on their phone, on their laptop, in their watch complications.
Exoserva's calendar sync solves both problems. Personal availability flows in. Job schedules flow out. The scheduling view in Exoserva reflects reality.
How the Sync Works
Bidirectional Sync
The sync operates in both directions:
Exoserva → Google Calendar: When a job is created, assigned to a technician, or rescheduled in Exoserva, the corresponding event is created or updated in the technician's Google Calendar. Cancellations remove the event.
Google Calendar → Exoserva: When a technician creates a personal event in Google Calendar (a vacation day, a personal appointment, a blocked-off morning), that event appears in Exoserva's scheduling view as unavailable time. Dispatchers see the block before assigning the job, not after.
This bidirectionality is what makes the integration genuinely useful. One-way sync — jobs to calendar only — still leaves dispatchers blind to personal availability.
Incremental Sync with syncToken
Google Calendar's API provides a syncToken after each sync operation. On the next sync, Exoserva sends that token back to Google, and Google returns only events that changed since the last sync — not the entire calendar.
For a busy technician with years of calendar history, this is the difference between a 50ms sync operation and a 5-second one. Incremental sync keeps the integration fast and doesn't burn through API quota.
Real-Time Updates via Webhooks
Beyond scheduled syncs, Exoserva registers webhooks with the Google Calendar API. When an event changes in Google Calendar — a rescheduled personal appointment, a new block, a deleted event — Google pushes a notification to Exoserva immediately. The scheduling view updates without waiting for the next sync cycle.
This matters most for same-day scheduling. If a technician adds a block to their Google Calendar at 9 AM, the dispatcher sees it before booking a 10 AM job — not after the conflict already happened.
Timezone Handling
Field service businesses often span multiple timezones. A company headquartered in Dallas might have technicians working in Mountain Time. A national operation might have jobs and techs across four time zones.
Calendar sync handles this at the event level. Jobs are stored with their timezone in Exoserva. When exported to Google Calendar, the event carries the correct timezone metadata. Google Calendar displays the event in the technician's local time. A job at 2:00 PM Central shows as 1:00 PM Mountain for a technician in Denver — automatically, without anyone manually converting.
Outlook Calendar Support
The same integration architecture works for Microsoft Outlook Calendar. If your technicians use Outlook — common in markets where businesses run on Microsoft 365 — they can connect Outlook instead of (or in addition to) Google Calendar.
The sync behavior is the same: bidirectional, incremental, with real-time updates. Setup follows the same pattern through Exoserva's calendar integration settings.
Setting Up Google Calendar Sync
Step 1: Connect Your Google Account
In Exoserva, go to Settings → Integrations → Calendar. Select Google Calendar and click Connect.
You'll be directed to Google's OAuth consent screen. Sign in with the Google account you want to connect and grant the requested calendar permissions. Exoserva requests read/write access to your calendar to support bidirectional sync.
After authorization, you'll return to Exoserva with the integration active.
Step 2: Choose Sync Direction (Per Technician)
If you're setting up sync for a team, each technician connects their own Google account through their Exoserva profile. They control which personal calendars to include in the availability block.
As the account owner or admin, you can see sync status per technician in the team scheduling view.
Step 3: Verify the First Sync
After connecting, Exoserva performs an initial full sync to pull existing calendar events. Depending on calendar size, this may take a few minutes. After the initial sync, all subsequent updates use the incremental syncToken approach.
Check the scheduling view in Exoserva to confirm that personal events from Google Calendar appear as blocks, and create a test job to confirm it appears in the connected Google Calendar.
Handling Sync Conflicts
Job moved in Exoserva vs. event moved in Google Calendar simultaneously
If a job is rescheduled in Exoserva at the same moment a technician manually moves the event in Google Calendar, Exoserva's version wins. Exoserva is the authoritative source for job scheduling. Google Calendar reflects what Exoserva knows — if there's a conflict, the Exoserva record takes precedence and the Google Calendar event updates accordingly.
Deleted events in Google Calendar
If a technician deletes a job event from their Google Calendar (not cancels the job in Exoserva), the job still exists in Exoserva. The calendar event will be re-created on the next sync cycle. To cancel a job, do it in Exoserva — the deletion will then propagate to Google Calendar.
Expired webhook channels
Google Calendar webhooks expire after a maximum of 7 days and must be renewed. Exoserva handles this automatically, renewing webhook registrations before they expire. If you see sync delays, check the integration status panel in settings — it will indicate if webhook renewal failed.
Best Practices
Have each technician connect their personal Google account, not a shared company account. Bidirectional sync is only useful when it reflects each individual's actual availability.
Use calendar blocking consistently. Encourage technicians to block personal time in Google Calendar rather than telling the dispatcher verbally. Once it's in the calendar, Exoserva sees it automatically.
Audit sync status periodically. The integration settings panel shows last sync time and status per connected account. Spot-check this monthly to catch any OAuth tokens that may have expired or permissions that may have been revoked.
FAQ
What if a technician doesn't use Google Calendar or Outlook? Calendar sync is optional per technician. Technicians who don't connect a calendar simply don't have personal blocks imported. Dispatchers should manually note their availability in those cases.
Can I sync multiple Google calendars (work and personal)? The integration connects to the primary calendar on the authorized Google account. If a technician maintains separate work and personal calendars within the same Google account, they can configure which calendars to include in the sync settings.
What happens to historical events when I first connect? The initial sync imports existing future events from Google Calendar. Historical (past) events are not imported — Exoserva focuses on upcoming availability for scheduling purposes.
Related Guides
- AI Dispatch: Intelligent Technician Routing
- GPS Tracking: Setup, Mileage, and ETA
- Setting Up AI Voice for Your Business
Ready to Eliminate Scheduling Conflicts?
Calendar sync takes 5 minutes per technician to set up and eliminates the most common source of same-day dispatch problems. Personal availability in, job schedule out — automatically, in real time.