The Walk-Up & Drive-By Culture

The desk at Bellweather Logistics logged thirty tickets a day and did, by its own later estimate, about fifty. The other twenty arrived by hallway, by a tap on the shoulder, or by a direct message to whichever technician the user liked best. Some came from a man from dispatch who had worked out that if he stood near the desk looking lost, someone would ask. None of the twenty were in the queue. None of them were in the reports. The desk was told, in the annual review, that its volume was flat and its backlog was rising. It could not explain why, because the why was standing near the desk looking lost.

This series is about the twenty. It covers why walk-ups happen and what they cost: interruption, unlogged work and a fairness problem the desk cannot see. It covers the hallway request handled well, which means logging it yourself in twenty seconds rather than sending the person away. It covers direct messages and chat as a support channel, and deciding whether they are one. Then comes designing the walk-up window instead of suffering it, with a person, a sign and a laptop that logs. It covers redirecting without alienating people, including the manager and the friend. And it covers measuring the shift to logged work, so the thirty becomes fifty on paper and the report finally tells the truth.

Articles in This Series

• Why Walk-Ups Happen and What They Cost the Desk
  The human reasons, the cost to the desk (interruption, unlogged work, the invisible backlog, fairness), a one-week census as a worked example, and the walk-up census.
• The Hallway Request, Handled Well in Twenty Seconds
  The twenty-second reply, logging it yourself on the spot, never send-me-a-ticket as a brush-off, the one you fix on the spot and still log, and the hallway script.
• Direct Messages and Chat as a Support Channel
  The direct message that becomes a ticket, the team channel nobody owns, deciding whether chat is a channel at all, the auto-reply, the technician's personal messages, and the redirect.
• Designing the Walk-Up Window Instead of Suffering It
  Hours, the queue-duty person who staffs it, the sign, and the laptop at the window that logs every visit. Covers what the window is for and what it sends to the queue, and the window standard.
• Redirecting People to the Queue Without Alienating Them
  Tone, the why explained once and kindly, the manager who walks up, and the executive. Covers the user who tried the portal and it failed, the colleague who is a friend, and the reply set.
• Measuring the Shift From the Hallway to Logged Work
  Walk-up share over time, the unlogged estimate, the satisfaction difference, the channel report, declaring the culture changed, and the channel shift scorecard.

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.