Automate the whole flow. Keep the decisions.
An approval gate pauses a running workflow until the right person signs off, then it carries on by itself. Discounts over a threshold, jobs above a value, credit notes, a quote to a key account, anything a person should see before it goes out. Nothing waits in someone's head or in a WhatsApp thread, and every decision is on the record with who made it and when.
Gate added
Quotes above the threshold pause at send
Owner notified
It lands in their queue, not their inbox
Approved, then it flows
Sends, logs, and moves the job on by itself
Live in
Built your way
This is what makes the rest safe to switch on
Every AI claim on this site raises the same question: what if it gets it wrong. An approval gate is the answer, and it is a mechanism rather than a promise.
The workflow waits, it does not restart
An approval gate is a step in the middle of an automation. Everything before it has already happened; everything after it fires the moment someone approves. Nobody re-does the first half by hand.
Rejection is a path, not a dead end
Approve and it continues. Reject and it goes down the other branch: back to the estimator, a note to the customer, a different stage. Both outcomes are designed, so neither one leaves the job stranded.
The value raises the gate, not a person
Gates fire on a threshold being crossed, a stage being entered, or a record having sat somewhere too long. It does not depend on somebody spotting it.
The AI cannot approve on your behalf
On a call, a high-stakes change will not commit on a spoken yes: the caller presses a key after the change is staged. Over text it needs a typed keyword, checked against the raw message rather than by the model, so a model that believes it was confirmed still cannot commit.
Every attempt is auditable
Commits and refusals both. When someone asks who authorised the credit note, the answer is a record rather than a recollection.
By role, not by name
Gates route to whoever holds the role, so approvals do not stall because one person is on leave.
Where the money moves
Credit notes, write-offs, invoices above a value, purchase orders to a new supplier. The places where a mistake is expensive are the places a gate earns its keep.
Where compliance bites
A permit signed off before work starts, a remedial approved before the certificate issues, a safety acknowledgement recorded before the tech is on site.
Customer-side sign-off too
The customer approving the extra work is the same shape of gate: the job does not proceed until the approval is on the record.
Shaped to your trade
Your business doesn't run like the template. Neither does Fieldproxy.
Commercial HVAC
Quotes above contract value hold for the account manager before they reach the client.
Fire & Safety
Remedial work is approved before the certificate can be issued, not after.
Facilities
The landlord approves the extra spend before the contractor is sent.
Field Services
Credit notes and write-offs need a name against them, every time.
Platform
Everything you need, in one platform
A complete field service suite, explore what's included.
Estimates & Quotes
Branded quotes out the door, e-signed on the spot, converted to jobs.
Contracts & Invoices
Recurring billing, payment tracking, and QuickBooks/Xero sync.
Work Orders
Create, assign, track, and close every job, priority-aware and SLA-safe.
Job Checklists
Dynamic forms, conditional logic, required photos, and sign-offs.
Reporting & Dashboards
Revenue, utilization, SLAs, and leaderboards, live, no spreadsheets.
Customer Portals
24/7 self-service for bookings, invoices, and service history.
Integrations
Plays nicely with the tools you already use
Automations
Gates are a step in any workflow
Push + SMS + email
However the approver wants it
QuickBooks
Approved invoices sync, held ones do not
Xero
Same gate, same sync
Customer portal
Customer-side approvals
Zapier
Anything else
AI agents
Agents that stop at the gate
The agents do the work up to the decision. The decision stays with a person.
Calling Agent
Books and reschedules on the phone, but a cancellation or a payment stages first and needs a keypress from the caller before it commits.
Text Agent
Handles the thread, and quotes the change back before it commits. Only a typed keyword, matched in the runtime, lets it through.
Watcher Agent
Notices the job that has sat too long, or the approval nobody actioned, and raises it before it costs you the renewal.