Communicating Realistic Timelines When Everyone Wants to Be First
Why this matters
During a surge, every customer believes their situation is the most urgent one on your board, and honestly, many of them genuinely are urgent, just not more urgent than the others making the exact same claim. The natural response under pressure is to tell each caller what they want to hear ("we'll be there today") to get them off the phone and calm them down. That response is the single most damaging habit a shop can develop during a disaster, because it trades a hard conversation now for a much worse one later, when the truck never shows.
Why vague optimism backfires worse than honest bad news
A customer told an honest, unwelcome timeline ("realistically three to five days, here's why") can plan around it, arrange alternatives, and, importantly, trusts you more once you actually deliver on that window. A customer told a hopeful timeline you cannot keep ("today, for sure") experiences something closer to a broken promise than a delay, because they made decisions, cancelled plans, or stopped calling other options based on your word. The second customer is angrier, even though the first one waited longer in actual hours.
The three-part structure of an honest timeline conversation
- State the real constraint, plainly. "We have a large number of calls right now from the storm, and we're triaging by severity." This is not an excuse, it is context that helps the customer understand the wait is not about them personally.
- Give an honest range, not a hopeful point estimate. "Realistically two to four days" beats "probably tomorrow" every time, because the range survives contact with reality and the point estimate usually does not.
- Name what would move them up or down the list. "If it gets worse, or if you're without water entirely, call back and we'll reassess" gives the customer a clear, fair mechanism instead of a sense that the list is arbitrary or that squeaky-wheel calling is the only lever they have.
Handling the customer who pushes back
Some customers will not accept the honest window and will push, sometimes hard, for a same-day commitment. Hold the line without getting defensive.
- Acknowledge the frustration directly: "I hear you, this is a real inconvenience and I wish I had better news."
- Repeat the honest constraint, not a new promise: do not cave into a same-day commitment just to end an uncomfortable call. A commitment you make to escape pressure is a commitment you often cannot keep, and it damages trust worse than holding the original honest line.
- Offer the actual mechanism for reprioritization if their situation has a genuine safety dimension you had not previously known about: "If there's an active safety concern I don't know about yet, tell me now and I'll reassess where you sit on the list."
Train whoever answers the phone to use the same structure
Inconsistent messaging across your team creates the worst version of this problem: two customers compare notes and one was told "today" while the other, in a nearly identical situation, was told "later this week." Give everyone answering calls the same honest framework and the same severity criteria, so the message is consistent no matter who picks up. See related: The Storm or Emergency Demand Spike Decision Tree.
Update proactively, not just on request
An honest timeline given once and never revisited still erodes trust if circumstances change and nobody tells the customer. If a window is going to slip, or the priority list shifts and someone moves later than originally indicated, reach out before they call to ask. Silence during a surge reads as abandonment even when nothing has actually gone wrong operationally.
The mental model to keep
The goal of a timeline conversation during a surge is not to make the customer feel better in the next thirty seconds, it is to give them information they can actually plan around and trust. A hard truth delivered calmly and kept builds more loyalty over the length of a surge than an easy comfort delivered now and broken later.
References
- Trade-standard practice for disaster-period customer communication and expectation-setting
- See related: The Storm or Emergency Demand Spike Decision Tree
- See related: A Regional Disaster Hits While Normal Jobs Are Still Scheduled: Decision Tree