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

How are you handling emergency or same-day jobs without disrupting the schedule?

Gwen Albright

We've been wrestling with this one for months and I want to hear how others are solving it.

We run 8 technicians across 3 zones. Our bread and butter is scheduled maintenance, but we get 3-5 emergency calls per week that need same-day response. The problem: every time we shove an emergency into the schedule, we break 2-3 other appointments. Customers get bumped. Technicians run late. Dispatchers spend their whole day replanning.

Here's what we've tried:

  • Keeping one "float" slot per day — but that's revenue we're not capturing, and emergencies don't conveniently arrive one per day
  • Overbooking the first appointment of each day assuming cancellations — works 60% of the time, creates chaos the other 40%
  • Asking technicians to absorb extra jobs — they're burning out, and I'm getting pushback on overtime

I'm curious what your actual operational rules look like. Do you have a written policy customers agree to? How do you decide which scheduled job gets bumped? And has anyone found a way to make this not feel like a daily crisis?

Gwen

  • We stopped pretending we could predict emergencies and started charging accordingly...

    Same-day callout fee of $150 before we even look at the job. Cuts volume by half, customers who truly need it pay for the disruption. Technicians get $50 of that as a bonus for taking the interrupt.

    Not pretty but it works.

  • Ray that's interesting! We've been scared to charge extra but maybe we should. Thanks so much for sharing that!

    We're trying something different — we actually have two "shadow" slots every day that aren't visible to customers until 8am. If no emergency comes in, we release them as "available today" to our waitlist. If we get an emergency, we use one of those slots and only bump someone if we're out of shadows.

    It helps but I feel like we're just hiding the problem? Like Gwen said the emergencies don't cooperate with our planning...

  • in reply to Deja Washington

    In my experience the shadow slot thing sounds clever but falls apart in July when everyone's AC dies at once.

    We triage by value of the scheduled job. Commercial maintenance contract? Never bump. First-time residential customer? Bumpable. Repeat customer with history? Negotiate.

    Written policy is useless. Customers don't read it and they'll argue anyway. What matters is your dispatcher having authority to make the call and your technicians knowing who's actually flexible.

  • We're testing a "technician swap" protocol. If emergency hits Zone A, we don't just look at Zone A techs — we check if a Zone B tech can finish early and hop over, or if Zone A has a job that can move to Zone B.

    Requires real-time location tracking and buy-in from the field. We're two months in. Results are mixed but trending positive.

    My team can't move forward on scaling until we solve this. Happy to share the protocol doc if anyone wants it.

  • honestly we just call people. like if jimmy's got 4 jobs and an emergency hits his zone we look at job 4 and call that customer. most people are fine moving to tomorrow if you explain

    the ones who aren't fine we offer a discount on next service

    not elegant but we're dispatch not magicians

  • We split our fleet into two pools:

    • Maintenance pool: 5 techs, tightly scheduled, no interruptions
    • Response pool: 3 techs, loose schedules with 60-90 min buffers, handle all same-day and overflow

    Response pool costs more per job but our maintenance efficiency is up 23% since we stopped breaking those schedules.

    Requires right-sizing the pools — we adjust monthly based on emergency volume trends.

  • in reply to Sylvia Chen

    Sylvia this is exactly the kind of structural thinking I needed. Two pools never occurred to us — we're treating all techs as interchangeable.

    Do you track different KPIs for the response pool? I'm wondering how you measure "success" when their day is inherently unpredictable.

  • in reply to Sylvia Chen

    Yes — response pool is measured on resolution rate (emergency closed same-day) and customer satisfaction specifically, not utilization. They're expected to have downtime.

    Maintenance pool: utilization, on-time arrival, jobs per day.

    Different scorecards, different comp structures. Took a year to get right.

  • in reply to Sylvia Chen

    Another way to think about it: the two-pool model essentially creates a service level agreement with your own operation. You're protecting predictable revenue by explicitly funding response capacity.

    We've taken a similar approach but with floating technicians who rotate into the response role weekly — prevents burnout and cross-trains the team.

    Worth noting: we found response pool techs need different soft skills. They're walking into crises, not following a checklist. Hiring profile changed significantly.

  • so basically what im hearing is everyone is just making it up as they go lol

    seriously though ive been on the tech side of this and the thing that actually helps is when dispatch tells us why the schedule changed not just that it changed. like "hey connor job 3 had a baby with a medical device so you're taking their slot and they'll get you tomorrow" — makes me feel like im helping not just absorbing someone else's problem

    that and snacks in the van. cant fix the schedule but can fix morale