Home Services · Operations & Admin
The job finished Tuesday and the invoice went out Saturday
The customer is happy. The tech is three calls down the road. And the invoice is sitting because nobody has the model and serial number, or the before photo, or the note explaining why the job took ninety minutes longer than quoted. So the office chases the tech, the tech is under a house, and four days go by on money you have already earned and already paid labor on.
Multiply that across every job, add the warranty claims nobody files and the callbacks nobody codes, and you get the gap between what a shop grosses and what its owner takes home — most of which is sitting in paperwork nobody wants to do.
What happens after the truck leaves
The board gets rebuilt by hand every morning, in one person's head
Your dispatcher knows which tech is good with which equipment, who is near what, who the difficult customers will tolerate, and which two guys cannot be sent to the same neighborhood. None of that is written anywhere. When they take a week off, the week costs you two or three jobs and everybody agrees the dispatcher is irreplaceable, which is true and is also a business risk.
Warranty claims that are real money never get filed
A compressor under manufacturer warranty is a genuine recovery and the paperwork is genuinely annoying — model, serial, install date, failure description, proof of purchase. The tech has moved on, the office does not have the details, and the claim window closes. So you eat parts you were entitled to recover, quietly, several times a month.
Invoices are held hostage by a missing photo or a serial number
Not by a dispute, not by a credit problem — by one field. The job is complete and billable and it waits days for a piece of information that takes the tech eleven seconds to supply if somebody asks for exactly that thing at the right moment.
Callbacks happen three times a month and nobody codes them
Same failure, same part, sometimes the same tech. It is a training problem or a parts-quality problem or a diagnostic problem, and it stays a mystery because nobody categorizes callbacks — they just get absorbed as the cost of doing business by a business that could have stopped paying it.
Chasing the eleven-second answers so your office does not have to
Start with the invoice blockers, because it is immediate money and requires nothing from anybody. When a job closes, an agent checks it against what your billing actually needs — serial numbers, photos, the parts used, the note explaining the variance — and texts the tech asking for precisely what is missing, on the job it is missing from. Not a form. Not another app. A text message with a specific question, which is the only format a tech under a house will answer.
The same mechanism files warranty claims. Once the job record has the model, serial, install date, and failure description, generating and submitting the claim is clerical work, and clerical work that nobody has time for is exactly what should be automated. Most shops discover the recovery is meaningfully larger than they assumed.
Dispatch is the more delicate piece and we treat it as an assistant, not a replacement. It proposes tomorrow's board with reasons attached — proximity, equipment familiarity, capacity, customer history — and your dispatcher accepts, rejects, or overrides. The value is not that it dispatches better than a good dispatcher. It is that the reasoning stops living exclusively in one person's head.
And callbacks get coded automatically from the job records, so the pattern surfaces without anyone maintaining a spreadsheet about it.
What we build toward
- 4 days → same dayJob complete to invoice sent
- Missing fields chased by text at close-out rather than discovered by the office two days later. This is the fastest cash-conversion improvement available to most shops and it requires no change in how anyone works.
- FiledWarranty claims, from the job record
- Claims generated and submitted from data the job already captured, inside the window. Owners routinely underestimate this recovery because the ones they miss leave no trace.
- CodedEvery callback, with the pattern surfaced
- Callbacks categorized by failure, part, and tech automatically, so a recurring problem shows up as a pattern in month two rather than as a vague feeling in year two.
Sized against your own numbers. Days-to-invoice is the one to hold us to — you can pull your current average out of ServiceTitan this afternoon, and if it does not move within two months the project did not work.
What actually gets built
Invoice blocker chasing by text
Knows what each closed job is missing for billing and texts the tech asking for exactly that. No app to install, no form to open — a specific question about a specific job, which is the only thing that gets answered from a crawlspace.
Warranty claim generation
Assembles and files manufacturer warranty claims from the completed job record, tracks them to resolution, and flags the ones approaching a claim window so the recovery does not quietly expire.
Dispatch assist with stated reasoning
Proposes the board with the reasoning visible — proximity, equipment familiarity, capacity, customer history — for your dispatcher to accept or override. Designed to make the logic legible, not to take the decision away.
Callback coding and pattern detection
Categorizes every callback by failure mode, part, install date, and tech, and surfaces the recurring combinations. Usually the first month produces one finding a shop owner did not know and immediately acts on.
Purchase order and truck stock reconciliation
Matches parts used on jobs against purchase orders and truck stock so the discrepancies that currently surface at inventory show up weekly, while somebody can still remember what happened.
Modeled, not claimed
What four days of billing lag costs a twelve-truck shop
Twelve trucks, a normal mix of service and replacement, and an average of three to four days between job completion and invoice release.
Every day between finishing the work and sending the bill is a day you have paid labor, consumed parts, and financed the customer for free. Shops treat it as unavoidable, but the specific cause is almost never a dispute — it is a missing field, and a missing field is a chasing problem rather than a business problem.
Close that gap to same-day and the working capital release is immediate and permanent, which for most shops is the difference between drawing on the line of credit in the shoulder season and not. The warranty recovery lands on top of it, and unlike the billing improvement it is pure margin rather than timing.
- 3–4 days
- typical completion-to-invoice lag
- Permanent
- the release is a shorter cycle, not one-time
- This afternoon
- how long it takes to pull your current number
Illustrative arithmetic, not a client result. Your days-to-invoice is already in your field service platform, which makes this the easiest thing on this page to check before you believe us.
What owners and dispatchers push back on
My dispatcher is my best employee. This is going to feel like a demotion.
It would, if it were built to replace them, and a lot of dispatch software is sold exactly that way. This one proposes and explains, and the dispatcher decides — which in practice makes them faster on the routine eighty percent and leaves them the judgment calls that are actually why they are good. It is worth being straight with them about the second reason too: right now the business has a single point of failure named after them, and they usually know it. Making the reasoning visible is how they take a real vacation.
My techs will not use another app. I have bought two they ignored.
Then do not buy a third. Everything tech-facing here runs over text message, because that is the only channel with universal adoption in this trade. A specific question about a specific job — what is the serial on the unit you just installed at the Marshall house — gets answered. A notification asking them to open an app and complete a form does not, and no amount of policy fixes that.
Our ServiceTitan data is a mess. Half the job records are incomplete.
That is the condition this is designed for, and it is also why the invoice-blocker piece goes first: it improves the data as a side effect of chasing it. The warranty and callback work gets better as the record gets better, which means the sequencing matters. Anybody who proposes starting with the analytics on top of incomplete job records is selling you a dashboard that will be wrong.
Straight answers
Which field service platforms does this work with?
ServiceTitan, Housecall Pro, FieldEdge, and Jobber cover most shops in this size range and all are workable. ServiceTitan gives the most access and therefore the most capability. If you are on something older or partly on paper, the honest answer is that the platform is the first project, not this.
Does the dispatch piece work for a shop that runs multiple trades?
Yes, and multi-trade is where it earns the most, because the constraint set is harder — a tech qualified for gas work is not interchangeable with one who is not, and a dispatcher juggling three trades is holding more in their head than any one person should.
How does it handle a tech who just does not respond to the texts?
It escalates to the office after a set interval rather than nagging indefinitely, and the non-response pattern itself is reported. Usually one or two people account for most of the billing lag, and the value of knowing that is separate from the value of the chasing.
How long until this is live?
The invoice-blocker chasing is typically running in three to four weeks because it is narrow and low-risk. Warranty filing follows once the job records are consistently complete enough to support it, which is usually a month or two later — and is a consequence of the first piece working.
Also for home services operators
On the hottest Saturday of the year, half your phone calls ring out
Marketing & ReportingYour agency reports leads. A lead that rings out is not a lead.
Different industry? See every industry and function we have mapped.
Pull your days-to-invoice, then talk to us
The Pulse AI Operations Index scores intake, operations, and reporting across a home services business. Bring your current completion-to-invoice number and your callback count — those two decide most of what we would recommend.