Understand the Insights Pages
Insights replaces the old Reporting page with five focused views (Revenue & Sales, Jobs, Customer, Team, and Assets & Pricebook) and tells you honestly when a number cannot be measured yet.
Insights replaces the old Reporting page with five focused views (Revenue & Sales, Jobs, Customer, Team, and Assets & Pricebook) and tells you honestly when a number cannot be measured yet.
The single Reporting page has been replaced by Insights, a section in the sidebar with five pages. Each one answers a different question:
| Page | The question it answers |
|---|---|
| Revenue & Sales | Where did the money come from, what did it take to earn, and what is still unpaid? |
| Jobs | How much work got done, and was it done right? |
| Customer | Who do you serve, who stays, and what is a kept customer worth? |
| Team | Who did the work, and how efficiently? |
| Assets & Pricebook | What do you sell, and what do you service? |
Each number now has one obvious home. What used to be the "Service Quality" page folded into these: how a job went (on-time arrival, first-time fix, callbacks) lives on Jobs, and what customers said (reviews, CSAT) lives on Customer. The old "Jobs & Team" page split into Jobs (the work) and Team (the people). Every widget is drawn with the chart that reads fastest for it. A goal becomes a bullet chart, a day-and-hour pattern becomes a heatmap, and so on (see Understand Report Charts and Graphs).
Your old links still work: /reporting and /insights/quality take you to their
new homes, /insights/jobs-team opens Jobs, and /insights/retention opens
Customer.
The range you pick stays with you as you move between the five pages, and it lives in the page address, so you can send a colleague a link and they will see exactly the numbers you are looking at. (Two figures are a live snapshot rather than a range total, and say so: AR outstanding on Revenue & Sales is what is unpaid right now, and the reputation strip on Customer is your all-time rating.)
This is the most important thing to understand about Insights.
Some numbers can only be worked out if the underlying event was recorded. If your crews have never checked in on site, JobsiteOn genuinely does not know what time they arrived, so it cannot tell you your on-time arrival rate.
When that happens, the card says "Not tracked yet" and tells you the one thing that would start capturing it. It does not show you a zero.
That distinction matters more than it might sound. "0% callback rate" would mean your crews never have to go back to a job, excellent news. But a company that has simply never recorded a callback has not earned that number; it just has not measured one. Showing you a confident zero there would be inviting you to make a decision on a number nobody ever counted.
So: a zero on Insights is always a real measurement. If we cannot measure something, we say so.
| Card | What turns it on |
|---|---|
| On-time arrival | Crews checking in from the app when they arrive on site |
| First-time fix, Callback rate, Callback reasons | Linking a return visit back to the original job, and picking a reason |
| Quality score | It is built from on-time arrival, first-time fix and CSAT, so it appears once those do |
| CSAT, Complaints | Sending a review request after a job |
| Team utilization | Setting technician working hours, so billable time has something to be measured against |
| Subscriber figures | Adding a recurring service agreement |
A few numbers are real but worked out rather than stored, and they say so on the card. Subscription MRR, for example, is estimated from each agreement's per-visit price and how often those visits fall, because service agreements are priced per visit rather than as a monthly subscription.
The benchmark card on Revenue & Sales compares you against published 2025-26 field-service industry figures. The filled bar is you; the two markers are the industry average and the top quartile. Those markers are fixed reference points. They are not calculated from your account, and they do not move when you change the time range.
Did this answer your question?