Most field service software demos are pitched to two people: the owner, who signs, and a lead tech, who tries the mobile app. The person who will live in the software eight hours a day, every day, often isn’t in the room. That’s the dispatcher, the CSR who answers the phone, or the office manager who turns finished work into invoices.
That’s backwards. On a team of 15 to 40 technicians, the office is where a field service platform succeeds or fails. A tech may touch a job for an hour. The office touches it at intake, at scheduling, at every reschedule, at close-out, at billing, and again when the customer calls to ask where the invoice is.
This guide is the office-chair version of an FSM evaluation. If you want the short answer to “Jobber or ServiceTitan for office staff?”, it’s in the FAQ on our Jobber vs ServiceTitan comparison. If you need a whole-company buying framework, start with how to choose field service management software. This post goes narrower: what dispatchers, CSRs and billing staff should test, and how to score it.
A dispatcher’s day, and what each hour asks of the software
Here is a composite day for a dispatcher at a 22-tech commercial HVAC and plumbing contractor. It’s an illustration, not one customer’s story, but every moment in it comes up on most commercial teams.
6:45 AM: two techs call in. One is sick and one has a truck in the shop. Eleven jobs need new owners before 8:00. The software has to show the whole team on one board, let the dispatcher drag a job to another tech, and push the change to that tech’s phone. It should also say who is qualified. Moving a backflow test to a tech without the certification creates a problem nobody notices until the inspector does.
8:30 AM: a property manager calls about a leak that came back. The CSR needs the building, the unit, last week’s job notes and the tech who was there, all on one screen while the caller waits. If that history sits in another tech’s text thread, the CSR puts the caller on hold and starts digging.
10:00 AM: texts start landing. Customers confirm windows, ask about ETAs and send photos. If those texts go to technicians’ personal phones, the office never sees them, and when a tech is off the conversation goes with them.
12:15 PM: a part is backordered. The job can’t close, but it can’t disappear either. The dispatcher needs a status like “Waiting for Parts” that the whole office can filter on, so someone follows up with the supplier.
2:00 PM: next week’s maintenance visits. Forty preventive-maintenance and inspection visits are due under service contracts. If someone has to rebuild them by hand every cycle, the one week that person is on vacation is the week a contract customer gets missed.
4:30 PM: close-out. Eighteen jobs were completed today. Every one should become an invoice with the line items the tech already entered, and any finished job without an invoice should show up somewhere obvious.
Month-end: the bookkeeper. Invoices and payments need to reach the accounting system without anyone re-keying them, and customers created in the field app shouldn’t turn into duplicates in QuickBooks.
Every item on the checklist below comes from one of those moments.
The 12-point evaluation checklist (office edition)
Use this in demos. For each item, ask the vendor to show it with your dispatcher at the keyboard, not the sales engineer.
Dispatch board
- One board for the whole team. Day and week views, every tech side by side, jobs colored by status, filters by crew or group. Red flag: the demo uses five techs and you have 25.
- Same-day reshuffle in two moves. Drag a job to another tech or time slot, and the tech’s mobile app updates. Ask what the customer is told, and when. Time it: move three jobs and see how long it takes.
- Skills and certifications enforced at assignment. Required skills on the job, held skills on the tech profile, and the scheduler won’t suggest someone who doesn’t qualify. Red flag: certifications live in a spreadsheet.
- Recurring work generates itself. Maintenance and inspection visits on contract appear as jobs on their cycle, ready to schedule. Ask: what happens to future visits when the contract changes?
CSR and intake
- One customer record a CSR can read in ten seconds. Sites, contacts, equipment, open jobs, past visits and notes on one screen. Test: look up a real multi-site customer while someone times you.
- A shared inbox, not personal phones. Texts and emails in threads the whole office can see, assignable to a person, with replies landing in the same place. Ask: does texting cost extra, and who bills it?
- Intake to job without retyping. A web request or portal booking should create the job with the customer, address and requested window already filled in.
- Customer self-service that cuts phone calls. A portal where customers accept estimates, check job status, download reports and pay invoices. Every “where’s my report?” call it absorbs gives your CSR back time.
Invoicing handoff
- Finished job to invoice in one step. Line items, customer, site and payment terms carry over from the job, with no retyping. Test: close a job in the mobile app, then invoice it from the office.
- A safety net for unbilled work. Some list or report should catch completed jobs with no sent invoice, with a way to mark warranty and contract visits non-billable so the list stays honest.
- Accounting sync, and which direction. Ask exactly what syncs (customers, items, invoices, payments) and whether it is one-way or two-way. One-way sync means corrections made in QuickBooks don’t come back.
- Office seats: who counts, and what they cost. Some vendors count anyone who logs in as a user. Others bill per technician and include some office users. Get the office-seat count and price in writing. Our ServiceTitan pricing and Jobber pricing guides show how two big vendors define users.
Access (bonus check)
+ Roles and permissions for each office job. Can each office role be limited to the screens and data it needs, such as the dispatch board for dispatchers, invoices and payments for billing, and settings and user management for admins? Ask whether roles are fixed or can be adjusted, and what field users can see. Test: log in as a dispatcher and try to open billing or company settings. This check isn’t in the score table below. Add it as a row if access control matters to your office.
Score it: a weighted table you can copy
Weight each item by how much it matters to your office (1 = nice to have, 3 = can’t run without it). Score each vendor 0 (missing), 1 (workaround) or 2 (works as shown). Multiply, then add up.
Here’s a worked example from the same 22-tech shop, comparing two unnamed vendors after demos. The scores are illustrative.
| # | Item | Weight | Vendor A | A × W | Vendor B | B × W |
|---|---|---|---|---|---|---|
| 1 | One board for the whole team | 3 | 2 | 6 | 2 | 6 |
| 2 | Same-day reshuffle | 3 | 2 | 6 | 1 | 3 |
| 3 | Skills enforced at assignment | 2 | 1 | 2 | 2 | 4 |
| 4 | Recurring work generates itself | 3 | 1 | 3 | 2 | 6 |
| 5 | Ten-second customer record | 2 | 2 | 4 | 2 | 4 |
| 6 | Shared inbox | 2 | 2 | 4 | 1 | 2 |
| 7 | Intake to job without retyping | 1 | 2 | 2 | 1 | 1 |
| 8 | Customer portal | 2 | 1 | 2 | 2 | 4 |
| 9 | Job to invoice in one step | 3 | 2 | 6 | 2 | 6 |
| 10 | Unbilled-work safety net | 2 | 0 | 0 | 2 | 4 |
| 11 | Accounting sync direction | 3 | 1 | 3 | 2 | 6 |
| 12 | Office seats in writing | 2 | 1 | 2 | 2 | 4 |
| Total (max 56) | 28 | 40 | 50 |
Vendor A gave the slicker demo. Vendor B wins by 10 points, mostly on recurring contract work, the unbilled list and two-way sync: the things that cost this shop money every month. That’s the point of weighting. A commercial shop running maintenance contracts should weight items 4, 10 and 11 heavily. A residential shop with a call center would weight items 5 to 7 higher.
Two rules keep the table honest. First, a feature only scores 2 if your own dispatcher made it work in the demo. Second, score item 12 from the written quote, not the sales call.
How to run the demo from the office chair
- Bring three real scenarios from last week: the sick call, the callback and the backordered part.
- Let your dispatcher drive, and count clicks for a reassignment and for job-to-invoice.
- Write down every “we can configure that.” Each one is a quote question: included, extra, or a services project? Our hidden fees guide lists the quote lines to check.
Where Forz fits for office teams, and where it doesn’t
Forz is built for commercial and inspection-driven contractors, so the office side matters to us. Here’s how it maps to the checklist, from our live feature pages:
- Dispatch (items 1–4): a drag-and-drop scheduling and dispatch calendar with day, week, month and list views; AI schedule suggestions that rank up to five technician-and-slot options; skills matching that only suggests technicians holding every required skill; and recurring jobs that arrive on their cycle ready to place.
- CSR and intake (items 5–8): customer, site and contact records in one place; a shared conversations inbox for SMS and email (texting runs on your own Twilio account or Forz telephony, priced separately); online booking; and a customer portal where customers accept estimates, check job status, download inspection PDFs and pay invoices.
- Invoicing (items 9–11): Convert > Invoice copies a job’s line items into a draft invoice, an Unbilled list catches finished jobs with no sent invoice, and customers, items and invoices sync both ways with QuickBooks Online (invoicing and payments).
- Office seats (item 12): Forz prices per user, and office logins count. A 22-tech shop with three office staff is 25 users: $1,250 a month billed annually ($50 × 25) or $1,500 month-to-month ($60 × 25). The minimum is 10 users. Guided onboarding, including office training, and one standard data import are included (Forz pricing).
Where Forz is not the right pick:
- You want software to answer the phone. Forz isn’t an AI receptionist or answering service. Your team takes the call. Forz can transcribe and summarize recorded calls afterward.
- Job costing is your top office requirement today. Our product roadmap lists the Job Costing module as in progress, so check its status in your demo.
- You run a residential call center built around call booking, memberships and marketing attribution. That’s the operation ServiceTitan is designed for. See the Jobber vs ServiceTitan hub.
- You have fewer than 10 people. You’d pay the 10-user minimum. See whether the Small Business Program on Forz pricing applies.
If you’re past the size where one person runs dispatch from memory, our guide to field service software for mid-size contractors covers the wider 10–50-tech decision. To compare vendors feature by feature, the compare hub has the side-by-side pages. When you book a demo, bring this checklist and your dispatcher.
FAQ
What should a dispatcher look for in field service software?
A single board that shows every technician, two-move reassignment that updates the tech’s phone, skills enforced at assignment, and recurring maintenance that generates its own jobs. Test all four with your own dispatcher at the keyboard, using a real day’s reshuffles.
How many office users should I budget for?
Count everyone who will log in to schedule, take calls, invoice or report, including part-time and backup staff. Then check how each vendor bills them: some count every login as a user, others bill per technician and include some office users. Get the number in writing.
