• Replies 9 replies
  • Subscribers 2 subscribers
  • Views 12 views
  • Users 0 members are here
Options
Related

How do you handle customers who want a specific technician?

Paula Hendrix

Hi everyone — the team has been wrestling with this one lately and I'd love to hear how others are handling it.

We've got a growing number of customers (residential HVAC, mostly) who call in and specifically request "the guy who was here last time" or name a technician by name. Sometimes it's because they built rapport, sometimes it's a warranty callback and they want continuity, sometimes they just don't want to explain their setup to someone new.

The challenge: **our best technicians are also our busiest**, and accommodating these requests can throw off routing efficiency, create gaps in schedules, or delay other jobs. We've tried explaining that we can't guarantee specific techs, but that doesn't always land well with customers who feel like they're being passed around.

A few questions for the group:

  • Do you allow customer technician requests at all, or is it strictly "next available"?
  • When you do honor requests, how do you balance that against route efficiency?
  • Has anyone found a good way to set expectations upfront so this doesn't become a tension point?

The team wants to preserve relationships without letting customer preferences dictate our entire dispatch strategy. Curious what's working for others.

Parents

  • Paula, this is a classic operations tension and honestly I think a lot of teams handle it poorly by going all-or-nothing.

    Here's what we've landed on after some trial and error:

    We categorize requests into three buckets:

    • Technical continuity required — warranty callbacks, complex installs we documented specifically, anything where the original tech has institutional knowledge. We honor these, period.
    • Preference, not requirement — customer just liked someone. We'll note it, try to accommodate if it's within 48 hours and doesn't blow up the route, but we don't promise.
    • Specialized skill match — actually not a preference issue, just sounds like one. Customer thinks they want "Dave" but really they need someone certified on that equipment type.

    The key is training your dispatchers to diagnose which bucket fast. Most customers will accept "Dave's booked solid this week, but I'm sending Mike who actually did Dave's advanced training on this system" if you frame it right.

    Also: we added a "preferred technician" field in FieldPulse that's visible to dispatch but doesn't auto-assign. Lets us track the pattern without letting it drive the system.

Reply

  • Paula, this is a classic operations tension and honestly I think a lot of teams handle it poorly by going all-or-nothing.

    Here's what we've landed on after some trial and error:

    We categorize requests into three buckets:

    • Technical continuity required — warranty callbacks, complex installs we documented specifically, anything where the original tech has institutional knowledge. We honor these, period.
    • Preference, not requirement — customer just liked someone. We'll note it, try to accommodate if it's within 48 hours and doesn't blow up the route, but we don't promise.
    • Specialized skill match — actually not a preference issue, just sounds like one. Customer thinks they want "Dave" but really they need someone certified on that equipment type.

    The key is training your dispatchers to diagnose which bucket fast. Most customers will accept "Dave's booked solid this week, but I'm sending Mike who actually did Dave's advanced training on this system" if you frame it right.

    Also: we added a "preferred technician" field in FieldPulse that's visible to dispatch but doesn't auto-assign. Lets us track the pattern without letting it drive the system.

Children
No Data