How do I know which calls actually turned into paying jobs?

This page may contain affiliate links from which Blur Studio earns commissions.

Most small businesses can tell you roughly how many calls come in a week. Very few can tell you how many of those calls actually became paying jobs, and that number matters more, since it's the one that tells you whether your phone handling is actually working or just generating noise.

The free setup that gets you most of the way

Contact tags on KrispCall, a cloud phone system for business calls and texting, are included on every plan, including the entry Starter tier, at no extra cost. A tag is just a label you attach to a contact or a call, "won," "lost," "follow-up," "no answer," and once you've got a habit of tagging consistently, you can filter straight to any category and count it. KrispCall's own help center describes tags as being for easy identification and sorting, which is exactly the mechanism you need here, just not pre-built into a named "conversion tracking" feature the way some sales tools market it.

The setup itself is genuinely simple: open a contact's record, tap the exclamation icon to open the tag sidebar, and add or remove tags as the relationship with that contact changes. There's no stated limit on how many tags you can create or apply, so you can get as specific as actually useful, "won - roof repair," "lost - price," "lost - timing," rather than a single flat won/lost split that tells you less.

Step by step: building the habit

1. Pick a short, fixed set of outcome tags before you start, won, lost, follow-up needed, no answer. Keep it to four or five options; too many categories and people stop tagging consistently. Tracking which callers need a follow-up builds on the same tags.
2. Tag immediately after the call ends, not at the end of the day from memory. The accuracy of this entire system depends on tagging happening in the moment, while the outcome is still fresh.
3. Add a reason tag for losses specifically, "lost - price," "lost - timing," "lost - went elsewhere." A flat loss count tells you less than a breakdown of why.
4. Count weekly, not monthly. A weekly count surfaces a bad pattern (a team member's close rate dropping, a specific lost-reason spiking) while you can still do something about it that week.
5. Review the "lost - price" and "lost - timing" tags specifically every month, since those are usually the two categories with an actual fixable lever behind them, pricing confidence or scheduling flexibility, unlike "went elsewhere," which is harder to action directly.

A worked example: a one-person trade business

Say you run a one-person plumbing business and take about 20 calls a week. Without tagging, you have a gut feeling that "most calls go okay." After a month of tagging every call, you might discover the real split is 8 won, 7 lost to price, 3 lost to timing, and 2 no-shows. That's a genuinely different picture than "most calls go okay," and it points at a specific, fixable problem: price objections are your biggest leak, not timing or no-shows. Without the tags, you'd likely have guessed timing was the bigger issue, since a missed appointment feels more memorable than a quiet price-based no after the call ends politely. The tags correct for memory bias, which is the actual value here, not the tagging mechanism itself.

What this setup genuinely doesn't tell you

Tagging outcomes tells you your close rate. It does not tell you which marketing channel, ad, or listing actually generated the call in the first place, since KrispCall doesn't advertise source-based call attribution anywhere on its help center or site, and I found nothing suggesting that's a hidden feature either. If you're running Google Ads, Facebook ads, and a few directory listings at once and genuinely need to know which one is driving calls that convert, that's a different, more specific job: a dedicated call-tracking tool like CallRail, which assigns a unique number to each marketing channel so a call's source is known the instant it rings, not guessed afterward. CallRail's base Lead Tracking plan runs around $50 a month plus usage, which is a real added cost on top of your phone system, so it's worth confirming you actually need channel-level attribution, not just outcome tracking, before adding it. Plenty of small businesses running one or two marketing channels don't need this distinction nearly as much as they think they do; the outcome tagging alone answers "is my phone handling working," which is usually the more urgent question.

Common mistakes that make the numbers useless

The most common failure is inconsistency: one week everyone tags carefully, the next week it slips because things got busy, and the resulting data has gaps that make the close-rate number unreliable right when things got hectic enough that you'd actually want to know what happened. Treat tagging as part of ending the call, not an optional extra step, the same way you'd treat hanging up the phone itself.

The second mistake is tagging too broadly to be useful. A single "lost" tag with no reason attached tells you that something didn't work, but not what to fix. The extra five seconds it takes to pick "lost - price" instead of just "lost" is what turns a vanity number into an actionable one.

The third is checking the numbers once, seeing something uncomfortable, and quietly dropping the habit. The whole value of this system comes from the trend over months, not a single week's snapshot, since any one week can be an outlier for reasons that have nothing to do with how well your team is handling calls.

This looks a little different by business type

For a field service business, the "lost" reasons usually cluster around price and availability (the caller needed someone today and you're booked a week out), so tagging timing losses specifically tells you whether it's worth adding capacity or adjusting how far out you're willing to schedule emergency work at a premium. Calling back the prospects you lost on timing is covered in phoning past enquiries that went quiet.

For an agency fielding new-business enquiries, losses cluster more around fit and budget mismatch than price itself, someone calling expecting a much smaller engagement than you actually offer. Tagging "lost - budget mismatch" separately from "lost - price" surfaces whether your marketing is attracting the wrong size of prospect in the first place, which is a positioning problem, not a pricing one, and the fix is different.

When tagging alone isn't enough

If you're spending real money across several ad channels and the actual business question is "which channel should I spend more on," outcome tags can't answer that, no matter how disciplined your tagging habit is, since the missing piece is attribution, not outcome. That's the specific point to add a call-tracking tool, not before. If your real question is closer to "is my team actually any good on the phone," outcome tags answer that cleanly and for free, and a call-tracking tool's extra attribution data wouldn't change the answer.

How I'd approach this

Once outcome tagging has been running for a month or two and the manual counting gets tedious, I'd build a small dashboard that pulls the tag data automatically and shows close rate and loss reasons by week without anyone having to count by hand. That's a genuinely useful step once the habit is proven and the manual counting becomes the bottleneck, and it's a much smaller build than a full call-tracking platform if attribution by marketing channel isn't actually what you need yet. I build this kind of lightweight reporting layer on top of whatever phone system a client already runs, which is usually far cheaper than it sounds once the underlying tagging habit already exists. Sending call details to Google Sheets or Slack without code is a lighter first step.