Jobs on every technician's Google Calendar, and their busy time blocking dispatch
Fieldproxy puts every scheduled job on the assigned technician's Google Calendar, with the customer, address, contact and job details in the event, and moves the event when the job is rescheduled in Fieldproxy. In the other direction, appointments already on that calendar (leave, training, a personal appointment) block the time in Fieldproxy, so the dispatcher and the Dispatch agent can't book a job on top of them. The schedule itself lives in Fieldproxy; Google Calendar is where people see it.
Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces the shared spreadsheet or the colour-coded calendar you schedule from today; it is not a layer on top of another field service tool. One price per company, unlimited users.
See your team's calendars connected
Tell us how you schedule today. We set it up on your own job types and technicians before you commit.
What syncs
Jobs go out. Busy time comes in.
Two directions, each with one owner. Fieldproxy owns the schedule and writes it to Google Calendar. Google Calendar owns everything else in a person's day, and Fieldproxy reads it as busy time. Keeping each side the owner of its own data is what stops two systems overwriting each other.
| Object | Direction | When |
|---|---|---|
| Scheduled jobs | Fieldproxy โ Google Calendar | When a job is scheduled and assigned, an event is created on the technician's calendar. |
| Reschedules and reassignments | Fieldproxy โ Google Calendar | When the job's time or technician changes in Fieldproxy, the event moves to the new time or the new person's calendar. |
| Job details in the event | Fieldproxy โ Google Calendar | Customer, site address with a map link, site contact, job number, job type, priority and the office's instructions, written when the event is created or updated. |
| Busy time and personal appointments | Google Calendar โ Fieldproxy | Existing events on the connected calendar show as unavailable time in Fieldproxy, so jobs aren't booked over them. |
| Cancelled or deleted jobs | Fieldproxy โ Google Calendar | Set up per account: the event is removed or marked cancelled, as agreed at setup. |
| Edits made to the event in Google | Set up per account | The schedule is owned by Fieldproxy. Whether a time change made directly in Google is read back is agreed at setup; by default, reschedule in Fieldproxy. |
The same pattern runs on the Outlook and Microsoft 365 connection, so a team split across Google and Microsoft calendars is scheduled from one board.
The workflow
From booking to the technician's phone, step by step
A typical day with the calendar connection in place. Which calendars are connected and what counts as busy are agreed at setup.
- 1
Technicians keep their calendar as it is
Technician or office
Leave, training, a school run, a doctor's appointment: whatever is already on the connected Google Calendar. Nobody re-enters it into Fieldproxy. - 2
Busy time shows on the dispatch board
Fieldproxy, read from Google
Those events show as unavailable time against the technician. The dispatcher sees the gap before offering the slot to a customer, not after the technician calls to say they can't make it. - 3
A job is booked into free time
Dispatcher, helped by the Dispatch agent
The Dispatch agent suggests who should go, using skills, location and free time, and leaves out anyone whose calendar is blocked. The dispatcher approves, and every change can be undone. - 4
The event appears on the technician's calendar
Fieldproxy, written to Google
An event is created on the assigned technician's Google Calendar with the customer, address and map link, the site contact, the job number and the instructions. It shows on their phone like any other appointment. - 5
Plans change, and the calendar follows
Dispatcher
A job moved to the afternoon or handed to another technician is changed once, in Fieldproxy. The event moves to the new time or to the other person's calendar, and the customer can be sent the new time. - 6
The work is done in the Fieldproxy app
Technician, Android or iOS
The calendar tells them where to be. The Fieldproxy app runs the visit: GPS check-in, the checklist for this job type, photos, parts and the customer signature. It works offline and syncs when signal returns.
See your technicians' calendars and your dispatch board side by side.
Get DemoWhat stays where
Google Calendar for the person's day. Fieldproxy for the work.
The calendar is a view of the schedule, not the schedule. Everything the job needs to be done properly, and paid for, lives in Fieldproxy.
| Stays in Google Calendar | Lives in Fieldproxy |
|---|---|
| Personal appointments, leave, training, internal meetings | Jobs, visits, schedules, assignments and the dispatch board |
| The technician's own view of their day on a phone they already use | The job itself: checklist, photos, parts, signature, GPS check-in |
| Reminders the technician sets for themselves in Google | Customer notifications: confirmations, reminders and on-my-way messages |
| Calendars for people who never touch field work | Customers, sites, assets, quotes, invoices and payments |
| Sharing a calendar with a subcontractor's office, if you choose | Subcontractor access to their own jobs, by login or a job link |
Why the schedule can't live in the calendar
A calendar knows that Tuesday at 9 is taken. It doesn't know the job needs a gas-certified technician, that the part is on another van, or that the customer wants a text when someone is on the way.
What Fieldproxy adds to a booking
Your own stages, forms and checklists, skills and certifications, van stock, customer notifications and the invoice at the end.
Who still needs the calendar
Technicians who plan their life on Google, office staff who book their own visits, and subcontractors who want your jobs next to everyone else's.
Worked example
One Tuesday at a demo HVAC company
Demo data with fictional names. Harbour Line Heating runs four technicians who all use Google Calendar on their phones. The office schedules from Fieldproxy.
- Monday evening: technician Priya Nair adds a 2 pm dentist appointment for Tuesday to her own Google Calendar.
- Tuesday 8 am: on the Fieldproxy board, Priya's afternoon shows a block from 2 pm. Nobody had to tell the office.
- Tuesday 9:40 am: a no-heat call comes in from the Delgado household. The Dispatch agent suggests Priya for 11 am (closest, certified, free before her appointment) and the dispatcher approves.
- Tuesday 9:41 am: โNo heat, Delgado, 14 Ferry Roadโ appears on Priya's Google Calendar at 11 am, with the address, the map link, the contact's number and the job number.
- Tuesday 10:15 am: the Delgados ask for 12 instead. The dispatcher moves the job in Fieldproxy; the event moves to 12 and the customer gets the new time.
- Tuesday 12:05 pm: Priya checks in by GPS in the Fieldproxy app, works through the no-heat checklist, adds photos and the part used, and the customer signs.
- Tuesday 2 pm: she is at the dentist. No job was ever offered for that slot.
Setup
Connected and live within a day
Each person, or your Google admin, approves access once. The rest is done by the Fieldproxy team as part of getting you live.
- 1
A short call about how you schedule
Who is scheduled, which calendars they use, what should count as busy, and what the event should say. - 2
Approve access with Google sign-in
Each technician or your Google admin approves the connection with OAuth. Fieldproxy never sees a Google password, and access can be revoked from the Google account at any time. - 3
Choose the calendars
Pick which calendar receives jobs and which calendars are read for busy time, per person. Subcontractors can be connected the same way. - 4
Agree the event and the edge cases
What goes in the event title and description, and how cancellations and edits made in Google are handled for your account. - 5
Test with real jobs, then go live
Book, move and reassign a few real jobs and check each calendar. Your existing customers and jobs come across with free, assisted migration.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- Your technicians already live in Google Calendar and you don't want to take that away.
- Jobs keep getting booked over leave, training or appointments the office didn't know about.
- You schedule from a shared Google Calendar today and have outgrown it: you need checklists, photos, stock and invoices on the job.
- Subcontractors want to see your jobs on their own calendar.
- Some of the team is on Google and some on Microsoft 365.
Not the right fit when
- You only want a booking widget that drops appointments into a calendar. A scheduling app is simpler and cheaper.
- You want Google Calendar to stay the master schedule. Fieldproxy owns the schedule; the calendar shows it.
- You want to keep another field service system and only add a calendar sync. Fieldproxy replaces the field service tool rather than sitting on top of one.
See it built around how your team already works.
Get DemoStraight answers
Google Calendar and field service: questions we get asked
Does Fieldproxy sync with Google Calendar both ways?
If a technician drags the event to a new time in Google Calendar, does the job move?
What shows in the calendar event?
Does the office see what my personal appointments are?
Do technicians need Google Calendar to use Fieldproxy?
Can subcontractors see their Fieldproxy jobs in their own Google Calendar?
Does it work with Google Workspace and personal Gmail calendars?
What about Outlook users on the same team?
Can I schedule jobs from Claude or ChatGPT and have them land on the calendar?
How long does setup take?
Related
More on scheduling, and the rest of the stack
See every connection on the integrations page, or connect Claude, ChatGPT or Copilot through Fieldproxy's MCP server to book and move jobs from a chat, with a confirm step.
Keep the calendar. Give the schedule a proper home.
Tell us how you schedule today. We show it running with your own technicians and job types.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.