The number that starts arguments
ServiceTitan Close Rate: Why One January Can Read 0% and 100%, and Which Version Belongs on Your Screen
Three people open three screens and read three close rates for the same technician. None of them is lying. ServiceTitan uses the name for more than one calculation, and this page sorts them out, then shows what to do with the one you keep on your ServiceTitan dashboard.
November 13, 2026 · 12 min read
The short answer
ServiceTitan defines close rate as closed opportunities divided by sales opportunities, times 100%. A closed opportunity is a completed job whose sold estimates meet the job type's sold threshold. Conversion rate is the invoice-based cousin. Reports disagree because the legacy Technician Performance Board labels conversion as Close Rate, threshold changes are retroactive, and the Close Rate, As Of and Rolling columns credit late sales differently.
On this page
- Three screens, three close rates, one sales meeting
- Closed opportunities over sales opportunities, in ServiceTitan's words
- Conversion rate, and the legacy board that borrows the close rate label
- Close Rate, As Of and Rolling: one January, two verdicts
- Ten sales calls, worked through with invented numbers
- Work that moves a close rate, and settings that only move the math
- Monday's close rate routine, and where DataCram fits
Three screens, three close rates, one sales meeting
The sales meeting starts at 7:30. The service manager brings a close rate from the dashboard. The comfort advisor brings a different one from a report he likes. The owner brings a third, printed from a board taped beside the coffee maker years ago. Twenty minutes later nobody has mentioned a customer, and the meeting has become a referendum on arithmetic. Everyone is right about something, which is the worst result a meeting can have. Then technician scorecards put it to work.
This does not mean anyone is bad at math, or that ServiceTitan's reports are wrong. ServiceTitan applies the words close rate to more than one calculation, and it says so itself. Its KPI Matrix, as read in ServiceTitan's help center in November 2026, marks report KPIs that match the standard definition with a green check, partial matches in yellow and mismatches in red. It also notes that "Only 20 legacy reports are represented in the matrix."
This page takes the number apart: ServiceTitan's definition, the invoice-based cousin that borrows its name, three date versions in one template, and Monday's routine. It sits beside average ticket and booking rate. For why two ServiceTitan screens disagree in general, read reading ServiceTitan reports, and for joining reports with ad and call data, our integration dashboards page.
Closed opportunities over sales opportunities, in ServiceTitan's words
ServiceTitan's help article What's a sold threshold, read in November 2026, gives the formula plainly: "close rate = [count of closed opportunities] / [count of sales opportunities] * 100%". Each half of that fraction has its own definition, and each leans on a setting your company controls. The setting is the sold threshold, which the article calls "a job type setting that determines the dollar amount subtotal when a job is considered closed or converted."
| Term | ServiceTitan's wording | What it means in practice |
|---|---|---|
| Closed opportunity | "A completed job where the total of sold estimates meets the sold threshold." | The visit is finished and the estimates signed on it add up to at least the job type's line. |
| Sales opportunity | "A job that is not No charge or Unconvertible." | Nearly every sales call lands in the denominator, signed or not. |
| Sold threshold | "You assign different sold thresholds based on job type." | Each job type carries its own line, so the close rate depends on how job types are set up. |
| No Charge job | It "cannot decrease" the close or conversion rate "but can increase either rate if the sold threshold is met or breached." | A free visit that turns into a sale helps the number. One that does not stays out of it. |
| Open, Won, Dismissed | "An opportunity is open until at least one of the created estimates is closed or the opportunity is dismissed." | Sold at or above the threshold is Won. Sold below it is Dismissed, which is not a close. |
The No Charge rule comes from ServiceTitan's dashboard business metrics article, and the open, won and dismissed statuses from its glossary. One glossary line deserves a second reading: "Every closed estimate is a sold estimate. Not every sold estimate has necessarily been closed." A technician can sell a small add-on below the line and still not have closed. He sold something; the report says he did not close. Both are true.

