How do you handle customers who want a specific technician?

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
  • Love this thread — so many practical perspectives! This is exactly the kind of operational nuance we love seeing the community work through together.

    Quick note from our side: we're actually exploring some features in this space for 2025, including better visibility into technician history with specific customers and smarter routing that can optionally prioritize continuity without forcing it. Nothing committed yet, but the use cases you're describing are directly informing those conversations.

    In the meantime, the "preferred technician" field Gwen mentioned is probably your best bet for tracking — and if you haven't seen it, this post on rolling out to larger teams has some dispatcher training tips that might help with the expectation-setting piece.

    Keep the stories coming — real examples help us build better.

Reply
  • Love this thread — so many practical perspectives! This is exactly the kind of operational nuance we love seeing the community work through together.

    Quick note from our side: we're actually exploring some features in this space for 2025, including better visibility into technician history with specific customers and smarter routing that can optionally prioritize continuity without forcing it. Nothing committed yet, but the use cases you're describing are directly informing those conversations.

    In the meantime, the "preferred technician" field Gwen mentioned is probably your best bet for tracking — and if you haven't seen it, this post on rolling out to larger teams has some dispatcher training tips that might help with the expectation-setting piece.

    Keep the stories coming — real examples help us build better.

Children
No Data