Product
The whole operation, in one platform
Service Biz Hero covers the route board, the technician's phone, the billing candidate queue, customer messages, commissions, and the outside systems a recurring-service business already depends on. Every module below ships for every account.
Recurring-service work runs on three things: a route that holds up under real-world changes, a crew that can complete a job from a phone, and a billing process nobody has to babysit. Service Biz Hero is built around those three things first, with the communication, commission, and integration pieces wired into the same record instead of bolted on as separate tools.
The office runs the desktop side - the route board, the billing queue, the settings a technician never touches. The technician runs the phone side - today's route, the checklist, the photos. Both sides read and write the same underlying job and agreement, so a change made on the road shows up on the office screen immediately, and a change made in the office shows up on the technician's phone the same way. What a person can do is decided by their role, not by which device they happen to be holding - a dispatcher assigning a technician to a truck should not need a different device than the one they use for everything else.
Job types, durations, and the rules that drive the route board are configurable per business rather than fixed to one trade. A panel-cleaning visit, a pest-control drop-off, and a plumbing call-out are different shapes of work, and the platform is built to hold all three without a schema rewrite for each new trade it takes on.
Dispatch
Build the day on one route board. Auto-fill packs remaining capacity, and a locked cell stays locked once the plan is final.
Technician App
Today's route, a checklist that remembers the property, before-and-after photos, and an offline queue that never loses a job.
Billing
A completed job becomes a billing candidate. A person reviews it before anything is invoiced or charged.
Customer Communications
Reminders, en-route texts, a post-visit email with photos, and review requests to the platforms you actually use.
Reschedules and Churn
Every reschedule is tracked as an event, not a note, so a pattern shows up before a customer is gone.
Commissions
Calculated straight from the signed agreement, adjusted automatically when pricing changes, with a review queue.
Integrations
Truck location and QuickBooks export, so the office isn't re-typing data that already exists somewhere else.
Dispatch
The route board is where a dispatcher spends the day: drag a job onto a truck and a day, let auto-fill pack the remaining capacity, and lock a cell once the plan is set. New customers keep their promised day, a pushed job escalates instead of getting lost, and a hold pulls a job into review the moment something looks wrong.
Dispatch also owns the rules a dispatcher usually has to hold in their head - which job goes where when a route needs to be rebuilt mid-morning, and what happens when a customer is inside the window where a job can no longer move without a heads-up. See how it works on the dispatch page.
Technician App
A technician opens one screen for the whole day: the route, the job checklist, and the dispositions that move a job from scheduled to complete. Before photos are required to start a job, after photos are required to finish it, and clock-out is blocked until every job assigned that day has been dispositioned - so nothing quietly falls off the route.
The checklist remembers what it saw at a property last time and surfaces it as an upsell lead when something changes. Everything works with no signal and syncs the moment it returns. Full detail on the technician app page.
Billing
A completed job becomes a billing candidate automatically, gets classified, and waits for a person to review it before anything is invoiced or charged. The review screen runs a three-way comparison - the signed agreement, the current pricing, and the invoice preview - so drift gets caught before a customer sees it, not after.
The overdue queue is the money screen: declines rise to the top, and a decline fires a customer text on its own. Two ledgers keep one-time invoices separate from recurring agreements, and multiple completed jobs for one customer in a day combine into a single charge instead of several. Full walkthrough on the billing page.
Customer Communications
A customer hears from the office at the moments that matter: a reminder ahead of the visit, a text the moment a technician is en route, and a single email after the job with photos and notes - never a text for that last one. Review requests go out afterward to whichever platforms you've told the system to use, in the order you set, not a platform picked for you.
Every message respects what a customer has actually consented to receive, checked per customer, per channel, every time a message would otherwise go out.
Reschedules and Churn
A reschedule - whether a customer asks for it through the portal or a technician requests it from the field - is recorded as an event, not a scribble in a note. A job that keeps getting pushed is visible to the people scheduling it, and language in a customer message that sounds like a cancellation pulls that job out of the route and into review before it can slip through.
That record is what turns "we lost another customer and nobody saw it coming" into a pattern the office can act on early.
Commissions
A rep's commission is calculated straight from the signed agreement - not a spreadsheet built after the fact - and adjusted automatically the moment a review catches pricing drift between what was signed and what actually got billed. Every adjustment carries a reason and stays visible in an audit trail.
Commissions run inside the platform rather than in a spreadsheet someone reconciles by hand at the end of the month, and the results are what feed the export to your accounting system - not a second, separately maintained set of numbers that has to agree with the first.
Integrations
Truck location comes from the GPS units already installed in the trucks, so dispatch and clock-in both reflect where a truck actually is. On the accounting side, invoices and payments export in the shape QuickBooks Online's own import tools expect, so the numbers reach your books without a manual rebuild every month.
Both integrations are built to read from a system you likely already have running rather than asking you to adopt something new just to get the data flowing. Truck location supports both dispatch (knowing where a truck actually is when a route needs to change mid-day) and the technician app's clock-in check; the QuickBooks bridge is a file export today, with a direct, credential-based connection planned as the next step once that integration path exists.
Frequently asked questions
What happens if I sign and it turns out the routing doesn't work the way the demo showed?
The routing rules are published on the dispatch page, in plain language, before you ever sit through a demo. Priority order, capacity, holds, and locks are described exactly as they run - so you can judge the mechanism yourself instead of taking a sales rep's word for it.
Does the mobile app work when my technician has no signal out at a property?
Dispositions, photos, and completions queue on the phone and sync automatically the moment signal returns. A technician working through a dead zone keeps working; nothing has to wait for bars.
Does this integrate cleanly with QuickBooks, or am I doing manual cleanup every month?
Invoices and payments export in the column layout QuickBooks Online's own import screens expect, so your bookkeeper brings them in without hand-fixing the shape. A direct, credential-based connection is the planned upgrade once that path exists; the file export is what runs today, and it is a real workflow, not a placeholder.
Can it separate my service schedule from my billing schedule?
Yes. Service cadence and billing cadence are separate fields on every agreement, so a customer serviced on one rhythm can be billed on another without either field fighting the other.