A smaller wrinkle: the glossary says closed estimates have "a subtotal equal to or greater than the Sold threshold," while ServiceTitan's close rate troubleshooting article says "To count as a Close, an estimate must have a subtotal greater than the Sold Threshold." An estimate signed for exactly the threshold sits on that line; test one job to see which way your account counts it.
Conversion rate, and the legacy board that borrows the close rate label
Close rate has a sibling that reads a different document. The troubleshooting article puts it in two phrases: Close Rate is "Exclusive to sales and estimates." Conversion Rate is "Exclusive to revenue and invoices." The sold threshold article gives conversion as "[count of converted opportunities] / [count of job opportunities] * 100%", where a converted opportunity is "A completed job where the invoice subtotal meets the sold threshold." Service, maintenance and install visits live there. Sales calls live in close rate.
Now the trap. In the legacy Technician Performance Board, the column labeled Close Rate is described as "The technician's conversion rate within the report date range." Its calculation is "([Jobs] - [Estimates]) / [Jobs]", and in that report "Estimates" means "completed jobs with an invoice totals less than the sold threshold." So the oldest board in the building uses one metric's name, a second metric's formula, and a column called Estimates that counts invoices.
None of this is hidden; ServiceTitan wrote it down. When a technician quotes the board and a manager quotes the dashboard, they are not disagreeing about performance. They are holding two calculations that share a label. Settings shift conversion too, and ServiceTitan's articles, read in November 2026, name the main ones.
- The dispatch fee. ServiceTitan's advice is to "set the sold threshold for a job type to a minimum of $1 over your dispatch fee." Its own example is a service job with "a $49 dispatch fee" set to "$50." Without that, a visit that collects only the fee counts as converted.
- A threshold of zero. In ServiceTitan's words, "With a $0 sold threshold, conversion rates are always 100%." The legacy report guides add that "The default sold threshold is $0.00," so an older account may still carry zero on a job type or two.
- Sold now, done later. ServiceTitan "automatically changes jobs to unconvertable for the Conversion Rate, only if there is a Sold estimate that is performed later." With Perform Work Now, "The estimate is Closed and the job is Converted."
- The Daily Huddle. The legacy Daily Huddle guide computes conversion as "([Jobs Completed] - [Estimates]) / [Jobs Completed] * 100," which is not the dashboard's formula either.
Close Rate, As Of and Rolling: one January, two verdicts
The newer Technician Performance report template offers three close rates side by side. Its help article, read in November 2026, gives the formulas: "Close Rate Rolling: [closed opportunities] / [sales opportunities As Of]" and "Close Rate As Of: [closed opportunities As Of] / [sales opportunities As Of]," next to the plain Close Rate.
Then it gives an example worth memorizing. An estimate is built on a job completed January 1 and sold February 1. For January, "Close Rate is 0%," while "Close Rate As Of is 100%." Same technician, same signature. One column says he struck out in January; the other says he went one for one. The difference is when the sale gets its credit, and whoever picked the column made that choice.
The article adds a note on dates: the filter follows "the job's completion date if the job is not sold. However, if an estimate has been sold, the Sales Opportunity date filter corresponds with the estimate's sold-on date." Put plainly, last month's close rate is not finished when last month ends, and which column you hold decides whether it keeps moving.
Ten sales calls, worked through with invented numbers
An illustration, with numbers we made up, applying the definitions above and following the pattern of ServiceTitan's January example. A comfort advisor runs ten sales calls in one month, and all ten jobs are completed. The sales job type carries a $1 sold threshold, the figure ServiceTitan's article gives for sales job types. Your own column tooltips are the final word on how your account counts.
- 1.Four jobs end with signed estimates well above $1. Each is a closed opportunity, status Won.
- 2.Three jobs end with options presented and nothing signed. Each stays an open sales opportunity until an estimate closes or someone dismisses it.
- 3.One job was booked as No Charge and nothing was sold. It leaves the denominator, because a No Charge job cannot lower the rate.
- 4.One job was booked as No Charge, and the homeowner bought a replacement anyway. It counts as a close, because a No Charge job that meets the threshold can raise the rate.
- 5.One customer signs two weeks after the month ends. Like ServiceTitan's January estimate, it counts against the plain Close Rate and for the As Of version.
Plain close rate for the month: five closes out of nine sales opportunities, or 56%. The As Of version, run after the late signature, reads six of nine, or 67%. Neither is wrong. Had a homemade spreadsheet kept the unsold No Charge job in the denominator, the month would read five of ten, or 50%, and the advisor would have a grievance he could prove.
Work that moves a close rate, and settings that only move the math
Changes in the work
- Where the lead came from. ServiceTitan's technician scorecards split "Tech Leads" from "Marketing Leads," and the two deserve separate rates
- Follow-up on open estimates, since an opportunity stays open until an estimate closes or someone dismisses it
- What the technician presents and leaves behind: options, a written estimate, a clear next step
- Who rides along with whom, and what they talk about in the truck afterward
Changes in the arithmetic
- A new sold threshold, which ServiceTitan applies retroactively
- More job types marked No Charge, which removes visits from the denominator
- Moving from the legacy board to the dashboard, or from plain Close Rate to As Of
- A different business unit filter on the same report
The retroactive rule deserves its own warning. ServiceTitan's troubleshooting article says "Changes to the Sold Threshold in the job type settings are retroactive." Change a threshold in June and last March changes with it. A spreadsheet that saved March as a typed number now disagrees with ServiceTitan's March. On dashboards we build, a threshold change goes on the screen with its date, so the jump in the history line has a caption instead of a mystery.
The left column is where coaching lives. The right column is where a close rate jumps a dozen points over a weekend without one extra signature. Our technician scorecard page shows close rate beside the other per-person numbers, with the comparisons that are fair and the ones that start fights.
Monday's close rate routine, and where DataCram fits
- 1
Pick one definition and print it under the tile
Plain or As Of, estimates or invoices. One sentence, in words, where the number is shown.
- 2
Open the job type settings
Check each sold threshold against your dispatch fee, using ServiceTitan's $1-over rule as the starting point. Write down the date of any change, because it rewrites history.
- 3
Pull the open opportunities
Every unsold estimate from the last 30 days, oldest first, with a name and a phone number. This is the list that actually changes the number.
- 4
Compare each person with their own last quarter
Not with each other across different lead sources, and not with a figure from somebody's blog.
- 5
Save the hard questions for one monthly meeting
What moved, why, and what changes next. That is the job of the monthly numbers review.
If you want this routine on a screen, a custom ServiceTitan dashboard is from $575 to build, depending on complexity, as of November 2026, with a fixed written estimate first and hosting from $55 a month. The API connection goes live the same day. ServiceTitan's Developer Portal says customer-built apps require being "on the Works or Ent Plus package," and its API Terms limit storing API content to 24 hours except where they allow otherwise, so confirm your package and agreement first.
If the screen is fine and the conversation is the trouble, the numbers review is from $575 a month, as of November 2026: a standing session with you or your managers to walk through what moved and what to do about it, with no long contract. Skip both if one person already reads the right report and the team acts on it. DataCram is a San Antonio web studio building since 1999, not affiliated with ServiceTitan, whose name is its trademark; builds fall under web app development, and our work is published.
Questions owners ask about ServiceTitan dashboards and numbers
ServiceTitan's help center, read in November 2026, gives it as the count of closed opportunities divided by the count of sales opportunities, times 100%. A closed opportunity is a completed job whose sold estimates meet the job type's sold threshold. A sales opportunity is any job that is not No Charge or Unconvertible. Other screens use the same name for different formulas, so check the column.
Because the legacy Technician Performance Board's Close Rate column is, by ServiceTitan's own description, a conversion rate built from invoices, while the dashboard's close rate counts sold estimates. Business unit filters and date fields also differ by screen. Our guide to why ServiceTitan reports disagree walks through the other causes.
As read in November 2026, ServiceTitan's rule of thumb is a minimum of $1 over your dispatch fee. Its examples are $1 for sales job types, $50 for a service job with a $49 dispatch fee, and $1 for recall job types. Threshold changes are retroactive, so record the date you change one, or last year's numbers will shift without explanation.
No. ServiceTitan describes Close Rate as exclusive to sales and estimates and Conversion Rate as exclusive to revenue and invoices. Close rate asks whether estimates sold on a sales job met the threshold. Conversion asks whether a service, maintenance or install invoice met it. The same sold threshold setting feeds both, which is part of why they get confused.
It can rebuild the calculation from raw records, such as job types with their soldThreshold and noCharge settings and estimates with soldOn dates, or it can read ServiceTitan's own report output through the Reporting API, whose columns ServiceTitan says may change. Our page on moving ServiceTitan data into a dashboard covers both routes and how each gets checked.
We will not give you a number, because we have not found a sourced benchmark, and the figures passed around come without one. Compare each advisor with their own past quarters, split by lead source, using one written definition. If you want help reading the trend, that is what our ServiceTitan numbers review is for.
Keep reading
- Dashboards by role: techniciansA Fair Technician Scorecard on ServiceTitan Data: Five Numbers and the Arguments They StartClose rate, average ticket, revenue per hour, recalls and memberships per technician, using ServiceTitan's definitions and comparing like with like.
- Same word, different countWhy Two ServiceTitan Reports Disagree, and How Both Can Still Be RightWhy ServiceTitan reports do not match: date fields, sold versus completed, business units and adjustments, in ServiceTitan's own words, plus a tie-out.
- Reporting and dashboardsThe Owner's Screen ServiceTitan Can't Draw Alone: Jobs, Revenue, Calls and Ad Spend TogetherWhat ServiceTitan's built-in reports and custom dashboards cover, and when a custom dashboard that adds ad, call and website data is worth building.
- 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
- The Leads Are Weak: What Glengarry Glen Ross Gets Backwards About Home Service CompaniesHome service owners quote the movie and complain about the leads, then close nearly every real homeowner who calls. The close was never the problem. The stack on the desk is. Where the good leads actually come from, why purchased ones feel weak, and how to own the board instead of racing for scraps.
- Why Your Trade Pages Rank on Page ThreeSearch Console says Google shows your service page, just on page three. Six reasons contractor pages stall in the twenties and thirties, what Google's own guidance says about each, and a one-month plan to move one trade up.
Settle which close rate your team reads
Tell us which screens your managers quote and where they disagree. Someone at DataCram replies with the definitions behind each one and what a single, labeled tile would take.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.