Why Your Technicians Are Turning Down Jobs (And It's Probably Your Fault)

The Pattern Nobody Talks About

You book a job. You call your top technician. He says, "I'll take it," but then texts back 20 minutes later: "Actually, can you give that one to someone else? I've got too much on."

He doesn't have too much on. You know it. He knows it.

What he actually means is: "I don't have enough information to feel good about this job."

This happens in plumbing shops in Burnaby, HVAC teams in Surrey, appliance repair businesses across the Lower Mainland—and it costs you money every single time. Your technician isn't lazy. He's protecting his day. And the reason he's protecting it is because you haven't given him what he needs to succeed.

What Technicians Are Actually Looking For

When a job comes in, your tech's brain is running a rapid-fire checklist:

• Do I know where this is? (Bad address = wasted drive time.)
• Have we been here before? (Repeat customers = faster diagnosis.)
• What am I walking into? (No description = could be 30 minutes or 3 hours.)
• Do I have the parts? (If it's an HVAC compressor replacement, I need to know the unit model now, not on-site.)
• What's the customer expecting to pay? (If the estimate is vague, I'm walking into conflict.)

If you hand him a job sheet with three of those blanks, he's going to decline. Not because he's difficult—because he knows from experience that incomplete jobs turn into overtime, customer complaints, and re-visits.

A $1.2M HVAC contractor in Burnaby we've worked with realized this after losing three jobs in one week to his most reliable technician. His dispatcher was sending out jobs with just a name, number, and symptom. No service history. No unit specs. No prior estimate data. His tech, who'd been with him for seven years, started saying no.

What Changes Everything

The fix isn't more money or a pep talk. It's job packaging—one clear, complete summary waiting for your technician before he ever leaves the shop.

Here's what that looks like:

A plumber gets a call about a backed-up toilet on Tuesday morning. Instead of a sticky note, he gets a one-page summary:

• Customer name, address, phone, notes ("This is Mrs. Chen, third visit in 18 months—previous issues were tree roots in main line.")
• Service history (Last visit: June 2023, $450 snake and camera.)
• Photo from last visit (showing the crack in the main line).
• Estimated time window (30–60 minutes if it's roots again; 90 minutes if it's a new blockage).
• Estimated parts cost range ($0 if it's a simple snake; $1,200–$2,000 if the main line needs repair).

That tech now knows: this is a repeat problem, I've seen it before, I know what to expect, I can set customer expectations correctly, and I can pack the right tools. He accepts the job. He arrives confident. He closes it faster.

How AI Fits In

You can't manually build that summary for every job. You don't have time. But AI can.

AI can:

• Pull service history and past photos from your system in seconds.
• Cross-reference the customer's address with your route data to estimate drive time.
• Compare the current problem description to similar past jobs and suggest typical time and parts costs.
• Flag red flags (new area, no history, high complexity) so you can prepare.

The result: your technicians get context, not just a job number. They feel prepared. They accept more work. They execute faster. Your utilization goes up.

The Real Cost of Job Rejection

If your team is turning down 2–3 jobs per week (which is typical for a $500K–$1.5M business), that's 100–150 jobs per year. At an average job value of $400–$800, you're leaving $40K–$120K on the table annually.

Most of that isn't because the work is genuinely too much. It's because your technicians don't feel set up to win.

What to Do Monday Morning

Start with your top three technicians. For the next week, before you dispatch a job to them, write down what information they actually ask for. You'll see the pattern immediately.

Then build a one-page job summary template that includes those items. Use your scheduling and CRM data—you already have most of this. If you're not capturing service history or past photos, that's your next priority.

Technicians who feel prepared don't decline work. They execute it.