See every tech in the field, live
A service dashboard gives home-service companies a real-time view of every tech in the field: revenue per visit, average ticket, callbacks, zero-ticket jobs, and membership conversions. When that data is live, a service manager can stop a bad day from becoming a bad month.
The problem
You have techs in the field all day. What do you actually know about them?
Here is the before-and-after that most service managers recognize. Before a live dashboard: a plumbing company closes the month and discovers two techs averaged $180 average tickets while two others averaged $520, and the company has no idea when the split happened or which jobs caused it. After a live service dashboard: the same manager can see at noon that a tech is running zero-ticket jobs back to back, call the dispatcher before the afternoon schedule runs, and recover the day. The difference is not data collection, it is visibility timing.
What good looks like on a service team
Status colors below reflect a single service day and are illustrative. Real targets vary by trade, season, market, and how your company defines a billable job. Use these as a starting framework, not industry guarantees.
- Revenue per tech (today)On pace. Jorge has the highest average ticket in the group this week.Good
- Current
- $1,840
- Target
- $1,500+
- Average ticket (today)Two techs dragging the average down with sub-$200 service calls. Review job types before tomorrow.Watch
- Current
- $312
- Target
- $380+
- Callback rate (rolling 7 days)Three callbacks tied to one tech. Likely a parts issue. Pull the jobs before end of day.Poor
- Current
- 6.2%
- Target
- < 4%
- Zero-ticket jobs (today)Two are warranty; one is unexplained. Follow up before close of business.Watch
- Current
- 3
- Target
- 0–1
- Memberships sold (MTD)Halfway through the month at 70% of goal. Need to run a short tech contest this week.Watch
- Current
- 14
- Target
- 20
- Jobs completed (today)Strong completion rate; capacity is well-utilized.Good
- Current
- 22
- Target
| Metric | Current | Target | Status |
|---|---|---|---|
| Revenue per tech (today)On pace. Jorge has the highest average ticket in the group this week. | $1,840 | $1,500+ | Good |
| Average ticket (today)Two techs dragging the average down with sub-$200 service calls. Review job types before tomorrow. | $312 | $380+ | Watch |
| Callback rate (rolling 7 days)Three callbacks tied to one tech. Likely a parts issue. Pull the jobs before end of day. | 6.2% | < 4% | Poor |
| Zero-ticket jobs (today)Two are warranty; one is unexplained. Follow up before close of business. | 3 | 0–1 | Watch |
| Memberships sold (MTD)Halfway through the month at 70% of goal. Need to run a short tech contest this week. | 14 | 20 | Watch |
| Jobs completed (today)Strong completion rate; capacity is well-utilized. | 22 | Good |
Info
Data visibility gap
Most home-service CRMs will show you service revenue and job counts after the fact. The gap is the word 'after.' A tech who runs six zero-ticket or low-ticket jobs in a Tuesday afternoon is invisible until a report runs on Friday, by which time the pattern has already happened again on Wednesday and Thursday. A live service dashboard closes that gap so the manager can intervene while the schedule is still moveable.
A live service dashboard, mid-afternoon
This is the kind of view a service manager or operations leader keeps on the web or on the office TV while the afternoon schedule runs. Figures are illustrative.
Figures are illustrative. Datacube builds your service board around the CRM, accounting system, and KPI definitions your team already uses. 'Cube Cooling' is a fictional demo company.
Service KPIs: what each metric reveals and what to do about it
| KPI | What it reveals | Action when it turns red |
|---|---|---|
| Revenue per tech | Whether each tech is reaching their revenue potential on the jobs dispatched to them | Review job types assigned; check if low-revenue jobs are filling a high-potential tech's day |
| Average ticket | Whether techs are presenting full-scope repair options or selling only the minimum fix | Run a same-day role-play on presenting options; review the specific jobs dragging the average |
| Callback rate | Quality of the repair: a high callback rate means the problem was not fixed correctly or completely | Pull the job records, identify whether it is a parts issue, a process gap, or a specific tech pattern |
| Zero-ticket jobs | Jobs that closed with no revenue, which can indicate warranty work, mistakes, or missed billing | Verify warranty legitimacy; flag unexplained zero-ticket jobs for dispatcher follow-up the same day |
| Memberships sold / lost | Whether the service team is building recurring revenue or leaving it on the table | Launch a short membership contest; highlight the top tech on the office TV to create visible accountability |
| Capacity utilization | Whether the schedule is full; idle capacity is direct revenue loss on a fixed-cost labor day | Cross with demand: if inbound calls are high but capacity shows slack, check the dispatch workflow |
A daily coaching cadence built around the service dashboard
01 Morning: set the goal line before the first truck rolls
Open the service board as the schedule populates. Confirm tech assignments align with revenue targets, flag any gaps in capacity, and put the day's membership goal on the office TV. When the team sees the number before they leave, they are more likely to ask about it on every call.
02 Midday: check the real-time snapshot
By noon you can see revenue per tech, average ticket so far, and whether any zero-ticket jobs need a follow-up call. If one tech is running well under target, a five-minute dispatcher conversation can redirect the afternoon before it compounds.
03 Rolling: watch the callback rate before it becomes a pattern
Set a rolling seven-day callback view on the board. One callback in a week is noise. Three from the same tech inside four days is a signal worth investigating today: pull the jobs, check the parts used, and decide whether a ride-along is warranted.
04 End of day: lock in the data before it goes stale
Review zero-ticket jobs before the CRM closes out. Confirm unexplained ones are investigated. Log coaching notes. When a tech's average ticket is 20% below the team on a Tuesday, that coaching conversation is more useful Tuesday evening than at the Friday staff meeting.
05 Weekly: tie performance to goals and contests
Run a one-on-one built on each tech's week-to-date numbers from the dashboard. Set individual revenue-per-tech and average-ticket targets. If membership numbers are lagging, launch a seven-day contest. Datacube can display the leaderboard in rotation on the office TV so the pressure is visible without being a separate conversation.
Warning
Owner takeaway
Average ticket is a lagging indicator if you only see it monthly. The decision it drives (coaching a tech to present full repair options, adjusting call types, running a contest) needs to happen in the same week as the dip, not the following month. A live service dashboard does not change the data, it changes when you see it, and that timing is the entire value.
What a service dashboard from datacube tracks
Revenue per tech, live
Track each tech's daily and month-to-date revenue against their personal goal. Sort by highest to lowest and use the leaderboard to drive peer accountability without a manager having to say a word.
Average ticket by tech and job type
Break down average ticket by individual and by service category so you can tell whether a low average is a tech-specific coaching issue or a systemic pricing gap on a particular job type.
Callback tracking
Flag callbacks as they are logged in the CRM and surface the pattern by tech, by trade, and by job type. Catch a rising callback rate before it becomes a reputation or warranty-cost problem.
Zero-ticket job alerts
Every job that closes with no revenue gets a visible flag. Managers can distinguish warranty work from unexplained zero-dollar closes and follow up the same day rather than discovering the gap in a month-end audit.
Membership sold and lost
Track membership sales per tech, MTD and YTD, and run contests to drive conversion. Also surface memberships that lapsed or were cancelled so the service team can see the retention picture alongside the sales number.
Goals and contests on the office TV
Put the service team's revenue goal, average-ticket target, and membership count on a rotating office-TV display. Real-time visibility drives self-accountability during the shift, before the manager has to intervene.
Connecting your service data to the dashboard
A service dashboard is only as good as the data feeding it. Datacube is designed to consolidate job data, revenue, and tech performance from the CRM and operations tools your team already uses. For teams using ServiceTitan, Workiz, or Housecall Pro, the service board can be built to pull jobs completed, revenue per visit, callbacks, and zero-ticket flags without exporting a spreadsheet. When connected to QuickBooks, labor cost and gross margin sit alongside the revenue view so an operations leader can see profitability, not just top-line job revenue.
The build process takes approximately four to six weeks and is done for you by the datacube team. That includes connecting your data sources, configuring the KPI definitions your service manager already uses, and building the visual layout for web, mobile, and office TV. You supply access to your tools; the datacube team handles the rest.
Service data sources datacube is designed to consolidate
Mention of a platform does not imply official partnership or marketplace certification.
The short version
- A service dashboard for contractors shows revenue per tech, average ticket, callbacks, and zero-ticket jobs in real time, not at month end.
- The value is timing: catching a bad pattern mid-week lets a manager intervene while the schedule is still recoverable.
- Goals, leaderboards, and contests on the office TV create accountability without a manager having to repeat the same coaching conversation.
- Datacube builds the service board around your CRM, your KPI definitions, and how your team measures a good day in the field.
Service dashboard FAQs
See your service board, live
Bring a few months of service data and we will show you what a real-time service dashboard looks like built around your techs, your CRM, and how your team defines a great day in the field.
Keep exploring
Related
Go deeper