The email thread lives on the job, not in someone's Outlook.

Connect your mailboxes and every message with a customer shows up inside their record: the full history, who owes a reply, what is unread, which attachments arrived. Reply from the job. AI summarises the long thread, drafts the response, sorts what just landed, and picks the right template. And when you want it handled without you, the text agent answers inbound email on its own.

Get Demo See it change live

Help desk with customer emails as tickets, each with an owner and an SLA clock, and the customer's jobs alongside.

Plain English

Describe the change. It goes live.

EmailPlain English

Threads on the record

Every message to and from that customer, in order

Reply from the job

Inline composer on the message timeline

Nothing forwarded

The history stops living in one person's inbox

Live in

Immediateno forwarding, no digging

Built your way

Email, treated as part of the job

Not a separate tool your team alt-tabs to, and not a mailbox rule. The conversation sits where the work sits.

Threads inside the record

The same element works two ways: an email history on a contact, job or customer screen, or a standalone inbox with search and a compose button. Rows read like a real inbox line, unread state, a preview of the newest message, who owes a reply, attachment and delivery-failure signals.

Your existing mailboxes

Connected over IMAP and SMTP, so it is the address your customers already write to. An admin sets them up once in the portal; your team just sees the threads.

Summarise the long thread

The escalation that ran to forty messages across three people, reduced to what was agreed and what is still open, before you join the call about it.

Draft the reply

AI writes the response in your template and your tone, and a person sends it. The draft is a starting point, not an outbound message.

Classify what lands

Quote request, complaint, supplier invoice, scheduling change. Sorted as it arrives so the right person sees it rather than everyone seeing everything.

Templates that suggest themselves

AI produces a template from how you already write, and picks the right existing one for the thread in front of you.

The attachment becomes the job

The PO, the site instruction, the signed quote: read out of the email and filed against the work, instead of re-saved by hand and re-uploaded.

Findable a year later

Because the thread is on the record rather than in a mailbox, the person who answers the query in twelve months is not the person who has to remember it.

Answered on its own, when you want

The text agent handles inbound email end to end: it reads the message, finds the job, and replies. Anything that moves money or cancels work stages a preview and waits for a typed confirmation.

See it built around how your team already works.

Get Demo

Shaped to your trade

Your business doesn't run like the template. Neither does Fieldproxy.

Facilities

The tenant emails rather than raising a ticket. It becomes a work order anyway.

Commercial HVAC

The PO arrives as a PDF attachment. The fields land on the job, not in a folder.

Fire & Safety

Certificates and remedial approvals stay attached to the asset that needs them.

Field Services

The customer's whole history is on the record when the new person answers.

Platform

Everything you need, in one platform

A complete field service suite, explore what's included.

Want it running on your jobs? We set it up around them.

Get Demo

Integrations

Plays nicely with the tools you already use

IMAP / SMTP

Your existing mailboxes

Gmail

Threads + attachments

Outlook

Threads + attachments

QuickBooks

Invoice + payment sync

Automations

Trigger work off an inbound email

Zapier

Anything else

AI agents

The AI agents that work the inbox

Reading, drafting and classifying are one thing. Answering on its own is a decision you make per agent.

Text Agent

Answers inbound email against the real job record, reschedules it, and stages anything high-stakes for a typed confirmation.

Document Intelligence

Reads the PO, quote or warranty claim that arrived as an attachment and pulls out the fields.

Knowledge Agent

Answers the policy and pricing questions in the thread from your own documents, rather than from a guess.

Explore all AI agents →

See it built around how your team already works.

Get Demo

Bring the inbox you run your operation out of

On the mapping call we walk how work actually arrives, and how much of it arrives as email. Then we configure it on your workflows.

Get Demo See pricing

Also works from ChatGPT, Claude and Copilot in Teams

Fieldproxy's MCP server lets your team run the day and change the software itself from the AI assistant they already use, with a confirm step before anything changes.

The email thread lives on the job, not in someone's Outlook.

Describe the change. It goes live.

Email, treated as part of the job

Threads inside the record

Your existing mailboxes

Summarise the long thread

Draft the reply

Classify what lands

Templates that suggest themselves

The attachment becomes the job

Findable a year later

Answered on its own, when you want

Your business doesn't run like the template. Neither does Fieldproxy.

Facilities

Commercial HVAC

Fire & Safety

Field Services

Everything you need, in one platform

Customer Communications

Customer Portals

Work Orders

Contracts & Invoices

Reporting & Dashboards

Mobile App

Plays nicely with the tools you already use

The AI agents that work the inbox

Text Agent

Document Intelligence

Knowledge Agent

Bring the inbox you run your operation out of