FieldproxyAI-native field service softwareBy role: operations
What does an operations manager need from field service software?
An operations manager needs field service software that shows what is going wrong before customers notice, not a list of everything: jobs at risk of missing their SLA, work stuck in a status, visits that will need a second trip, and technicians over or under booked. Behind that they need a small set of weekly numbers they trust (first-time fix, utilization, SLA attainment, revenue and margin by job type, branch or region) built from data captured on the job, plus approvals that route themselves and a way to change forms and rules without waiting on IT.
- Exceptions first: show what needs action today, not every open job.
- Measure from the job itself: time stamps from the technician's phone, not typed later.
- Five numbers cover most weeks: first-time fix, utilization, SLA met, margin, overdue invoices.
- Rules and approvals should fire on thresholds, not on someone remembering.
- If changing a form takes a ticket and weeks, the process will drift back to spreadsheets.
This page is for the person who runs the service operation day to day. Dispatchers and finance teams need different screens; their guides are linked below.
Facts checked as of November 2026. Sources at the end of the page.
Step by step
What an operations manager's week looks like in good field service software
The software earns its place if each of these takes minutes, from data the field already captured.
Every morning: the exceptions list
One view of what needs a decision: jobs due today with no technician, jobs whose SLA response or fix deadline is inside the next few hours, jobs in 'waiting on parts' or 'waiting on customer' longer than your limit, technicians running late, and visits closed without the required photos or readings. Everything else stays off the screen.
During the day: alerts, not checking
Rules watch the thresholds you care about (an SLA at 75% of its time, a job three days in one status, a branch falling below its utilization line) and message the right person. The operations manager is told; they do not have to look.
Approvals that route themselves
Quotes over a value, discounts past a limit, overtime, purchase orders and not-to-exceed increases land in one approval queue with the job attached. Approve and the work carries on; reject and it goes back with a reason. Every decision is recorded.
Weekly: the numbers that matter
First-time fix rate, technician utilization (billable hours against paid hours), SLA attainment, jobs completed, revenue and gross margin per job, by job type, team, branch or customer. ServiceTitan, for example, defines first-time fix as jobs completed on the first visit without follow-ups, return trips or extra parts, and tracks utilization as billable hours against total hours.
Monthly: across branches and brands
The same measures rolled up across regions, branches or sister companies, with each team lead seeing only their own technicians and the operations manager seeing all of them.
Whenever the process changes
A new field on a form, a new status, a tighter SLA for one customer or a new report column is a change the operations team can make, or request in plain English, and see live the same day.
Why it goes wrong
Why operations managers end up running the business from spreadsheets
These came up on our sales calls with operations leads, by trade and size.
The numbers come from typing, not from the job
An oil and gas operational technology support team of about ten field technicians closed tickets on laptops at the end of the day, so the close time was when someone typed, not when the fix happened. They could not measure mean time to repair at all.
Status is tagged by hand
A commercial electrical contractor running 30 to 40 visits a day across self-storage sites tagged jobs 'needs parts' or 'waiting' by hand, so the board was only as accurate as the last person who remembered. Several people opened the same job because nobody was sure who owned it.
The software shows lists, not risk
The same contractor could not see, while scheduling, that another open job existed at the same site for the same technician. The information was in the system; nothing put it in front of the person deciding.
No KPIs at all
A five-technician electrical contractor described it plainly: they could not track any KPI or metric, so they did not know if they were winning or losing. Quotes went cold with no follow-up because nothing showed which ones were waiting.
Every change needs IT
The oil and gas team's forms lived in an enterprise service management tool, and any change went through the central IT team, which could take months. Field teams worked around it with photos on phones that were later copied to laptops.
Answers that are not kept
A renewables operations and maintenance head liked asking an AI questions about the fleet but pointed out that answers in a chat get lost. Operations managers need the useful answers pinned to a dashboard everyone sees.
Ways to do it
Ways operations managers get this today
| Approach | What you get | Where it falls short |
|---|---|---|
| Spreadsheets fed by exports | Full control of the formula; works with any tool | Always a day or a week old; someone spends hours a week building it; no alerts |
| Built-in reports in a trade FSM (for example ServiceTitan) | Standard measures on a dashboard. ServiceTitan puts utilization in Dashboard > Technician Scorecards > Productivity (Hours Worked and Billable Hours) and revenue per job in the Avg Ticket column | Fixed definitions and layouts; measures your business tracks differently may need exports or a custom report |
| A BI tool (Power BI, Looker) on the FSM's data | Any chart, any join, finance-grade reporting | Needs an analyst and a data pipeline; good for the board pack, slow for today's exceptions |
| Enterprise service platforms (Dynamics 365 Field Service, Salesforce Field Service) | Deep configuration, CRM in the same system. Microsoft lists improving first-time fix rate and completing more service calls per technician among what its Field Service app is for | Changes are typically made by an admin or partner; implementation is a project |
| Configurable FSM with rules and alerts (Fieldproxy) | Exception views, threshold alerts, approval queues and reports built around your own statuses and measures, changed on request | A smaller vendor than the enterprise platforms; if your finance team already runs a BI stack, feed it rather than rebuild every report |
Worked example
A worked example: one Monday for a 40-technician, three-branch operation
Say a commercial HVAC and electrical service company has 40 technicians across three branches and runs about 180 visits a day, a mix of maintenance contracts with SLAs and reactive calls. The operations manager opens the exceptions view at 7:30.
It shows 6 items, not 180. Two emergency calls from a contract customer have a 4-hour response deadline and are not yet assigned. One job has sat in 'waiting on parts' for five days, past the three-day limit. Three of Friday's jobs were closed without the required after photos. The two emergencies go to the dispatcher with one click each, the parts job goes to purchasing, and the three technicians get a request for photos.
At 11:00 an alert arrives: the north branch's SLA attainment for the week has dropped to 88% against a 95% target. The jobs behind the number are attached: four late responses, all on the same contract, all booked after 3 pm. That is a scheduling rule to change, not a technician problem.
On Friday the weekly digest lands: first-time fix by branch, utilization by technician, margin by job type and the overdue invoices. The south branch shows a low first-time fix on rooftop unit repairs; the second visits were for parts. The fix is a van stock list for that job type, decided from data the technicians captured on the job, not from a spreadsheet built over the weekend.
Before you buy
What to check before you buy
Good signs
- The demo opens on an exceptions view built from your own statuses, not a generic dashboard.
- Time stamps (on the way, arrived, completed) come from the technician's phone, and work offline.
- You can set a threshold and an alert yourself, such as a job three days in one status.
- Approvals by value or rule are built in, with the decision recorded on the job.
- Team leads can be limited to their own technicians and branch, while you see everything.
- First-time fix and utilization are calculated the way you define them, and you can see the jobs behind each number.
- Adding a field, status or report column does not need the vendor's services team or your IT department.
Red flags
- Every report in the demo is a fixed template with the vendor's definitions.
- KPIs only appear after an export to a spreadsheet or a separate BI subscription.
- Status changes are typed by the office after the technician phones in.
- Changing a form or workflow is quoted as a services project.
- Branch or team permissions are all-or-nothing.
In Fieldproxy
Setting it up in Fieldproxy
Your statuses and an exceptions view
Job stages are set to how you run (e.g. Booked, On the way, On site, Waiting on parts, Waiting on customer, Complete, Invoiced), and an operations view lists only the jobs breaking a rule today. See work orders and job management.
Watcher agent on thresholds
The Watcher agent watches jobs, SLAs and readings and flags or escalates when something goes wrong, such as an SLA near breach or a job too long in one status (e.g. three days in Waiting on parts goes to the ops lead).
Approval gates
Quotes over a value, discounts over a limit, purchase orders and time off pause in one approval queue until the right person signs off; the workflow then carries on and the decision is logged. See approval workflows.
Your measures, scheduled
First-time fix, utilization, SLA results, revenue and margin by trade, branch, technician, customer or job type, as dashboards, a wall-screen KPI ticker, or daily and weekly digests by email, Slack or Teams from the Scheduler agent. See dashboards and reporting.
Ask, then keep the answer
Ask the Command Center a question in plain English (for example 'why is the west branch under 65% utilization this week?') and get the jobs behind it; useful questions become a report or dashboard tile instead of a chat.
Branches, brands and permissions
Team leads see their own technicians and branch; several companies or brands can share technicians while keeping their own numbering, price books and books, and roll up into one view. See multiple companies in one account.
Change without IT
New fields, statuses, rules and report columns are requested in plain English and shown as a preview to confirm, with Undo. See the AI builder.
How switching works
How switching to Fieldproxy works
We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.
Bring your Monday questions
Tell us the five things you check every week and the spreadsheet you build to answer them today.We set up your statuses and rules
Your job stages, SLA targets, approval limits and alert thresholds are configured, and the exceptions view is built around them.Your reports on your data
Your measures are built with your definitions, and the weekly digest is scheduled to the people who need it.Live within a day
Technicians start capturing time stamps and photos in the app, and the numbers fill in from real jobs from then on.
FAQ
Questions people ask
- What KPIs should a field service operations manager track?
- Start with five: first-time fix rate, technician utilization, SLA attainment, gross margin per job, and overdue invoices. Add callbacks within 30 days and average time in each status once those are trusted.
- How do I calculate first-time fix rate?
- Divide the jobs completed on the first visit, with no return trip or follow-up for the same issue, by all completed jobs in the period. Decide up front whether planned multi-visit work and customer-caused revisits count, and keep the rule fixed.
- What is a good technician utilization rate?
- It depends on travel and the mix of work, so compare against your own trend rather than an industry figure. Measure billable hours against paid hours, and look at the jobs behind a drop before acting on it.
- Can team leaders see only their own technicians?
- In Fieldproxy, yes: visibility is set by role, team and branch, so a team lead sees and assigns only their own technicians while the operations manager sees every branch.
- Can I get alerts instead of checking dashboards?
- Yes. Thresholds such as an SLA near breach, a job too long in one status or a branch under its utilization line can post to email, Slack or Teams the moment they are crossed.
- Do I need a separate BI tool?
- Not for day-to-day operations. If finance already runs Power BI or a data warehouse, push the field service data there for the board pack and keep the exception views and alerts in the field service system.
Sources
Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.
- ServiceTitan Help: measure performance and make decisions (Technician Scorecards): https://help.servicetitan.com/commercial/docs/measure-performance-make-decisions-3
- ServiceTitan: field service metrics (first-time fix definition): https://www.servicetitan.com/blog/field-service-metrics
- Microsoft Learn: Overview of Dynamics 365 Field Service: https://learn.microsoft.com/en-us/dynamics365/field-service/overview
- IBM: What is field service management (FSM)?: https://www.ibm.com/think/topics/field-service-management
Related
Keep reading
- Field service software for dispatchers
- Field service software for finance teams
- Tracking SLA response and fix times
- Field service software for 100+ technicians across branches
- What is the best field service software for a 5-10 person HVAC team?
- Cheaper ServiceTitan alternatives for small plumbing and HVAC companies, without payment processor lock-in