By the time Lucas (name changed) saw the first little audio bubble pop up, he already knew how the next hour of his life would go.

He’s a 35‑year‑old IT manager at a small, family‑run sales company. Recently, his team had switched from an ancient, clunky system to a shiny new platform—modern, intuitive, efficient. On paper, it was a dream.

In reality, the dream came with a catch: support that only seemed to speak in voice messages.

Every time Lucas opened the in‑app support chat, he got the same thing—audio clips. Not quick ones, either. Long, rambling instructions he had to replay again and again just to catch a simple detail. For someone who relies on text to scan, search, and solve problems, it was a nightmare.

He asked them to stop. More than once. He even told them he was hearing impaired, hoping that would be the end of it.

They ignored him.

Then one day, things actually broke. The company’s point‑of‑sale systems stopped talking to the local server. Everything was online, but nothing was communicating. It was beyond what he could fix alone, so he did what he had to do: contacted support.

The first reply?

Another voice message.

That’s when Lucas decided he’d had enough.

When support asked for the remote access ID, he didn’t type it. He held down the microphone button and sent it back as an audio clip.

They wanted the password next. He sent that as audio too.

Suddenly, something changed.

The voice messages stopped. The chat switched to text.

Now they were asking for screenshots. Later, they needed the admin credentials—a long, ugly password full of numbers, uppercase and lowercase letters. Lucas sent that by voice as well, carefully making it just as annoying for them as their messages had been for him.

From that moment on, everything stayed in text. Even the follow‑up the next day.

Watching from the sidelines, people loved the quiet twist of revenge. One person joked that when support asked for screenshots, Lucas had missed a chance to send a ten‑minute audio description of every pixel on his screen. Another imagined printing the screenshot, faxing it, and somehow turning the fax noise into an audio file.

Lucas admitted he’d thought about dragging it out, maybe starting a long “audio discussion,” but he needed the systems back up first.

Still, his point had been made.

It turned out support knew exactly how annoying voice messages were. They just didn’t care—until, for once, they were the ones who had to listen.