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.
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
Built your way
Not a separate tool your team alt-tabs to, and not a mailbox rule. The conversation sits where the work sits.
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.
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.
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.
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.
Quote request, complaint, supplier invoice, scheduling change. Sorted as it arrives so the right person sees it rather than everyone seeing everything.
AI produces a template from how you already write, and picks the right existing one for the thread in front of you.
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.
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.
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.
Shaped to your trade
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
A complete field service suite, explore what's included.
Automated SMS, email, and WhatsApp, branded and 2-way.
24/7 self-service for bookings, invoices, and service history.
Create, assign, track, and close every job, priority-aware and SLA-safe.
Recurring billing, payment tracking, and QuickBooks/Xero sync.
Revenue, utilization, SLAs, and leaderboards, live, no spreadsheets.
Full field toolkit with offline-first capture, photos, and e-signatures.
Integrations
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
Reading, drafting and classifying are one thing. Answering on its own is a decision you make per agent.
Answers inbound email against the real job record, reschedules it, and stages anything high-stakes for a typed confirmation.
Reads the PO, quote or warranty claim that arrived as an attachment and pulls out the fields.
Answers the policy and pricing questions in the thread from your own documents, rather than from a guess.