Jobs on Outlook calendars, busy time blocking dispatch, and the service mailbox turned into jobs
Fieldproxy connects to Outlook and Microsoft 365 through Microsoft Graph and does four things. Scheduled jobs appear on the technician's or office user's Outlook calendar and move when the job is rescheduled. Busy blocks in Outlook are read, so jobs aren't booked over meetings or leave. Emails to a shared service address, such as service@, can create jobs, with attached PDF work orders read by AI. And confirmations and reports go to customers from your own Microsoft 365 address. In short: jobs out, busy time in, work orders in from the mailbox, customer email out.
Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces the spreadsheet, the shared calendar and the inbox you dispatch from today; it is not a layer on top of another field service tool. One price per company, unlimited users.
See your Outlook calendars and mailbox connected
Tell us how work arrives and how you schedule today. We set it up on your own job types before you commit.
What syncs
Four connections, each with one owner
Built on Microsoft Graph (Mail and Calendar). Fieldproxy owns the schedule and the job; Outlook owns people's days and your mailbox. Each record has one side that is the master, which is what stops the two systems overwriting each other.
| Object | Direction | When |
|---|---|---|
| Scheduled jobs | Fieldproxy โ Outlook calendar | When a job is scheduled and assigned, it appears on that person's Outlook calendar, and it moves when the job is rescheduled in Fieldproxy. |
| Deleted jobs | Fieldproxy โ Outlook calendar | Deleting a job removes its calendar event. |
| Busy time | Outlook calendar โ Fieldproxy | Busy blocks are read so jobs aren't booked over meetings, training or leave. |
| Service mailbox emails | Outlook mailbox โ Fieldproxy | Emails to a shared service address you choose can create jobs. Attachments such as PDF work orders are read by AI and the details placed on the job. |
| Customer emails | Fieldproxy โ customer, via Microsoft 365 | Confirmations and visit reports are sent from your own Microsoft 365 address, so replies come back to your mailbox. |
| Edits made to the event in Outlook | Set up per account | The schedule is owned by Fieldproxy, so jobs are rescheduled there. Whether an edit made in Outlook is read back is agreed at setup. |
Only the calendars and mailboxes you pick are read. Teams on Google use the Google Calendar connection, which works the same way.
The workflow
From an email in the service mailbox to a finished visit
How a typical job runs with the Outlook connection. Which emails create jobs and which calendars are connected are agreed at setup.
- 1
A work order arrives by email
Customer, to your service mailbox
A facilities client emails service@ with a PDF work order attached, as they always have. Nothing changes on their side. - 2
The email becomes a job
Fieldproxy, read from the mailbox
The email and the PDF are read by AI. The customer, site, requested work and the client's reference number are placed on a new job. If the site can't be matched, the job waits for the office with the reason. See email management. - 3
Busy time is already on the board
Fieldproxy, read from Outlook
Meetings, training and leave on each person's Outlook calendar show as unavailable time, so the dispatcher sees who is really free. - 4
The job is assigned
Dispatcher, helped by the Dispatch agent
The Dispatch agent suggests who should go by skills, location and free time. The dispatcher approves, and every change can be undone. - 5
It lands on the Outlook calendar
Fieldproxy, written to Outlook
The job appears on the technician's Outlook calendar with the site and job details, and moves if the job is rescheduled in Fieldproxy. - 6
The customer hears from your address
Fieldproxy, sent through Microsoft 365
The booking confirmation goes from your own Microsoft 365 address, so a reply comes back to your mailbox, not to a no-reply address. - 7
The visit runs in the app, and the report goes out
Technician, Android or iOS
GPS check-in, the checklist, photos, parts and the customer signature in the Fieldproxy app, offline if needed. The visit report is emailed to the client from your address.
See your own service emails become jobs before you commit.
Get DemoWhat stays where
Outlook for mail and people's days. Fieldproxy for the work.
Nobody gives up Outlook. What moves out of it is the job: the part that used to live in a forwarded email and a shared calendar.
| Stays in Outlook and Microsoft 365 | Lives in Fieldproxy |
|---|---|
| Meetings, leave, training and everything else in people's days | Jobs, schedules, assignments and the dispatch board |
| The service mailbox your customers already email | The job each email becomes, with its customer, site and attachments |
| Your Microsoft 365 sending address and its history | Which emails go out, when, and with which template |
| Internal email between staff | Customer notes, visit reports, photos, checklists and signatures |
| Contacts and address books in Outlook | Customers, sites and assets used for jobs and invoices |
Why the inbox can't be the job list
An inbox can't tell you which jobs are late, who has the part, which visits are missing photos or which finished jobs haven't been invoiced. A job list can.
What the job carries
Your own stages, forms and checklists, skills and certifications, van stock, the visit report and the invoice, with a customer portal where clients see their jobs.
Where the money goes
Invoices with payment links and Tap to Pay through Stripe, and two-way sync with QuickBooks, Xero and Sage.
Worked example
A facilities contractor on Microsoft 365
Demo data with fictional names. Northgate Facility Services maintains offices and shops for property managers. Every client sends work orders by email, and the whole company runs on Microsoft 365.
- 08:12: Elm Street Property Management emails service@northgate with work order PO-4471 attached: a leaking roof drain at Unit 3, Riverside Retail Park.
- 08:13: a job appears in Fieldproxy with the client, the site, the description and PO-4471 on it. The PDF is attached to the job.
- 08:30: the board shows engineer Tom Okafor in a toolbox talk until 10 (from his Outlook calendar). The Dispatch agent suggests him for 10:30, the nearest qualified engineer; the dispatcher approves.
- 08:31: the job appears on Tom's Outlook calendar at 10:30. Elm Street gets a confirmation from service@northgate, quoting PO-4471.
- 10:42: Tom checks in by GPS in the Fieldproxy app, completes the roof drain checklist with before and after photos, and records the parts used.
- 11:30: the visit report goes to Elm Street from Northgate's address. The job is ready to invoice against PO-4471.
Setup
Connected and live within a day
Your Microsoft 365 admin, or each user, approves access. The rest is done by the Fieldproxy team.
- 1
A short call
How work arrives today, which mailbox it arrives in, who is scheduled, and what customers should receive from you. - 2
Approve access with Microsoft sign-in
Each user approves access, or an admin approves it for the whole tenant. Fieldproxy never sees a Microsoft password. - 3
Pick the calendars and mailboxes
Choose which calendars receive jobs and are read for busy time, and which shared mailbox can create jobs. Nothing else is read. - 4
Choose which emails create jobs
The rules are agreed with you, and everything else stays in the mailbox. A few of your own past work-order emails are used to check what the AI reads. - 5
Test, then go live
Run real emails and jobs through, check the calendars and the customer emails, and go live. Existing customers and sites come across with free, assisted migration.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- Your company runs on Microsoft 365 and people plan their days in Outlook.
- Work orders arrive by email, often as PDFs, and someone retypes them today.
- Jobs get booked over meetings, training or leave the dispatcher couldn't see.
- You want customer emails to come from your own domain.
- You want Copilot as well as Claude or ChatGPT to work in your field data.
Not the right fit when
- You only need meeting bookings in Outlook. A booking tool is simpler.
- You want Outlook to stay the master schedule. Fieldproxy owns the schedule.
- You want to keep another field service system and add an Outlook sync to it. Fieldproxy replaces the field service tool rather than sitting on top of one.
- Your mail runs only on an on-premises Exchange server. Check with us first.
See it built around how your team already works.
Get DemoStraight answers
Outlook and field service: questions we get asked
Is the Outlook calendar sync two-way?
If someone moves the job's event in Outlook, does the job move?
Can emails to service@ create jobs?
Which mailboxes and calendars does Fieldproxy read?
Do customer emails come from Fieldproxy or from us?
Does it work with on-premises Exchange?
Do technicians need Outlook on their phone?
Can we use Microsoft Copilot with Fieldproxy?
Some of our team uses Google Calendar. Is that a problem?
How long does it take to set up?
Related
More on scheduling, email and AI assistants
See every connection on the integrations page. For Copilot, Claude or ChatGPT, see Fieldproxy's MCP server and Fieldproxy in Copilot.
Keep Outlook. Stop dispatching from the inbox.
Send us a few of your real work-order emails. We show them becoming jobs on your own setup.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.