Managing Expectations
The ticket was logged on Monday at 09:12. The technician read it at 09:20 and knew it would take a part that arrives on Thursday. They started on the three tickets ahead of it. On Wednesday at 14:00 the requester phoned, angry, to ask whether anyone had seen it. Nobody had told them anything. From their side of the desk the ticket had fallen into a hole on Monday and stayed there for two days. The work was fine. The silence was the failure. Most of the anger a desk receives is not about how long things take. It is about not knowing how long things will take, and finding out by asking.
This series is about ending the silence. It covers what users actually want to know, which is three questions and none of them is "is it fixed yet". It covers honest ETAs you can keep, in ranges, from the queue rather than from hope. It covers status updates that prevent the angry follow-up, including the update that says there is no news. Then comes the fix that is weeks away and how to keep faith for a month. It covers resetting expectations when the plan changes, early and without grovelling. And it covers setting expectations at the desk level. That way, the acknowledgment and the portal answer the questions before they are asked. A promise kept is good. A promise explained, and then kept, is what builds trust.
Articles in This Series
- What Users Actually Want to Know About Their Ticket
The three questions behind every ticket: did you get it, who has it, when will I hear. Covers silence as the enemy, the acknowledgment that answers all three, and the expectation card. - Honest ETAs: Promising a Time You Can Keep
Estimating from the queue not from hope, ranges rather than points, padding honestly, 'I will know by', re-estimating early, and the ETA phrasing table. - Status Updates That Prevent the Angry Follow-Up
The interval, the no-news update, what one update contains, and the status update message to copy. - When the Fix Is Weeks Away: Keeping Faith Over a Long Wait
Vendor dependencies, procurement and projects behind the ticket; the workaround in the meantime, the long-wait rhythm, keeping faith over a month, and the long-wait message. - Resetting Expectations When the Plan Changes
The ETA slips, the scope changes, the fix did not work; telling them early, the apology that is not grovelling, the new promise, and the reset message. - Setting Expectations at the Desk Level Before Anyone Asks
Published response times in plain words, the acknowledgment text, the portal and out-of-hours text, the service levels explained for users, and the 'what to expect' page.
Explore More Topics
This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.