One word, seven averages
Average Ticket in ServiceTitan: Seven Averages Wearing One Name, and the Median That Keeps Them Honest
One system replacement can make a slow week look like a record. Average ticket is the number owners quote most and question least. Here is how ServiceTitan counts it, where the other averages hide, and a one-minute check that tells you whether to believe the tile on your dashboard.
November 13, 2026 · 10 min read
The short answer
ServiceTitan calls the opportunity job average, average revenue from opportunity jobs only, its primary average ticket metric and the one on its dashboard. Other screens average differently: total job average includes no charge jobs, the legacy boards fold in adjustments or use invoice totals, and the Customer Record card skips jobs under a dispatch fee cutoff that defaults to $85. Check any average against the median.
On this page
- The week one replacement made everybody look brilliant
- Opportunity job average, ServiceTitan's chosen meaning
- An $85 line on the Customer Record, a $0 line in the legacy reports
- Sold Tuesday, completed Friday: sales and revenue on different calendars
- The median, a one-minute lie detector for the mean
- Ticket growth that customers do not resent
- A Monday look at the ticket, and what DataCram sells
The week one replacement made everybody look brilliant
An illustration, with numbers we invented. A plumbing and heating shop completes thirty service calls in a week, and they total $10,500. The average ticket is $350. On Friday one crew finishes a $14,000 system replacement. Now thirty-one jobs total $24,500, and the average ticket reads $790. The Monday email goes out with a celebratory subject line. Nobody on the service side did anything different.
The next week has no replacement, the average drops back to $350, and the same email now reads like an indictment. Two weeks of identical service work have produced a hero and a villain. This is the mean doing exactly what a mean does: it gives a big job a loud voice. The fix is not to stop reporting it. The fix is to know which average you are looking at, and to put a second number beside it.
This page is one of the number explainers in our ServiceTitan dashboards section. It pairs naturally with close rate, since the two together describe a sales visit, and with revenue per hour, which asks what all that ticket cost in time. If your average ticket comes up mostly in technician arguments, our technician scorecard covers fair comparisons, and our page on ServiceTitan reporting with outside data covers joining tickets with ad spend.
Opportunity job average, ServiceTitan's chosen meaning
ServiceTitan settles which average it means. Its dashboard business metrics article, read in November 2026, says: "Opportunity job average: Average revenue from only opportunity jobs. This is the metric on the dashboard and the ServiceTitan primary metric for average ticket." The same article lists two neighbors, "Total job average: Average revenue from all jobs including no charge" and "Converted job average," which averages "only opportunity jobs where the sold threshold has been breached."
Then the legacy reports and the Customer Record add their own. None of them is wrong. Each answers a slightly different question, and the trouble starts only when two of them meet in the same meeting under the same name. Here is the set, as ServiceTitan's help center described them in November 2026.
| Average | Where it appears | What it divides | Watch for |
|---|---|---|---|
| Opportunity job average | Modular Dashboard | Revenue from opportunity jobs only | Depends on which jobs are No Charge |
| Total job average | Dashboard metric list | Revenue from all jobs, no charge included | Free recall visits pull it down |
| Converted job average | Dashboard metric list | Opportunity jobs that breached the sold threshold | Moves with every threshold setting |
| Closed average sale | Modular Dashboard | Total sold estimates divided by closed opportunities | A sales number, not a revenue number |
| Job Avg, legacy Technician Performance Board | Legacy board guide | "[Revenue] / [Jobs]", splits applied | "Includes adjustment invoices" |
| Job Avg, legacy Daily Huddle | Daily Huddle guide | "Average invoice total for completed jobs" | Invoice total, not income items |
| Average Job Total card | Customer Record FAQ | One customer's jobs, several jobs in one project counted as one | Skips jobs under the dispatch fee threshold |

