Does it use live technician locations?

Yes, where the workspace tracks them: the assistant can read live technician locations and routes, within the signed-in user's permissions.

Route planning · Fieldproxy MCP

Plan tomorrow's routes by asking

From Claude, ChatGPT or Copilot in Teams, on your live field service data, with a confirm step before anything changes.

Book a demo How it connects

Reply to Claude...

Fieldproxy

ClaudeChatGPTCopilot in Microsoft Teams

Illustration of Fieldproxy's MCP tools inside Claude, ChatGPT and Copilot. Names and data are examples.

Short answer

Route planning from ChatGPT, Claude or Copilot: how does it work?

Fieldproxy's MCP server gives Claude, ChatGPT and Copilot route tools: plan daily routes per technician, check drive times between sites, see live technician locations and routes, geocode addresses and find which service zone a job falls in. Planned routes are applied only after you confirm.

Last verified September 27, 2026

Real requests

What people ask, and the tools it calls

You ask	Fieldproxy tools	You get
“Plan tomorrow's routes for the North region”	plan_day_routes, apply_schedule	Routes per technician with drive time, applied on confirm
“How long from the depot to the Riverside site at 8am?”	drive_time	The drive time
“Where are my technicians right now?”	technician_locations, technician_route	Live locations and today's route
“Which zone is 42 Harbour Road in?”	geocode_address, zones_for_location	The address and its service zone

The part nobody else does

Your AI can change the software, not just the data

Every other field service connector we checked (September 27, 2026) reads records and, at most, edits a few of them. Fieldproxy's MCP server can also build: new fields, screens, tables, automations and agents, made in a sandbox copy of your workspace and live only when you approve.

Add a field

"Add a warranty expiry date to every job." The column, the form field and the list column, in one ask.

Build a screen

"Build a subcontractor compliance screen that flags missing insurance." A new screen on your real data.

Wire an automation

"Email the service manager 30 days before a warranty runs out." Saved switched off until you turn it on.

Create an agent

Voice and text agents: validate, simulate against test conversations, then enable.

Add your own tools

Saved SQL tools such as "a customer's overdue invoices", which every AI connection in the workspace can then call by name.

Roll back anything

Every build is checked against your database before it saves, promoted from the sandbox when you approve, and can be rolled back.

Guardrails

Your AI proposes. A person confirms.

Built for operations with branches, teams and an IT review, not a single login.

Nothing changes on one call

Every write, send or action is a proposal the user confirms within 30 minutes. Writes can be undone. More than 5 rows needs bulk permission, and more than 1,000 is refused.

Keys scoped like API keys

Limit a key to certain tables, certain rows ("only the North region's jobs"), hidden columns, insert/update/delete, and an expiry from 1 hour to 90 days. Postgres enforces the row limits.

Builds save as drafts

Apps and automations are checked against the database before they save, new automations and agents are saved switched off, and public apps are never changed.

Sends are limited

Email goes only from the user's own mailbox, at most 20 sends an hour per key, inside the workspace's quiet hours. A sandbox never sends.

Everything is logged

Every call is written to an audit log with the tool, key, person and outcome. Administrators see every key and connected app, and revoking one applies on the next request.

FAQ

Questions

Does it use live technician locations?: Yes, where the workspace tracks them: the assistant can read live technician locations and routes, within the signed-in user's permissions.

Route planning, from the chat

Book a demo