Squeeze In a Same-Day Emergency: Decision Tree

Why this matters

The phone rings with a customer who has no heat, a burst line, or a business that cannot open, and the schedule for today is already full. Say yes to everything and you blow up the day for five customers to save one. Say no reflexively and you lose a customer who genuinely needed you and will remember that you turned them away. Squeezing in an emergency well is a repeatable judgment call, not a gut reaction, and the dispatcher who does it consistently is worth more than the one with the fastest phone pickup.

Start here: is it actually an emergency

Before touching the board, separate a true emergency from an urgent-sounding request. Ask two or three fast questions:

• Is there an active safety hazard (gas smell, active flooding, no heat in freezing weather, a business fully shut down)?
• Is the situation getting worse by the hour, or is it stable but inconvenient?
• Has this been going on for days and only now became "an emergency" because the customer finally called?

If the answer points to a real, worsening, or hazardous situation, treat it as a genuine same-day priority and move to the next step. If it is uncomfortable but stable (a slow drip, one dead outlet, a unit that is loud but running), offer the next available slot and log the details so it does not get lost.

Check what today's schedule can actually absorb

Do not guess. Look at three things on the board before promising anything:

1. Genuine slack, meaning a buffer block or a job flexible enough to slide without a callback (see the related article on buffer time).
2. A tech physically near the emergency address, not just next on the list. A nearby tech finishing early absorbs an emergency with almost no schedule damage; a tech across town does not.
3. Whether anyone today is already running long. Do not add a squeeze-in on top of a day that is already slipping. Fix the existing slip first.

If there is real slack and a nearby tech, you can likely fit the emergency without touching anyone else's appointment. If there is no slack, move to the next step before you commit to anything out loud.

Decide what has to give

When there is no free slot, something on today's board has to move. Work through this order:

• First, look for a job today that the customer already said is flexible ("anytime this week is fine").
• Second, look for the lowest-priority job of the day, meaning routine maintenance or a non-urgent estimate, not another customer's own emergency.
• Third, if nothing gives easily, ask whether the emergency can go to the very end of today or the first slot tomorrow instead of displacing someone else right now. Not every emergency has to be seen in the next hour; "today" and "immediately" are not the same promise.

Never bump one customer's real emergency to fit a different customer's real emergency without a serious safety comparison first. If two genuine emergencies collide, see the related decision tree on which goes first.

Confirm before you promise

Once you have identified the slot and the tech, do two things before you hang up or send the confirmation:

• Tell the customer the real window, not an optimistic guess. "Between 2 and 4" beats "this afternoon" and prevents a second call in ninety minutes asking where the tech is.
• Tell the displaced customer immediately, before the original appointment time, not after the tech is already late. See the related article on communicating a delay before the customer calls you.

A squeeze-in that is not confirmed on both ends is not a solved problem, it is two problems waiting to happen at the same time.

Log it so the day stays honest

Add the emergency to the schedule as a real, timed job, not a note on a sticky pad. Record what displaced, why, and what you promised each customer. This does three things: it keeps the tech's day realistic instead of stacking invisible extra work, it gives you a paper trail if a customer disputes what was promised, and it shows you, over time, how often "emergency" squeeze-ins are eating your buffer, which tells you whether you need to build in more slack going forward.

Quick recap

1. Confirm it is a real, worsening, or hazardous situation, not just an urgent-sounding one.
2. Check for genuine slack and a nearby tech before promising anything.
3. If nothing is free, bump the lowest-priority or most-flexible job first, never another emergency.
4. Confirm the real window with both customers before you hang up.
5. Log the change on the schedule so tomorrow's dispatcher sees an honest picture.

References

• Trade-standard practice for field-service dispatch and triage
• See related: Building Buffer Time Into a Daily Schedule
• See related: Two Emergencies at Once: Which Goes First? (decision tree)
• See related: Communicating a Delay Before the Customer Calls You