Five Solvit FSM Features That Actually Changed How We Work

I want to be upfront about context: we're not a huge operation. Eight field technicians, somewhere between 25 and 45 open work orders on any given day, covering installation and maintenance for industrial IoT equipment. Small enough that each additional hour of admin time per day is noticeable. Large enough that the coordination chaos of the spreadsheet era was starting to genuinely hurt us — both in operational efficiency and in customer experience.

The switch to Solvit FSM happened about fourteen months ago. Most of the benefits were predictable in advance, but the magnitude of improvement surprised me, and a couple of things I didn't expect turned out to matter quite a bit.

1. Smart Scheduling with Travel Time

This was the feature that sold us on the platform in the first place, and it delivered exactly what it promised. Work orders now auto-schedule with technician location factored in — when a new job comes in, the system knows where each technician is, what their current work order load looks like, and what travel time to the new job would be from their next available position.

Before this, I was spending the first 30-45 minutes of every morning doing manual scheduling by eyeballing a map and a spreadsheet side by side. I knew roughly where each tech was going that day, and I was trying to avoid the obvious waste — dispatching someone from the north end of the city to a job in the south when we had someone already on that side. But "roughly" and "trying to avoid" is a description of a manual process that gets things wrong often enough to matter.

The concrete improvement: we reduced average drive time per job by somewhere around 18% in the first three months. That's not a number I had before, obviously, because we weren't tracking it. But we noticed it — fewer technicians complaining about back-to-back long drives, more jobs completed per tech per day, lower fuel costs. The scheduling optimization alone has more than paid for the platform cost.

The other thing it fixed that I didn't anticipate: last-minute changes. When a job gets cancelled or a tech calls in sick, rescheduling 15 work orders manually used to take 45 minutes and several phone calls. Now it's a five-minute process of dragging and reordering on the dispatch board while the system recalculates travel times.

2. Offline-First Mobile App

Our technicians work in places where reliable connectivity is not a given. Industrial facilities, basements, rural properties, buildings with thick concrete walls. The pre-Solvit workflow for these situations was a combination of paper notes, remembered information, and phone calls to the office when the tech got back in range. Which meant information about job completion, time spent, parts used, and customer sign-off was often delayed hours and occasionally lost entirely.

The offline-first architecture means the app works exactly the same way whether there's signal or not. The job details are cached locally before departure. The technician does their work, completes the job record, captures photos, gets the customer signature on the tablet. When they drive out of the building and the phone gets signal again, everything syncs automatically.

I didn't think this would be as big a deal as it turned out to be. The time we lost tracking down information from jobs completed in low-connectivity areas was significant — maybe 30-45 minutes per day across the team dealing with "wait, what did you actually do on that job, I need to put it in the system." That time is gone now. The record is complete when the job is complete, regardless of where that job happened.

3. Parts and Inventory Visibility on the Job

The scenario I was most tired of: technician arrives at a job site, identifies the issue, realizes they need a specific part, calls the office or the warehouse, drives forty minutes round trip to get the part, returns to complete the job. Entire visit takes four hours. Billable time: maybe ninety minutes. Customer wait: all day.

With parts inventory integrated into the mobile app, technicians can see current stock levels and reserve parts before they even leave for the job. When a tech is en route and realizes they might need a particular component for a likely scenario, they can check availability right there and route to the warehouse first if needed — rather than discovering the shortage after they're already at the customer site.

The other dimension is accuracy. When parts are consumed on a job, the technician records it in the app at the time of use. Inventory updates immediately. Before, parts usage was captured on paper job sheets, transcribed to a spreadsheet at the end of the day (or the end of the week, honestly), and the inventory numbers were always running a few days behind reality. We had more than a few cases of someone checking the spreadsheet, seeing adequate stock, driving to the warehouse, and finding the physical shelf empty because three jobs had consumed those parts since the last update.

4. Customer Self-Service Portal

This one surprised me. I expected it to be a useful feature. I didn't expect it to be the feature that most visibly changed our customer relationships.

The portal lets customers log in and see the status of their open work orders in real time — scheduled time, assigned technician, current status. They can upload photos or documentation when submitting a job request. They can approve quotes electronically. They can see their job history.

The first thing I noticed was the phone calls stopped. We were getting maybe 12-15 inbound "where is my technician / what's the status of my job" calls per day. Within six weeks of the portal going live, that was down to maybe four or five. I'd estimate 60-70% reduction in status inquiry calls. That's not a trivial amount of time for whoever in the office was handling those calls — and more importantly, it's a better customer experience, because they can check themselves at 11pm when we're closed rather than waiting until morning to call.

The electronic quote approval was a secondary benefit I hadn't fully valued at the outset. Our approval turnaround time went from an average of about 2.5 days (send a PDF by email, customer prints it or doesn't, signs it or doesn't, scans it or doesn't, emails it back) to about 4 hours. Customers can tap Approve on their phone when they see the quote. Faster approvals mean faster job scheduling, which means faster revenue recognition and happier customers.

The photo upload feature from the customer side was the genuine surprise. Multiple customers have started submitting photos of equipment issues when they log a job request. The technician shows up already knowing what they're looking at, with a parts list they've prepared in advance. First-time fix rates went up noticeably on jobs where customers provided photos.

5. Real-Time Job Status and SLA Tracking

Before Solvit, SLA compliance was something we reviewed after the fact. End of the month, go through completed jobs, identify which ones breached their committed response or completion times, figure out why, feel bad about it. This is exactly backwards from how SLA management should work — you want to be proactive, not retrospective.

The real-time SLA visibility means we can see, right now, which open jobs are at risk of breaching their committed window. The system calculates remaining time against the SLA clock for every open work order and flags jobs that are within a configurable threshold — say, two hours from breach. The dispatcher gets an alert and can take action: reprioritize the job, reallocate a technician, contact the customer to reset expectations before the breach rather than after.

The difference between managing SLAs proactively and apologizing retroactively is enormous for customer relationships, especially in the B2B context where SLA penalties are sometimes contractual. In the first quarter after implementing this, our SLA breach rate dropped by almost half. Not because our technicians got faster — because we were no longer discovering problems after they were already problems.

The management visibility piece also changed how we talk about operations internally. I can look at the dashboard at any point during the day and see the complete state of the field — who's on what job, what's at risk, what's been completed. Before, the only way to know that was to call or message each tech individually or wait for end-of-day reports. The visibility itself improves decision-making quality, because you're making decisions based on current reality rather than information that's hours old.

Where We're Still Figuring It Out

Fourteen months in, we're still not using every capability fully. The preventive maintenance scheduling module is configured but we're still transitioning all our PM schedules into it. The reporting and analytics are more powerful than what we've built yet — there's a lot of data being captured that we haven't fully turned into insight.

The migration itself was less painful than I expected — about six weeks of parallel operation, running both the old system and Solvit simultaneously, before we cut over completely. The hardest part was getting consistent data entry habits established with the field team. A system is only as good as the data going into it, and getting eight technicians to consistently complete job records to the same standard takes time and reinforcement.

But the direction is clear. The combination of scheduling intelligence, offline capability, inventory visibility, customer self-service, and real-time SLA tracking has fundamentally changed what managing field operations feels like. Less firefighting, more actual management. Less information chasing, more time for the work that matters. That's probably the best summary of what switching to a proper FSM platform actually buys you.