• Replies 10 replies
  • Subscribers 2 subscribers
  • Views 11 views
  • Users 0 members are here
Options
Related

How do you handle customer complaints about appointment windows that get shifted?

Nadia Petrov
We've been seeing an uptick in customer complaints when appointment windows need to shift—whether due to emergency calls, technician illness, or jobs running long. While we always try to communicate proactively, the reality of field service means some disruption is unavoidable. I am interested in hearing how other teams approach this from a customer relationship perspective. Specifically:
  • What communication methods have you found most effective for delivering schedule changes?
  • Do you offer any form of compensation or goodwill gesture when windows shift significantly?
  • How do you distinguish between minor adjustments customers tolerate versus changes that genuinely damage trust?
From an operational standpoint, we are also weighing whether to build buffer time into our scheduling to reduce the frequency of shifts, or to maintain tighter schedules and accept that some rescheduling will occur. Another way to think about this trade-off is whether predictability or throughput matters more to your specific customer base. I would appreciate hearing what has worked—and what has backfired—in your experience.
  • We stopped giving customers "windows" entirely and started giving them committed times with escalation triggers. Here's how we structure it:
    • We quote a 2-hour arrival window only if the job before theirs is a standard service call
    • If the prior job is complex or diagnostic, we automatically build in a 30-minute buffer and communicate that upfront
    • If we're running 15+ minutes late, the system auto-texts with a revised ETA and the dispatcher calls within 5 minutes
    The key insight: customers don't mind waiting if they trust your timeline. What destroys trust is silence and uncertainty. We saw complaint volume drop 40% when we got aggressive about proactive communication. Pro tip: Train your CSRs to say "I'm calling because we respect your time" rather than "I'm calling because we're running late." Same information, completely different emotional framing.
  • Gwen's approach sounds nice in theory... we've tried similar and customers still complain. The reality is some customers want to complain. Our rule: if we shift by more than an hour, we offer $25 off or priority scheduling next time. About 60% take the discount, 30% just want to vent and appreciate being heard, 10% escalate no matter what you do. The ones who escalate? Document everything and protect your team. Not every customer is worth retaining. Worth noting: we stopped apologizing for shifts caused by emergency calls (gas leaks, safety issues). Customers actually respect "we're delayed because we're handling an emergency" more than vague "operational delays."
  • in reply to Ray DeLuca
    This is so helpful! I'm still somewhat new to dispatch coordination and I've definitely been on the receiving end of some very frustrated customer calls when schedules shift. We currently use the automatic SMS notifications that come through FieldPulse, but I'm wondering if anyone has found success with personalized phone calls for certain types of changes? I feel like I end up spending so much time on the phone some days, but then other times I'll send a text and get an immediate angry callback anyway. Is there a threshold where you automatically escalate to voice contact? And has anyone tried using the customer portal to let customers see real-time updates themselves? We haven't turned that on yet but I'm curious if it reduces the "where is my technician" calls! Really appreciate any insights—this thread is exactly what I needed to see today!
  • in reply to Ray DeLuca
    Ray, I really appreciate you sharing that perspective. The team has been wrestling with whether we're apologizing too much and undermining our own credibility. Can I ask how you distinguish between emergencies you disclose versus ones you keep private? We've had situations where mentioning "emergency call" led customers to ask for details, which gets uncomfortable fast.
  • in reply to Paula Hendrix
    Simple rule: if it's a safety issue (gas, electrical hazard, water damage) we say "emergency safety call." If it's a VIP customer throwing a fit? That's "operational necessity." Customers don't need to know another customer yelled louder than they did.
  • in reply to Brianna Simmons
    Hi Brianna, love that you're thinking about the customer experience holistically! We want to make sure you're set up for success here. A few thoughts from what we've seen across our customer base:
    • Phone calls for shifts over 2 hours or same-day changes tend to land better than SMS alone
    • The customer portal beta (announced here) is showing promise for reducing status calls—customers who can self-serve often feel more in control
    If you'd like, I can connect you with a couple of customers who've implemented proactive communication workflows. Sometimes it helps to hear directly from peers who've been in those exact customer conversations. Feel free to DM me and we'll get something scheduled!
  • in reply to Ray DeLuca
    Buffer time isn't the answer. We tried it. Customers book further out, then complain when you can't move them up. You're always wrong. Tighter scheduling with honest communication wins. Most of our reschedules happen in the first 2 hours of the day when we know where we stand. After that, we commit and eat the cost of running late rather than shifting. Customer retention metric that actually matters: repeat bookings, not complaint volume. Some complainers book again. Some silent ones don't return. Track the right thing.
  • in reply to Ray DeLuca
    honest q how do you handle it when the tech is the one running late not the schedule? like they took a long lunch or got stuck talking to a customer we had a guy consistently 30-45 min behind and his customers got the auto-text like it was our fault as dispatch when really...
  • in reply to Teresa Lund
    Teresa, that's a management issue, not a scheduling issue. Document the pattern, have the direct conversation, and if it doesn't improve, that's a performance conversation. One thing that helped us: we started showing techs their own delay analytics in FieldPulse. When they saw their "average delay to next job" compared to team average, behavior changed fast. Some people need data, some need coaching, some need to find another job. Don't let one person's habits poison your customer relationships.
  • in reply to Ray DeLuca
    Field perspective: customers are way cooler about delays when the tech owns it personally. I call ahead, explain what's happening (even if it's "last job was more complex than expected"), and give them a real choice—wait for me or reschedule. Pro tip: If they're waiting, I text when I'm 15 min out and again when I arrive. Eliminates the "when are they actually showing up" anxiety that drives most complaints. The companies with the happiest customers I've worked for all trained their techs on communication, not just technical skills. Worth investing in.