What actually moves average ticket, and when is a rising average a bad sign?
Average ticket is a mix statistic before it is a performance statistic. It moves when job mix changes, when option presentation changes, and when the right technician gets the right call. A rising average with falling job count usually means you are losing small jobs, not selling better. Always read average ticket alongside completed job count and total revenue.
Decompose before you diagnose
A single company-wide average ticket is a blend of a maintenance visit, a capacitor replacement and a full system change-out. Any shift in that blend moves the average without anyone selling differently. A cold snap that fills the board with cheap emergency repairs will drag the average down while the business has its best week of the quarter.
So the first move is always the same: split by job type, then look at the average within each type. Within-type averages reflect behavior. The overall average reflects mix. Confusing the two produces coaching sessions about a number nobody controlled.
What genuinely raises the within-type average
- Options presented instead of a single price. Presenting a good, better and best path consistently changes outcomes more than any script change.
- Diagnostic completeness. A technician who documents the whole system, not just the failed part, uncovers work the customer did not know to ask about.
- Assignment. Sending the technician with the strongest history on that job type to the calls where the value sits.
- Membership status. Members typically accept recommended work at different rates than first-time callers, which is why membership mix belongs in this analysis.
The failure modes hidden inside a rising average
Three patterns produce a rising average that should worry you. First, small jobs going elsewhere because your schedule cannot fit them, which shows up as a higher average and a lower job count. Second, replacement being recommended where repair was viable, which raises the average now and costs you trust later. Third, a reporting change, such as a job type being re-coded, that moves the average with no operational change at all.
The third one is more common than people expect. Whenever a metric jumps without an obvious cause, check whether someone changed a configuration in the operating system before you build a theory around it.
Making the comparison fair
Comparing technicians on average ticket without controlling for the calls they were given is unfair and everyone knows it, which is why the metric loses credibility fast. Comparing within job type, within membership status and within season is defensible.
The same discipline applies to evaluating how work is presented: the point is to give managers evidence for coaching conversations, not to rank people on a number the dispatch board handed them. When average ticket is reported next to job counts and mix in one revenue view, those conversations get much easier.
Topics: average ticket · pricing mix · technicians · revenue
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.