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

  • Another way to think about this is through the lens of customer lifetime value rather than individual transaction efficiency.

    We've found that honoring a technician request for a customer in their second or third service year has measurable retention impact — something like 12% higher renewal on service agreements when we accommodate. The cost of a slightly suboptimal route for one job is often outweighed by the recurring revenue protected.

    That said, we also use this as a relationship management tool. When we can accommodate, we make sure the customer knows: "Normally our techs rotate, but since this is a callback on our work, I'm keeping you with Sarah." It reinforces that this is a favor, not a guarantee.

    For newer customers or one-off jobs, we stick to the rotation and frame it as "getting to know our team."

Reply

  • Another way to think about this is through the lens of customer lifetime value rather than individual transaction efficiency.

    We've found that honoring a technician request for a customer in their second or third service year has measurable retention impact — something like 12% higher renewal on service agreements when we accommodate. The cost of a slightly suboptimal route for one job is often outweighed by the recurring revenue protected.

    That said, we also use this as a relationship management tool. When we can accommodate, we make sure the customer knows: "Normally our techs rotate, but since this is a callback on our work, I'm keeping you with Sarah." It reinforces that this is a favor, not a guarantee.

    For newer customers or one-off jobs, we stick to the rotation and frame it as "getting to know our team."

Children
No Data