Triage the backlog by consequence
Not every waiting job is equal. Sort what is outstanding into:
Losing money now. Customers waiting on a quote, jobs booked but unscheduled, anyone who has been promised a call today.
Losing money soon. Enquiries from the last few days with no response. These go cold fast and are the most recoverable.
Can wait. Routine maintenance, non-urgent follow-ups, anything with a flexible date.
Handle the second category first. A three-day-old enquiry can still be won; a two-week-old one usually cannot.
Communicate before customers chase
The cheapest thing you can do this week is tell people where they stand. A customer told "we are running behind, we can be with you Thursday" is far less likely to go elsewhere than one who hears nothing.
Be specific and be honest. A date you will actually hit beats an optimistic one you will miss, and missing a second promise loses the customer entirely.
Send it by text where you can. It is faster than calling and people read it.
Take work off the dispatcher today
Immediate relief comes from removing tasks, not adding hours:
- Move incoming calls to someone else, even imperfectly, for the busiest two hours
- Have technicians handle their own end-of-day paperwork
- Divert supplier and sales calls elsewhere
- Postpone anything not directly connected to getting jobs done this week
A dispatcher who is not being interrupted every four minutes recovers a surprising amount of capacity.
Stop taking on what you cannot deliver
This is counterintuitive and it is usually right. If the schedule is three weeks out, saying so at the point of enquiry is better than booking someone into a slot you will move twice.
Be straight with new callers about the current lead time. Some will wait, some will go elsewhere, and both outcomes are better than an angry customer who was promised Tuesday.
Use overflow capacity
Short-term options that can be arranged in days:
- A trusted competitor or subcontractor for overflow, on agreed terms
- Overtime for a technician who wants it
- An answering service to hold the phone line while dispatch works the schedule
- Bringing forward a planned hire
Subcontracting overflow feels like giving away work. Losing the customer permanently is worse.
Protect the follow-up
The quotes already issued are the cheapest revenue available, and they are the first thing dropped when dispatch is behind. If nobody can follow them up, give that specific task to someone else this week — an owner, an office manager, anyone. It does not require dispatch knowledge.
Then write down what caused it
When the immediate pressure passes, record what happened: what the volume was, where the day broke down, which jobs overran. Most dispatch crises repeat seasonally, and Houston's summer cooling season and post-storm periods are predictable. A written record turns next year's crisis into a plan.
Frequently asked questions
What should I handle first?
Enquiries from the last few days with no response. They go cold fast and are the most recoverable — a three-day-old enquiry can still be won, a two-week-old one usually cannot.
What is the cheapest immediate action?
Telling customers where they stand before they chase. A customer told you are running behind and can attend Thursday is far less likely to leave than one who hears nothing. Text is faster than calling.
How do I relieve the dispatcher today?
Remove tasks rather than adding hours — move calls to someone else for the busiest two hours, have technicians do their own paperwork, divert supplier calls, and postpone anything not about this week's jobs.
Should I keep taking bookings?
Be straight about the current lead time at the point of enquiry. Some callers will wait and some will go elsewhere — both are better than booking someone into a slot you will move twice.
What gets dropped that shouldn't?
Following up quotes already issued, which is the cheapest revenue available. Give that specific task to someone outside dispatch this week; it does not require dispatch knowledge.