What can my field service software never tell me, no matter how good the reports are?
It cannot tell you about demand that never became a record. Unanswered calls, calls that did not book, estimates never sent, and customers who chose a competitor leave no trace in the system. Field service software is a record of work that happened. Every number it produces is a percentage of a denominator it cannot see, which is why the biggest opportunities usually sit outside it.
The system starts recording too late
A job record begins when someone decides to create one. Everything before that moment — the ring, the conversation, the hesitation, the hang-up — happens in the phone system, the web form, or nowhere at all. If the call did not book, most field service platforms have no object to attach it to.
So when a dashboard says your booking rate is a certain figure, ask what the denominator was. Usually it is calls someone chose to log, which is not the same as calls that came in.
Four categories of invisible demand
- Unanswered calls. Rings after hours, during storms, or while everyone is on another line. Only the phone platform knows.
- Answered but unbooked. A real customer with a real problem who did not schedule. The most recoverable category, and the least measured.
- Quotes discussed but never sent. A technician talked through a replacement and never produced the estimate. There is no record of a quote that does not exist.
- Silent churn. A maintenance customer who simply stops calling. The system shows no negative event, just an absence.
How to give the blind spot a number
You cannot recover what never happened, but you can size it. Join the phone system's full call log to the field service system's records rather than relying on logged calls. The difference between total inbound calls and calls that produced any record is your unmeasured surface. Then apply your existing booking rate and average ticket to it to get an order-of-magnitude value.
That estimate is rough and should be labeled as rough. It is still far more useful than pretending the category does not exist. This is precisely the join that call analysis exists to make, and it is why we treat the phone system as a first-class data source alongside the field service platform rather than as an accessory to it.
Silent churn deserves its own detector
Absence is hard to alert on because nothing happens. The workable approach is a per-customer expected-return interval derived from that customer's own service history, then a flag when they pass it by a meaningful margin. Seasonal trades need the interval computed seasonally, or every summer looks like mass churn.
That is a customer intelligence problem rather than a field service reporting problem, and it is a good example of why the FSM should be one input to your reporting rather than the whole of it.
Topics: reporting · blind spots · measurement · lost demand
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.