Does it use my own templates?

Yes. Estimates, proposals and documents are generated from the workspace's templates, not free text.

Quotes and proposals · Fieldproxy MCP

Quotes and proposals from your own templates, 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

Quotes and proposals from ChatGPT, Claude or Copilot: how does it work?

Fieldproxy's MCP server lets Claude, ChatGPT or Copilot generate estimates and PDF documents from your templates, preview and issue proposals, re-issue a proposal, list quotes that need a follow-up and mark stale ones lost. Issuing or sending is a proposal you confirm first.

Last verified September 27, 2026

Real requests

What people ask, and the tools it calls

You ask	Fieldproxy tools	You get
“Estimate a replacement RTU for Northwind Site 14”	list_estimate_templates, generate_estimate	An estimate from your template and rates
“Preview and send the proposal”	preview_proposal, issue_proposal	A proposal preview, issued on confirm
“Which quotes over $5,000 need a follow-up?”	quotes_to_follow_up	Open quotes with their age and value
“Mark quotes older than 90 days as lost”	mark_quotes_lost	A bulk update, applied on confirm

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 my own templates?: Yes. Estimates, proposals and documents are generated from the workspace's templates, not free text.

Quotes and proposals, from the chat

Book a demo