Why Your Technicians Are Ghosting Your Own Job Leads (And How to Stop It)

The Pattern Nobody Talks About

You're a $1.5M HVAC business in Burnaby. Your phone rings. It's a lead—furnace repair, $180 job, new customer, 8 km away. Your lead goes to voicemail. Then it goes to a competitor.

This happens to you twice a week. You know it does.

You blame your technicians. "Why won't they answer?" But the real answer isn't laziness. It's information asymmetry. Your tech doesn't know what's on the other end of that call, so he doesn't pick it up.

He's been burned before: a "quick call" that turned into a 90-minute diagnostic. A customer who was angry before he even arrived. A job that looked profitable in the office but paid $40/hour once he factored in drive time. So he lets it ring.

What Techs Actually Need (In 10 Seconds)

Instead of hoping your technicians will answer, give them a reason to answer.

When your phone system is connected to your job data, an incoming call can trigger a screen popup showing:

• Job type (furnace repair, duct cleaning, emergency service)
• Customer address and drive time from his current location
• Estimated profit margin for this job type in this area
• Customer history (first-time customer, repeat, payment history, prior notes)
• Time window (same-day, next available, scheduled for Thursday)

Now your tech sees the call differently. "Furnace repair, 6 km away, $280 margin, new customer, same-day available." He picks it up.

Without that context, he's guessing. And guessing means no answer.

The Math on Ghosting

Let's say you get 40 inbound calls per month. Right now, your techs answer 18 of them. That's a 45% answer rate—typical for trades without lead context.

If your average job is $350 revenue and 60% margin, each missed call costs you about $210 in lost profit. Over a year, 40% of your leads ghosted = $18,480 in revenue you never even tried for.

A plumber in Port Moody realized this last fall. He was losing 15 calls a month to no-answer. Once his team could see job type and location before picking up, his answer rate jumped to 72%. By March, he'd recovered roughly $12K in annual revenue—just by letting his techs see the job before committing.

Why This Works Better Than Pressure

You can't shame or incentivize a technician into answering calls he doesn't trust. But you can remove the risk by giving him information.

When a tech knows:

• The job pays well for the distance
• The customer isn't a known problem
• He won't be stuck in traffic for an hour

He answers. Not because you told him to, but because it's a good call.

This is also why generic "answer your phone" policies fail. A tech who's been burned by unprofitable jobs will screen calls forever, no matter how many team talks you have.

The Setup (It's Simpler Than You Think)

You don't need a complete overhaul. You need:

1. Lead data connected to your phone system (job type, address, customer info) 2. A 10-second summary on screen when the call comes in 3. Margin visibility so techs see profit, not just a job

Most mid-sized trade businesses already have this data scattered across email, spreadsheets, and notes. The missing piece is connecting it to the moment your phone rings.

Once it's there, your techs stop ghosting because they're not afraid anymore.

The Ripple Effect

Higher answer rates also mean:

• Faster response time (which customers notice)
• Better first-call close rates (because your tech is prepared)
• Less time wasted on bad-fit jobs
• Fewer "I didn't know about that lead" conversations

It's not magic. It's just giving your team the information they need before they make a decision.

Your competitors who don't do this are still losing calls. You won't be.