It was a slow Tuesday afternoon when our helpdesk received a ticket unlike any other. The subject line simply read: “Mouse too quiet.” Intrigued, I opened the request to find the user’s description: “My mouse isn’t making enough noise when I click. How am I supposed to know if it’s working?”
At first, I thought it was a joke. A mouse making noise? Surely they meant a technical issue, like it wasn’t responding. But no, the user was genuinely concerned their quiet, modern optical mouse was broken because it lacked the classic clickety-clack sound of old mechanical mice. Our user hadn’t just grown fond of clicks—they had grown *dependent* on the audible feedback to feel like the mouse was doing its job.
When I called to clarify, the user explained that they liked the sound—it reassured them. They even shared how frustration set in when colleagues tried newer silent mice in the office. “You don’t know how peaceful it feels when you can actually *hear* each click,” they said.
After a moment of considering whether to suggest they invest in a vintage gaming mouse or learn Morse code, I calmly advised them that the quiet clicking was normal for modern mice. But, as a compromise, I recommended enabling the “Click sounds” accessibility setting on their computer, which made a small audio cue through the speakers every time they clicked.
The user was delighted. Problem solved, and office peace maintained.
To this day, I sometimes wonder if that was the first support call where the “hardware quality” complaint was really about the hardware being *too silent* rather than broken. If the “click” is dead, long live the click — but sometimes, it just needs to be heard in a different way.