One more sits nearby. ServiceTitan's dashboard article says "Closed average sale" "takes the total of all sold estimates and divides it by the number of closed opportunities, not the number of estimates." A comfort advisor who sells two estimates on one visit gets one closed opportunity, not two. That is a defensible choice, and it is also why his own tally of estimates never matches the screen.
An $85 line on the Customer Record, a $0 line in the legacy reports
The Customer Record's Average Job Total card skips jobs below a dispatch fee threshold whose "default is set to $85," in the words of ServiceTitan's FAQ as read in November 2026. The idea is sensible: a diagnostic visit that collected only the fee says little about what a customer is worth. But it means the customer card and the dashboard are averaging different piles of jobs, and the card's line may not match your actual fee.
The legacy reports start from the opposite end. Their guides say "The default sold threshold is $0.00," while ServiceTitan's current guidance is to set the threshold at least $1 over the dispatch fee. ServiceTitan also states that "With a $0 sold threshold, conversion rates are always 100%." It follows that a job type left at zero makes every job count as converted, so the converted job average quietly becomes the opportunity job average for that job type.
The legacy guides add one more fixed line: "Replacement rate: [Jobs Completed whose Total >= 3000] / [Jobs Completed] * 100," with a default "Service/Replacement threshold is $3000." That line is a ServiceTitan default, not a fact about your market. If your replacements usually run above or below it, the legacy replacement rate is counting a different set of jobs than your sales manager has in mind.
Sold Tuesday, completed Friday: sales and revenue on different calendars
Average ticket is a revenue number, and revenue in ServiceTitan keeps a different calendar from sales. The dashboard article defines "Total Sales: Total of sold estimate subtotals," adding that "Date filters apply to estimate sold on date." Completed Revenue is the "Sum of income items on completed job invoices," and "Most of the metrics related to revenue share the date filter of Job Completion Date." A job sold in March and installed in April lands in March's sales and April's revenue.
ServiceTitan says so without apology: "The Total Sales will not always match Completed Revenue, but these metrics will still be correct." Its listed reasons include an install job that "has not been completed," revenue "that did not come from a sold estimate," estimate items "not connected to an income GL account," and invoice items that "are updated or removed" after the sale. Each one shifts a ticket average too, and our guide to why ServiceTitan reports disagree covers the date fields in more depth.
- Only income items count on the dashboard. ServiceTitan says "Only invoice items connected to an Income GL Account will show on the dashboard." An item mapped to the wrong account vanishes from the average.
- Adjustments depend on the screen. Dashboard Total Revenue includes adjustment revenue; the Business Unit Performance template says of its Completed Revenue, "Adjustment invoices are not included."
- Technician averages are split. In the Technician Performance template, Completed Revenue is "adjusted by technician Split," and by default 100% goes to the first technician assigned.
- Cents vanish. ServiceTitan's mismatch article shows $24,291 on the dashboard against $24,291.32 in a report, and says it matches exactly.
The median, a one-minute lie detector for the mean
Our advice, not a ServiceTitan rule: show the median ticket beside the average. The median is the middle job when you line them up by size. A single giant ticket cannot drag it far, so when the two numbers sit close together, the average is describing a typical job. When they drift apart, something big or strange is in the pile, and you should go look before anyone sends an email.
Here is an illustration with eleven invented service tickets: $89, $89, $129, $185, $240, $310, $365, $420, $610, $1,150 and $9,800. They total $13,387. The average is about $1,217. The median, the sixth job, is $310. Remove the $9,800 job and the average of the other ten falls to about $359. One ticket was responsible for more than two thirds of the average.
- When the mean and median are close, read the average as a fair picture of the typical visit.
- When the mean runs far above the median, find the large jobs and ask whether they belong in this tile or in a replacement tile of their own.
- When the median falls while the mean holds, more small visits are coming in. That may be maintenance season, not a slump.
- Split by job type before splitting by technician. Service, maintenance and replacement visits are different animals, and averaging them together flatters whoever ran the most replacements.
Ticket growth that customers do not resent
Before you try to raise the number, make sure the number is measuring the right jobs. Then the useful levers are mostly about what happens in the driveway. These are observations from our side of the table, not promises, and none of them comes with a percentage, because we have no sourced figure to give you.
The mix, before the people
A season heavy with maintenance visits lowers the average without anyone working worse. Compare like job types before you coach.
What gets presented
A technician who offers one option gets one answer. Written options left with the homeowner give the follow-up call something to talk about.
The pricebook
If items carry stale prices or no sold hours, both the ticket and the hours behind it are off. See revenue per hour.
What it cost to earn
A bigger ticket with thinner margin is not progress. Read it beside gross margin per job.
A Monday look at the ticket, and what DataCram sells
- 1
Name the average
Write opportunity job average, or whichever you choose, under the tile in plain words.
- 2
Put the median beside it
If the two are far apart, open the list of the five largest tickets before anything else.
- 3
Split by job type
Service, maintenance and replacement each get their own line, so a busy tune-up month does not read as a pricing problem.
- 4
Check the settings log
Any change to No Charge job types, sold thresholds or GL mapping since last month explains a jump before a person does.
We do not publish a good average ticket, because we have no sourced one, and the targets that circulate come without a source or date. A custom ServiceTitan dashboard can show mean, median and job type splits on one tile, with the list one click away. It is from $575 to build, depending on complexity, as of November 2026, with a fixed written estimate first, plus hosting from $55 a month. The API connection goes live the same day.
ServiceTitan's Developer Portal says customer-built apps need the "Works or Ent Plus package," and its API Terms, last updated April 15, 2026, cap storing API content at 24 hours except where they permit more. Confirm both against your own agreement. If you would rather talk the numbers through, the monthly numbers review is from $575 a month, as of November 2026, with no long contract. DataCram is a San Antonio studio, building since 1999, and not affiliated with ServiceTitan. The build work falls under web app development, and an owner's morning dashboard is where a ticket tile usually lives.
Questions owners ask about ServiceTitan dashboards and numbers
As read in ServiceTitan's help center in November 2026, the dashboard shows the opportunity job average: average revenue from opportunity jobs only. ServiceTitan calls it its primary metric for average ticket. Total job average, which includes no charge jobs, and converted job average, which counts only jobs that breached the sold threshold, are separate metrics.
The Customer Record card skips jobs below a dispatch fee threshold whose default, per ServiceTitan's FAQ, is $85, and it counts several jobs in one project as one job. The dashboard's opportunity job average uses a different set of jobs. Both can be correct while disagreeing. Check the card's threshold against your real dispatch fee.
ServiceTitan's average ticket is a revenue measure, dated by job completion. Total Sales is a separate figure, dated by the estimate's sold-on date. Use revenue for ticket and sales for the sales team's pipeline, and label which is which. ServiceTitan itself says the two will not always match and both are still correct.
Not better, different. The average tells you total revenue per job; the median tells you what a typical job looks like. Showing both is our advice, because a wide gap between them flags a few large jobs pulling the average. It costs nothing to calculate and saves a lot of misplaced praise and blame.
In ServiceTitan's Technician Performance template, revenue is adjusted by technician split, and by default 100% of the split goes to the first technician assigned. If splits are left at default, the second technician on a big install may show none of it. Set splits deliberately before comparing technicians, as our technician scorecard page explains.
ServiceTitan's report column aggregation options, as its help center listed them in November 2026, are count, count distinct, sum, average, minimum and maximum. A custom dashboard can read invoice records through the API, with fields such as total, subTotal and each item's generalLedgerAccount, and compute a median itself. Our page on ServiceTitan API data explains how records reach a dashboard and how the totals get checked.
Keep reading
- The number that starts argumentsServiceTitan Close Rate: Why One January Can Read 0% and 100%, and Which Version Belongs on Your ScreenHow ServiceTitan counts close rate, why the legacy board's Close Rate is really conversion, and how a sold threshold rewrites history. A worked example.
- Revenue minus what it tookGross Margin per Job: What Belongs in Direct Costs, What the IRS Means by Gross Profit, and Why the Two DifferRevenue minus direct costs, job by job. ServiceTitan's job costing formulas, the IRS gross profit definition, and the costs that quietly go missing.
- Module: KPI dashboardA Field Service KPI Dashboard Built on Your Own Data: Ten Numbers, One Screen, No Package UpgradeThe ten numbers an HVAC or plumbing owner acts on, each defined and built from your own database on one screen. From $575 to build, by complexity.
- The build, in fullA Custom ServiceTitan Dashboard for One Role, With the List Behind Every NumberA custom ServiceTitan dashboard for one role: written definitions, a visible refresh time, lists one click away. From $575, hosting from $55 a month.
- Once a month, out loudThe Monthly ServiceTitan Numbers Review: What Moved, Why It Moved, and What Changes on MondayA monthly numbers review for ServiceTitan owners and managers: what moved, why, and what to do next. From $575 a month, no long contract, honest about fit.
- Dashboards by role: ownerA ServiceTitan Owner Dashboard for 7:45 a.m.: Eight Numbers, Each With Its List Behind ItThe eight numbers a home service owner checks before 8 a.m., read from your ServiceTitan account, each defined and one click from its list. From $575.
- Everything in ServiceTitan DashboardsSee the section
From the Insights desk
- What an After-Hours AI Answering Service Can and Cannot BookAI answering services now book visits for contractors around the clock. What one can safely book, which calls it must hand to a person, how handoff fails, and the consent and recording questions to settle before it answers your phone.
- The Garage Door, Locksmith and Appliance Repair Website: The First Five SecondsSomeone locked out, trapped behind a broken garage door or staring at a warm fridge gives your website about five seconds on a phone. What the first screen must show for each trade, and the speed, trust and booking that back it up.
See your average ticket beside its median
Tell us which average your team quotes and which screen it comes from. Someone at DataCram replies with what that number includes and what a mean, median and job type tile would take to build.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.