The trip nobody invoices

Callback Rate and Recall Rate: Counting Return Visits Fairly When ServiceTitan Publishes No Formula

A callback never shows up on a revenue screen, because nobody pays for it. It shows up in a lost slot, a second truck roll and a customer who is now less sure about you. Counting it fairly takes a definition, and ServiceTitan leaves the rate to you.

November 13, 2026 · 10 min read

dash.acmeheatingandcooling.com · recall check, April
Recall jobs matched to the visits they fix
Three recalls traced, one filed as warranty
  1. job 5120 recall, links to job 4987 completed Mar 4
  2. job 5133 recall, links to job 5012 completed Mar 11
  3. job 5141 recall, part failure booked as warranty work
  4. job 5150 same address in 30 days, not marked as recall
  5. March rate maturing until the 30-day window closes
Illustrative: a sample recall log for a fictional heating and cooling company

The short answer

ServiceTitan treats a recall, which it also calls a callback, as a No Charge job that fixes a persisting issue from an earlier job and points to the original in its Is recall for field. It reports recall counts by technician, but we found no published recall rate formula. Our definition, labeled as ours: recalls linked to jobs completed in a period, divided by those completed opportunity jobs.

On this page
  1. Thursday, same house, same rattle
  2. What ServiceTitan writes down about a recall
  3. The recall rate we would defend in front of a technician
  4. Eighty jobs, three recalls, two honest rates
  5. Counting fairly: the arguments a callback rate starts
  6. Root causes that deserve a Monday morning
  7. A callback tile, a monthly review, and the prices

Thursday, same house, same rattle

Tuesday, a technician replaces a capacitor and the condenser hums back to life. Thursday, the homeowner calls: the rattle is back. Friday morning a second truck goes to the same driveway. No invoice is written. The slot that truck filled could have been a paying call, and the homeowner now tells a neighbor the story with a slightly different ending than the one you would prefer.

That visit is invisible on most revenue screens, by design. It earns nothing, so revenue does not see it. It costs a technician's time, fuel and a slot, so the business very much feels it. A callback rate is the attempt to make that cost visible. Done badly, it becomes a weapon in the shop. Done fairly, it is one of the most useful numbers a service manager can bring to a ride-along.

This is one of the number explainers in our ServiceTitan dashboards section. It connects to revenue per hour, since recall visits consume hours without revenue, and to gross margin per job, since a recall quietly takes margin from the job it fixes.

What ServiceTitan writes down about a recall

ServiceTitan's glossary, read in November 2026, defines a recall job as "A job to fix a persisting issue from a previously completed job." It adds: "Recalls are No charge jobs and reference the original jobs in the Is recall for field." The sold threshold article settles the vocabulary: "Recall jobs, also known as callback jobs." So in ServiceTitan's terms, callback and recall are one thing.

The glossary also says "Recall and warranty jobs are marked as No charge by default." That matters for the other numbers. A No Charge job "cannot decrease" a technician's close or conversion rate, per ServiceTitan's dashboard article, so a recall does not drag down the rates on our close rate page. ServiceTitan's suggested sold threshold for recall job types is "$1," which keeps a free return visit from counting as converted.

Layered colored-paper scene of two service vans parked outside one small paper house, a curved paper arrow looping back to the door, soft shadows
A callback is the same driveway twice, and only one of those trips was paid for.

For reporting, ServiceTitan's article on recall jobs by technician says to "Use the Technician Performance report template and add the Recall Jobs column," with a warning: "For recall jobs to show in the report, they must be properly marked as recalls in ServiceTitan." The Business Unit Performance template also lists "Recalls Caused." Those are counts. We did not find a published formula for a recall rate, so we will not describe one as ServiceTitan's.

On the API side, the Job Planning and Management API, as ServiceTitan's Developer Portal documented it in November 2026, gives each job a recallForId, described as "ID of the job for which this job is a recall," along with warrantyId, noCharge, jobTypeId and completedOn. That link from recall to original is what makes a fair rate possible.

The recall rate we would defend in front of a technician

Everything in this section is DataCram's definition, offered as a starting point and labeled as ours on any screen we build. Every choice in it can reasonably go another way. The rule that cannot bend is that the choices get written down once and applied to everyone the same way.

DataCram's default callback rate definition, choice by choice, with the reason for each; ServiceTitan publishes no recall rate formula
ChoiceOur defaultWhy
What counts as a recallA job whose recallForId points at an earlier jobIt uses ServiceTitan's own link, not a guess from the address
What it is divided byCompleted jobs that were not No Charge, in the periodFree visits are not chances to cause a recall in the same way
Which month it belongs toThe month the original job was completedThe recall is a fact about the first visit, not the second
How long a recall can trailA window you pick and print, often 30 days to startWithout a window, a failure two years later counts as a workmanship miss
Who it counts againstTechnicians on the original job, by their splitThe recall technician fixed it; the original visit missed it
Warranty workIts own tile, not mixed inA failed part under warranty is a supplier story, not always a workmanship one

Dating by the original job has a cost: last month's rate keeps rising for a while as recalls arrive. We show that on the screen as a rate still maturing until the window closes. The alternative, dating by the recall's own date, mixes this month's callbacks with last month's work, and nobody can say which visits they describe.

Eighty jobs, three recalls, two honest rates

