FieldproxyFieldproxy

Text Agent

Your texts and emails, answered against real data.

A site contact texts "can you move Thursday's PPM visit to Friday?" The agent finds that job in your system, checks whether Friday works inside the contract window, moves it, and confirms. Not a canned auto-reply and not a chatbot that takes a message.Same brain as the voice agent. The tools, the roles and the safety rails are shared code, so a fix on one channel is a fix on both.

See it on your workflowThe voice channel

SMS and email

Two channels, one agent

SMS

Comes in through the SMS number you already use, so opt-outs, metering and threading are the ones the platform already handles.

Email

Comes in through a connected mailbox. The agent reads the message, finds the job, and replies on the thread. Most field service tools cannot answer an email at all.

Tools, not templates

It does the work, not just the talking

The agent has tools: it reads and changes your data mid-conversation, within the limits you set.

Knows who is texting

Resolves the number or address to the contact, so it answers about their jobs, not in general.

Books and reschedules

Reads availability, moves the job, writes it back to the record.

Respects business hours

A weekly grid in your own timezone, DST-correct, with holidays. Off means answered around the clock.

Answers from your FAQ

Hours, coverage areas, contract terms, policy. Authored once and shared with the voice agent.

Reads your documents

Optionally searches your ingested documents, the same store the document Q&A uses.

Hands off to a human

Escalates when it should, rather than guessing at something it should not answer.

Safeguards

What happens when it gets it wrong

The honest question about letting AI talk to your customers. Here is the actual mechanism, not a reassurance.

Nothing commits without a typed confirmation

Anything that moves money, cancels work, or notifies a customer stages a preview first and quotes it back. It commits only when the customer replies with the confirm keyword. The check runs in the runtime against the raw text, not in the model, so a model that believes it was confirmed still cannot commit. Matching is whole-word, so "send me a confirmation email" confirms nothing.

STOP never reaches the AI

A bare STOP, UNSUBSCRIBE or CANCEL is handled as platform business and the provider's own opt-out runs. Replying conversationally to STOP is exactly the compliance failure that keyword exists to prevent. Outbound replies also check the opt-out list independently, so an opted-out contact cannot be messaged even if a conversation is somehow still open.

Two bots cannot volley forever

Email has no hangup, so auto-replies, bulk mail, bounces, no-reply senders and out-of-office subjects are dropped before the agent sees them. Behind that, a per-hour reply cap counted by address, not by conversation, so closing and reopening cannot reset it. And a message that looks like it came from the agent's own mailbox is dropped outright.

It can only touch the tables you allow

The agent's queries run under a role whose grants are the tables you allowlisted. That boundary holds regardless of what the instructions say or what a customer tries to talk it into.

Every confirmation attempt is logged with what was asked, what arrived, and whether it counted. Reply caps and an optional monthly ceiling sit in front of the model, and crossing the ceiling suspends the channel rather than quietly spending.

AI and humans, working together

The agent takes the ETA question from site contacts at 140 locations. Your dispatch desk takes the conversation that needs a person. Neither is doing the other's work.

Bring the messages you answer twenty times a week

On the mapping call we walk your process end to end and find which of them the agent should take. Then we configure it on your workflows and you watch it run.

Put AI to work

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.

Part of the Fieldproxy platform

Every agent runs on the same AI Agents stack

Voice, vision, dispatch, and knowledge agents all share one runtime, one schema, and one customization surface, describe what you want in plain English.

See all Fieldproxy agents →

Works in every trade

Which industry are you running today?

See all comparisons →

See it running on your operation

Book a 20-minute demo and we'll show you this agent (and the rest of our AI Agents stack) tailored to your real workflows.