• Replies 9 replies
  • Subscribers 2 subscribers
  • Views 1 view
  • 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

  • Thanks everyone — genuinely helpful range of perspectives here.

    Brandon, I hear you on the math. We're at 22 techs and I can feel us approaching that inflection point where flexibility becomes chaos.

    Nadia, the CLV framing is useful — I'm going to pull some data on whether our "request honored" customers actually do renew at higher rates. If they do, that justifies building some inefficiency into the model.

    Gwen, the three-bucket diagnostic is going straight into our dispatcher training. That's exactly the kind of operational clarity we needed.

    And Carla — appreciate you jumping in. Would love to see continuity scoring or "last tech served" surfaced more prominently in routing if that ends up on the roadmap.

    Will update the team and report back if we land on something that sticks.

Reply

  • Thanks everyone — genuinely helpful range of perspectives here.

    Brandon, I hear you on the math. We're at 22 techs and I can feel us approaching that inflection point where flexibility becomes chaos.

    Nadia, the CLV framing is useful — I'm going to pull some data on whether our "request honored" customers actually do renew at higher rates. If they do, that justifies building some inefficiency into the model.

    Gwen, the three-bucket diagnostic is going straight into our dispatcher training. That's exactly the kind of operational clarity we needed.

    And Carla — appreciate you jumping in. Would love to see continuity scoring or "last tech served" surfaced more prominently in routing if that ends up on the roadmap.

    Will update the team and report back if we land on something that sticks.

Children
No Data