Stuck on Hold Forever: The Dark Design Behind Bots That Never Let You Win

You know the feeling. You've got a billing error, a package that vanished, a subscription you can't cancel. You open the app or dial the number, and a cheerful synthetic voice greets you like an old friend. We're so happy you reached out. Let's get this sorted together. And then — nothing gets sorted. Not really. You're just... in there. Cycling. Waiting. Pressing 1 again.

This isn't an accident. It's architecture.

The Waiting Room That Was Built to Break You

Customer service automation has been around long enough that most of us have stopped questioning it. We assume the hold music is just filler, that the progress bar means something, that the bot is genuinely trying to route us somewhere useful. But a growing number of former UX designers and product managers — people who actually built these systems — are starting to speak up about what was really happening behind the interface.

"We had a term for it internally," says one former designer who worked on support flows for a major US telecom carrier and asked to remain anonymous. "We called it 'friction stacking.' The goal wasn't to solve problems faster. It was to introduce enough small delays and dead ends that a certain percentage of users would just drop off before reaching a live agent."

That percentage, it turns out, is a KPI. A metric. Something optimized for.

Companies track what's called the deflection rate — the number of users who start a support interaction and never reach a human. A high deflection rate is considered a win. It means the bot did its job. The fact that the user's problem may still be completely unresolved is, in the language of the industry, someone else's problem.

Fake Progress and the Illusion of Movement

One of the more insidious design choices in modern support UX is the progress indicator — that little animation or status bar that suggests your issue is being processed, your information is being retrieved, your case is being escalated. Except often it isn't. The animation is a loop. A placeholder. A psychological pacifier.

Research in behavioral psychology has long established that humans tolerate waiting significantly better when they believe something is happening. Airlines figured this out decades ago. So did fast food chains. The perceived wait feels shorter when there's visible activity, even if that activity is entirely cosmetic.

Support bots weaponize this. The spinning icon, the "please hold while we look into this" message that repeats every 45 seconds, the "you're number 12 in the queue" counter that jumps from 12 to 9 and then somehow back to 11 — these aren't glitches. They are, in many cases, intentional design decisions meant to sustain your engagement just long enough that you feel too invested to leave, but never close enough to resolution to feel satisfied.

"We A/B tested hold animations constantly," another former product designer told us. She spent several years building support systems for a subscription software company. "Longer animations with more visual complexity kept users in the queue longer. It sounds absurd, but a fancier loading screen genuinely reduced drop-off. We were basically making people wait more patiently for nothing."

The Menu Loop as a Maze

If you've ever found yourself pressing 4 for billing, then 2 for account issues, then 1 for something that sounds vaguely relevant, only to be returned to the main menu with no explanation — you've been through a loop. These aren't design failures. They're design features.

Circular menu systems serve a dual purpose. First, they create the impression of a comprehensive, helpful system. There are so many options. Surely your issue is in here somewhere. Second, they quietly filter out users who don't have the time, energy, or cognitive bandwidth to keep pushing. The people who abandon the call aren't just frustrated — they're, from the company's perspective, successfully managed.

It's passive gatekeeping. Nobody's being rude to you. Nobody's telling you no. You're simply being worn down until you make the choice to leave on your own. The company's hands stay clean.

Hold Music as Psychological Pressure

Then there's the audio environment. Hold music is one of the oldest tricks in the book, but modern implementations have gotten considerably more sophisticated in their awfulness. Some systems use music specifically selected to be neutral enough to prevent you from fully disengaging — you can't quite zone out because it keeps changing, keeps shifting — while simultaneously being irritating enough that your stress levels creep upward the longer you stay on.

Other systems deploy what researchers call asymmetric silence — brief pauses in the hold audio that trick your nervous system into thinking someone is about to pick up. You perk up. You pay attention. Nobody comes. The music resumes. Your cortisol spikes a little more.

Combined with the occasional scripted message reminding you of the company's commitment to your satisfaction, these audio environments function less like waiting rooms and more like low-grade sensory endurance tests.

Who Actually Benefits Here

The obvious answer is the company. Fewer escalations to live agents means lower labor costs. Fewer resolved complaints means fewer refunds, fewer policy exceptions, fewer cases that require a human to make a judgment call. The math is pretty simple.

But there's a less obvious beneficiary: the platform itself. The longer you stay in a support loop, the more data gets generated about your behavior, your patience threshold, your specific pain points. That data informs future iterations of the same system. The bot gets smarter at keeping you in limbo because it's been trained on thousands of people just like you who also couldn't find the exit.

You are, in a very real sense, teaching the machine how to trap the next person better.

The Static Between You and a Solution

What's genuinely strange about all of this — and what makes it feel weirdly at home in the kind of territory Creabje tends to wander into — is how invisible the design is. You never see the friction stacking. You never see the A/B test that determined your particular flavor of misery. You just experience it as a vague, shapeless frustration, a feeling that the system is somehow against you but you can't point to anything specific.

That's the point. Intentional design that feels like dysfunction. A cage that looks like a customer service portal.

Some consumer advocates are starting to push back. There are renewed calls in several US states for legislation requiring companies to offer a direct path to a live human within a certain number of steps — no more infinite loops, no more fake escalations. Whether those efforts gain traction against the lobbying power of the industries that profit from the limbo is another question entirely.

In the meantime, the hold music plays on. The progress bar spins. And somewhere in a product roadmap you'll never see, someone is optimizing the exact length of the pause before the bot says I'm sorry, I didn't catch that. Could you repeat your request?

Again.