The job events that need a person, in the Slack channels your office already reads
Fieldproxy posts the job events your office needs to act on into the Slack channels you choose: a new urgent job, a technician running late, a failed inspection, a job gone overdue. Quotes or purchase requests above a limit you set post with Approve and Reject buttons, and the answer goes straight back to Fieldproxy. A morning summary of today's jobs and yesterday's misses lands in the ops channel. Every message links to the job, so nobody has to search for it. The jobs, the schedule and the technician app live in Fieldproxy; Slack is where the office hears about them.
Fieldproxy is AI-native field service software, set up around your workflow and live within a day. It replaces the field service tool, the dispatch spreadsheet and the WhatsApp group; it is not a layer on top of other field software. One price per company, unlimited users.
See your job alerts in your Slack
Tell us what your office needs to know about, and when. We set it up on your own job types before you commit.
What syncs
Alerts go out. Approvals come back.
Built on the Slack Web API and Events API. Most of the traffic is one way: Fieldproxy tells a channel something happened. Approvals are the exception, because a decision made in Slack has to land on the quote or purchase request it was about.
| Object | Direction | When |
|---|---|---|
| Urgent new jobs | Fieldproxy โ Slack | When a job is created with a priority you mark as urgent, it posts to the channel you choose. |
| Late arrivals | Fieldproxy โ Slack | When a technician hasn't checked in by the time they were due on site. |
| Failed inspections | Fieldproxy โ Slack | When a checklist or inspection on a job is marked as failed. |
| Overdue jobs | Fieldproxy โ Slack | When a job passes its due time without being completed. |
| Quote and purchase request approvals | Both ways | Requests above a limit post with Approve and Reject buttons. The decision, and who made it, goes back to Fieldproxy. |
| Morning summary | Fieldproxy โ Slack | Each morning, today's jobs and yesterday's misses post to the ops channel. |
| Other job events | Set up per account | Further events (for example job completed or a parts request) can be discussed at setup and confirmed for your account. |
Every message links back to the job in Fieldproxy, and alerts can be limited to working hours.
The workflow
Slack alerts for job events, step by step
A typical day once the connection is set up. The events, channels and approval limits are agreed with you.
- 1
The morning summary posts
Fieldproxy, to #ops
Today's jobs and yesterday's misses: what is booked, what didn't get finished, what is still open. The ops lead starts the day knowing where the gaps are. - 2
An urgent job comes in
Fieldproxy, to #dispatch
A job created with an urgent priority posts to the dispatch channel with a link. Whoever is on dispatch opens it and assigns it, with the Dispatch agent suggesting who is closest and qualified. - 3
A technician is running late
Fieldproxy, to #dispatch
If the technician hasn't checked in by the time they were due, a late-arrival alert posts. The office can call the customer before the customer calls them. The Watcher agent watches for the same kinds of misses inside Fieldproxy. - 4
A quote needs sign-off
Fieldproxy to Slack, and back
A quote above the limit you set posts with Approve and Reject. A manager taps Approve on their phone; the decision and who made it are recorded on the quote in Fieldproxy, and the quote can go to the customer. See approval workflows. - 5
An inspection fails
Fieldproxy, to #quality
A checklist item marked as failed on site posts to the quality channel with the job link, so a follow-up visit or a quote is raised the same day. - 6
A job goes overdue
Fieldproxy, to #dispatch
A job past its due time without completion posts, so it is rescheduled rather than discovered at the end of the week.
See your own alerts and approvals posting to a test channel.
Get DemoWhat stays where
Slack for the conversation. Fieldproxy for the job.
Slack is good at getting a person's attention. It is not where a job should live, because a thread can't hold a schedule, a checklist, a stock count or an invoice.
| Stays in Slack | Lives in Fieldproxy |
|---|---|
| The conversation about a job between office staff | The job, its status, notes, photos, checklist and history |
| Alerts that need a person to look now | The rules that decide when an alert fires |
| The Approve or Reject click | The quote or purchase request itself, its limit and its audit trail |
| Your channels, members and Slack permissions | Who in your company is allowed to approve, and up to what limit |
| Office-to-office chat | Technician work: the Fieldproxy app, offline, with GPS check-in |
Approvals show why the split matters. A manager's thumbs-up emoji in a thread approves nothing: the quote still sits in the system unapproved, and in three months nobody can say who agreed to it. With the Approve button, the decision is written to the quote in Fieldproxy with the name of the person who made it. Slack is where the click happens; Fieldproxy is where the record of it lives.
Why not run dispatch in a channel?
Teams that dispatch from a chat group lose jobs in the scroll. Nobody can see what is late, who has the part, or which finished jobs were never invoiced.
What Fieldproxy holds
Your own stages, forms and checklists, scheduling and dispatch with approval and undo, stock, quotes, invoices with payment links and Tap to Pay, and a customer portal.
What the technician uses
The Fieldproxy Android and iOS app: offline, GPS check-in, photos, signatures, in 27 languages.
Worked example
A Thursday at a demo fire safety company
Demo data with fictional names. Redfern Fire & Safety inspects and services fire alarms and extinguishers for commercial sites. The office runs on Slack; the engineers run on the Fieldproxy app.
- 07:30, #ops: the morning summary shows the day's booked jobs and one inspection left unfinished yesterday at Kingsway Medical Centre.
- 09:05, #dispatch: urgent job: alarm panel fault at Larch House. Ops coordinator Mia Chen opens the link and assigns engineer Sam Patel.
- 10:20, #dispatch: late arrival: engineer Dev Rao hasn't checked in at Oakfield School, due 10:00. Mia calls the site to say he is twenty minutes out.
- 11:40, #quality: failed inspection at Larch House: two extinguishers past service date. Mia raises a quote from the job.
- 11:55, #approvals: the quote is above Redfern's approval limit. Operations manager Ellen Ward taps Approve on her phone; the approval is recorded on the quote and it goes to the customer.
- 17:00: alerts stop for the day, as set for working hours.
Setup
Connected and live within a day
A Slack workspace admin installs the app. The Fieldproxy team does the rest with you.
- 1
Decide what is worth an alert
Which events need a person, which channel each goes to, and the hours alerts should post. - 2
Install the app in Slack
A workspace admin installs the Fieldproxy app into the channels you choose. - 3
Choose events and channels
Urgent jobs, late arrivals, failed inspections, overdue jobs and the morning summary, each mapped to a channel. - 4
Set the approval rules
The limit above which quotes and purchase requests need approval, and who can approve from Slack. - 5
Test, then go live
Fire each alert from a test job, approve a test quote, and check it lands back in Fieldproxy. Your existing data comes across with free, assisted migration.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- Your office and managers already work in Slack all day.
- Problems are found too late: late technicians, failed inspections and overdue jobs show up at the end of the week.
- Quotes or purchases wait days for a manager to sign them off.
- You want a daily view of the field without opening a report.
Not the right fit when
- You want to run dispatch inside Slack. Dispatch, scheduling and job records live in Fieldproxy.
- Your team doesn't use Slack. Inside Fieldproxy, the Watcher agent already flags missed visits and work about to go overdue.
- You want to keep another field service system and only add Slack alerts to it. Fieldproxy replaces the field service tool rather than sitting on top of one.
See it built around how your team already works.
Get DemoStraight answers
Slack and field service: questions we get asked
What does Fieldproxy post to Slack?
Can we approve quotes from Slack?
Can we change a job's status or reply to a customer from Slack?
Can different alerts go to different channels?
Will Slack get noisy at 3 am?
Do technicians need Slack?
How is this different from building alerts in Zapier?
Can I ask about jobs from Slack using AI?
What does it cost?
How long does setup take?
Related
More on alerts, approvals and automation
See every connection on the integrations page, or work with your field data from Claude, ChatGPT or Copilot through Fieldproxy's MCP server.
Keep Slack. Hear about the job before the customer calls.
Tell us which events your office needs to act on. We show them posting to your channels on your own setup.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.