An illustration with invented numbers. A technician completes 80 jobs in March that are not No Charge. By the end of April, three recall jobs point back at his March work through recallForId. One of the three involved a part the office booked as warranty work. The other two were a loose connection and a missed second fault.

  1. 1.All recalls: three of 80, or 3.75%.
  2. 2.Recalls without the warranty case: two of 80, or 2.5%.
  3. 3.Dated by the recall's own date instead, March would show whatever recalls happened to arrive in March, from February's work or earlier, and none of these three.
  4. 4.If one recall was never marked as a recall in ServiceTitan, it disappears from both rates, which is why ServiceTitan warns that recalls must be properly marked.

Two honest rates, depending on whether warranty work belongs in the number. We show both. The technician will ask which one goes in his review, and the right answer is the one you wrote down before the month started, not the one that suits the conversation.

Counting fairly: the arguments a callback rate starts

Usually counts against the original visit

  • The same fault, back within the window
  • A second fault the first visit should have caught
  • A repair left without the part it needed, with no follow-up booked
  • A new install that needs a return trip to work as sold

Usually belongs somewhere else

  • A part that failed under manufacturer warranty, tracked on its own tile
  • A different problem at the same address, booked as a recall out of habit
  • A customer who declined the recommended repair
  • A return trip the first technician scheduled on purpose to finish the job

The right column is why address-matching is a poor recall counter. Two visits to the same house in a month may be a customer who keeps adding work, which is good news. The recallForId link only exists when the office marks a job as a recall, so the fairness of the whole number rests on the CSR's habit at booking. A short written rule for when to mark a recall does more for accuracy than any dashboard. Where callbacks fit in a weekly coaching session is covered in our post on technician scorecards that coach.

Fairness also means comparing like with like. A technician who runs mostly installs will see different callback patterns from one who runs tune-ups. Our technician scorecard page covers splitting comparisons by job type so nobody gets ranked against work they do not do.

Root causes that deserve a Monday morning

A callback rate is a pointer. The work is in the list behind it. These are the patterns we would check first when opening that list, offered as places to look rather than findings. If you want recalls joined with ad and call data from outside ServiceTitan, our integration reporting page covers that build, and our capacity dashboard shows the slots recalls take.

  • One part, one supplier. Several recalls on the same component point at a supply problem, not a people problem.
  • One job type. If recalls cluster on a single job type, the pricebook may allow too little time, or the procedure has a gap.
  • The last call of the day. Check whether recalls cluster on late completions. If they do, routing may be squeezing the final job.
  • Missing parts on the truck. A temporary fix while waiting for a part is a planned return, and should be booked as one.
  • New installs. Commissioning steps skipped on a busy day tend to come back as recalls weeks later.

A callback tile, a monthly review, and the prices

  1. 1

    Write the recall rule for the office

    When a job is marked a recall, and when it is new work at the same address. One paragraph, taped where CSRs can see it.

  2. 2

    Choose the window and the dating

    Original completion month and a window you will keep, printed under the tile.

  3. 3

    Separate warranty work

    Its own count, so a bad batch of parts does not land on a technician's review.

  4. 4

    Open the list monthly

    Read every recall's notes with the service manager. The pattern matters more than the percentage.

A custom ServiceTitan dashboard with a callback tile built on recallForId, the window and warranty split shown, and the recall list one click away is from $575 to build, depending on complexity, as of November 2026. You get a fixed written estimate first, hosting runs from $55 a month, and the API connection goes live the same day. ServiceTitan's Developer Portal limits customer-built apps to the "Works or Ent Plus package," and its API Terms, last updated April 15, 2026, allow storing API content for 24 hours except where they say otherwise. Confirm both.

The monthly numbers review, from $575 a month as of November 2026 with no long contract, is a standing session to walk through what moved and what to do about it; recalls are a natural agenda item. Not worth it if your service manager already reads every recall each week. The data side is on our API data page, builds fall under web app development, and DataCram, building since 1999, is not affiliated with ServiceTitan.

Questions owners ask about ServiceTitan dashboards and numbers

ServiceTitan's glossary, read in November 2026, calls a recall job a job to fix a persisting issue from a previously completed job. Recalls are No Charge jobs and reference the original job in the Is recall for field. Its sold threshold article adds that recall jobs are also known as callback jobs, so the two words mean the same thing there.

We did not find a published formula. ServiceTitan's help center explains how to add a Recall Jobs column to the Technician Performance template, and the Business Unit Performance template lists Recalls Caused, but those are counts. Treat any recall percentage you see as its author's definition, and ask what it divides by.

In our definition, against the technicians on the original job, by their split, because the recall describes the first visit. The technician who returns did the fixing. Separate warranty part failures and decide in writing what happens when a customer declined the recommended repair, so the count reflects workmanship rather than bad luck.

ServiceTitan says recall jobs must be properly marked as recalls to show in its report. A return visit booked as an ordinary job, without the recall link, will not count. The usual fix is a short written rule for CSRs on when to book a recall, plus a monthly look at repeat visits to the same address.

No. Recall and warranty jobs are No Charge by default, and ServiceTitan's dashboard article says a No Charge job cannot decrease a technician's close or conversion rate, though it can raise either if the sold threshold is met. That is why a callback rate needs its own tile; it will not show up in the sales numbers.

We do not publish one, because we have not found a sourced benchmark. A number without a source tends to become a quota, and quotas discourage marking recalls honestly. Track your own rate on one written definition and compare each month with the same month last year. Our general manager dashboard page shows where callbacks sit day to day.

Keep reading

Free · No obligation

Get a callback number your technicians accept

Tell us how recalls are marked in your office today. Someone at DataCram replies with what your current count catches, what it misses, and what a fair callback tile would take.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote