ServiceTitan Vocabulary: The Foundation of Accurate Reporting

If your data feels off — booking rates that don't add up, marketing numbers that don't match reality, sales figures that look nothing like your revenue — the problem usually starts with vocabulary. Sydney Biancardi, COO at Iceberg Home Services, joined host Josh Lu on the Mastering ServiceTitan podcast to talk about exactly that: why getting the language right inside ServiceTitan is the precondition for clean data, accurate reporting, and decisions you can actually trust.

Biancardi's path to COO started behind a CSR headset — and occasionally a forklift. Over five years at Iceberg, she touched nearly every role in the company as it grew from nine employees to sixty, and her obsession with data integrity grew alongside it. Her core argument: if you're not speaking the same language as the software, the numbers you're running your business on aren't real.

Read on for the podcast highlights.

Calls, Leads, Jobs, and Opportunities: Getting the Workflow Right

ServiceTitan uses four terms that get treated as synonyms in the real world but mean very different things inside the platform: call, lead, job, and opportunity. Mixing them up doesn't just create reporting headaches — it means your marketing team is celebrating the wrong wins and your operators can't pinpoint where revenue is actually being lost.

Here's how the workflow actually flows in ServiceTitan:

• Call — any inbound contact

• Lead — a call where someone is requesting service

• Job — what a lead becomes once it's booked

• Opportunity — a job where something can be sold

"Not every call is a good call," Biancardi says. "I think our number is 20% of all calls are leads, and so that's something that's major for our marketing team to see. Whenever someone calls in, there's only a 20% chance that call is actually a lead of someone requesting service."

That distinction changes the entire conversation with marketing. When Iceberg's team was looking at total call volume and calling it a win, the underlying lead count told a very different story. Once the team got vocabulary locked in, they were able to layer on a metric they'd never had before: lead-to-opportunity rate, or LOP. Of 500 leads booked at a 90% rate, only about 45% of those jobs become true opportunities — the ones where a tech actually has something to sell.

Estimates vs. Invoices: Why the Workflow Matters

One of the most common data problems Biancardi sees — and one Iceberg lived through firsthand — is bypassing the estimate step and adding everything directly to the invoice. It feels easier in the moment, especially when work is being done same-day or next-day. The downstream cost is significant.

For roughly the first six months on ServiceTitan, Iceberg did exactly this. The result: $800,000 in revenue and $0 showing in sales.

"Sales and revenue I know can be used interchangeably in the real world as well. But in ServiceTitan they're literally the complete opposite side of the same coin," Biancardi says.

When a technician creates an estimate and the customer agrees, ServiceTitan gives two options: Perform Work Now — which immediately moves the estimate to the invoice and converts it to revenue — or Perform Work Later, which holds it on the follow-up tab as work in progress until it's linked to a scheduled job. Skipping the estimate entirely means none of that tracking exists. Close rate shows zero. Sales show zero. And if a part needs to be ordered and someone forgets to add the appointment, there's nowhere for that job to live while it waits.

Getting into the estimate workflow unlocked everything else: close rate visibility, average ticket analysis, multi-option presentation by technicians, and accurate job costing across diagnostic and installation stages — which had previously been lumped onto a single invoice.

Cleaning Up Abandoned Calls and Booking Rate

Before Iceberg could trust its booking rate, it had to fix what was feeding it. The culprit: unclassified abandoned calls. In ServiceTitan, any abandoned call over one minute that isn't attached to a CSR and isn't classified counts as a lead by default. When 80% of calls weren't being classified, the booking rate was meaningless — something like 17%, which the team correctly identified as inaccurate and simply stopped watching.

The fix was procedural before it was technical. Every CSR was required to classify every abandoned call, every time. No exceptions. By end of shift, the count should be zero. Once that habit was in place, Biancardi's team went into call reason settings and configured which reasons automatically flag a call as a lead — and which don't.

Vendor calls, spam, follow-ups, out-of-service-area inquiries — all marked as not a lead automatically when the CSR selects the right classification. Calls where a customer didn't book because of a dispatch fee or needed to check with a spouse? Still a lead, even though no job was booked. That distinction matters for understanding where in the funnel you're losing people.

Job Types, Opportunities, and Close Rate Accuracy

Once the call-to-lead workflow was clean, Biancardi's team went deeper into what happens after a job is booked. The focus: making sure close rate reflects real selling situations, not jobs where nothing was ever expected to be sold.

In ServiceTitan, each job type has a "no charge by default" checkbox. When selected, that job type won't count as an opportunity — and therefore won't factor into close rate. Iceberg uses this for recalls, labor warranty calls, and part installs. If a tech runs a recall, it shouldn't count against their close rate. If they do happen to sell something on that job, ServiceTitan is smart enough to flip it to an opportunity automatically.

Job types also support a sold threshold — a minimum dollar amount that has to be sold before a job counts as closed. Iceberg's diagnostic fee is $79, so their sold threshold is $80. Selling just the diagnostic doesn't count as a close. For part installs, the threshold is zero, so any sale counts. This level of precision means the close rate numbers are actually worth reviewing.

"Years ago it was our top salesman had more revenue than our installer, and it was just a little messy and it didn't make ton of sense," Biancardi says. Once estimates were in place and job types were correctly configured, the numbers finally told a coherent story.

Dashboards, Reporting, and What Comes Next

With clean foundational data, the reporting layer becomes genuinely useful. Biancardi's team runs department-specific dashboards for sales, call center, marketing, inventory, procurement, install, and dispatch — each customized for the person using it, pulling live data up to the minute.

For recurring data needs, she leans on scheduled reports — technician performance, payment status, whatever the team needs — delivered by email at 6 AM without anyone having to pull them manually. Dashboards for live visual tracking, scheduled reports for consistent operational data.

The next frontier for Iceberg is marketing quality scoring: rating opportunities on a one-to-five star scale to measure not just whether a lead converted, but how valuable it actually was. It's a layer of analysis that only becomes possible once the foundation — vocabulary, workflow, classification — is solid.

"ServiceTitan vocabulary is so important because if you're not speaking the same language as the software, your data is never going to be right. You have to understand how the software categorizes a lead versus a booking," Biancardi says.

Sydney Biancardi recently joined Josh Lu on the 'Mastering ServiceTitan' podcast to discuss:

• [3:07] The importance of clean data and common language

• [13:11] ServiceTitan implementation, SOPs, and micromanagement

• [21:23] Why tracking booking rates and abandoned calls is a gamechanger

• [26:35] A deeper dive into the differences between jobs and opportunities

You can find this interview and many more by subscribing to Mastering ServiceTitan on Apple Podcasts, on Spotify, or here.