It is the quietest horror of the modern service economy. We have spent the last three decades perfecting the art of “reach.” We can reach anyone, anywhere, at any time. But in the process of optimizing how we are reached, we have systematically dismantled the reason we wanted to be reached in the first place: to be known.

We have traded the direct line for the load-balancer, and we are all poorer for the transaction.

Earlier today, I hung up on my boss. It wasn’t an act of rebellion or a cinematic moment of professional suicide. It was a finger-slip. I was toggling between three different “priority” threads in a communication suite that treats every interaction like a glowing bead on a string.

My boss was just another bead. When I tried to slide his window to the foreground, my muscle memory-calibrated by a week of closing out low-value tickets-hit the “end call” icon instead of the “expand” one. There was no weight to the click. There was no friction. In a system designed for interchangeable parts, even the person who signs my paycheck is just a pixelated interruption.

The Erlang Ghost

In 1917, a Danish mathematician named Agner Krarup Erlang was obsessed with the Copenhagen Telephone Company. He wasn’t interested in what people were saying; he was interested in the physical reality of the wait. He developed the Erlang C formula, a piece of mathematical architecture that still governs every call center, every chat queue, and every digital waiting room you have ever suffered through.

Erlang’s math is beautiful if you are a machine. It calculates the probability that a customer will have to wait, based on the number of servers and the intensity of the traffic. It is the foundation of “load balancing.” The goal of an Erlang-based system is equilibrium. You don’t want one person sitting idle while another is overwhelmed. You want the work spread across the field like butter on toast.

But Erlang didn’t account for the “thread.” In his world, a telephone call was a discrete event with a beginning and an end. He couldn’t have imagined a world where a customer interaction spans four weeks, six channels, and 12 different time zones.

When we apply 1917 math to 2024 relationships, we create a ghost in the machine. We create a system where “Efficiency” demands that the customer be handed to the next available warm body, regardless of whether that body knows that the customer’s mother just died or that their previous three shipments were crushed by the same UPS driver in Des Moines.

The Taxonomy of the Queue

I remember a time, perhaps 15 years ago, when “Support” meant calling a guy named Greg. You had Greg’s extension. Greg knew your setup. He knew that your server rack was held together with zip ties and prayers. When you called, you didn’t start with your account number; you started with, “Hey Greg, it’s doing that thing again.”

Then came the “Scale” phase. The consultants arrived with their charts and their Erlang C calculators. They pointed out that if Greg went on vacation, your account stagnated. They argued that “Tribal Knowledge”-the stuff inside Greg’s head-was a liability. It was a “single point of failure.”

To fix it, they moved everything into a centralized routing system. They digitized Greg’s brain into a series of “Notes” fields in a CRM. Now, when you call, you get the System. The System sees that you are a “Gold Tier” customer, so it routes you to the “Priority Queue.” It finds an agent who has been idle for at least 42 seconds.

This agent, let’s call her Sarah, is very capable. But Sarah has never spoken to you. Sarah has to spend the first four minutes of the call reading the “Notes” that Greg (who was fired three years ago) and six other people wrote.

Sarah is efficient. But she doesn’t know you. She is reading a map of you, and as any cartographer will tell you, the map is not the territory. The continuity that made the problem bearable has been sacrificed on the altar of the load-balancer. We have balanced the load, but we have broken the thread.

The Specialist’s Anchor

This fragmentation is why we are seeing a quiet migration toward specialists. When everything is routed, people crave the un-routable. They look for the corners of the internet where the person behind the counter actually knows the inventory because they live in it.

Consider the difference between a massive, generalist e-commerce platform and a dedicated specialist. In the generalist world, you are a data point. If you buy a product and it’s defective, you enter a routing system that might land you in a call center in Manila or a chat-bot in Dublin. Neither has ever touched the product you bought. They are just reading a script about it.

Contrast this with a specialist like The Complete Lost Mary Collection. When an adult user is navigating the nuance of

Lost Mary vape flavors,

they are often looking for more than just a transaction; they are looking for the continuity of a specific experience.

A generalist store might stock those devices, but they treat them as “SKU #4829.” They don’t understand the difference between the cooling finish of a menthol profile and the sharp hit of a citrus one. They don’t know the “history” of the device evolution from the MT35000 to the MO20000 PRO.

When you deal with a specialist, the “routing” is organic. You aren’t being dumped into a pool of 5,000 interchangeable agents. You are entering a curated space where the depth of knowledge acts as a form of continuity. It’s the difference between a library and a pile of books. One is organized for discovery and relationship; the other is organized for volume.

The Cost of Equilibrium

The great lie of centralized routing is that it’s better for the customer because it reduces wait times. On paper, it does. Your “Average Speed to Answer” (ASA) drops from 120 seconds to 18 seconds. The managers get their bonuses. The dashboard glows green.

But the “Time to Resolution” (TTR) skyrockets. Why? Because every time you are routed to a stranger, you have to perform the “Backstory Dance.” You have to explain the leaky valve, the missing invoice, and the fact that you already tried restarting the router six times. You are doing the work of the system because the system was too “efficient” to remember who you were.

We are paying for the speed of the connection with the quality of the conversation.

I see this in my own work as a corporate trainer. I get “routed” into departments to fix their communication issues. I am often the fifth consultant they have seen in two years. I spend the first three days just listening to them vent about the last four guys.

The company thinks they are being efficient by hiring the “next available” trainer from a massive firm. In reality, they are starting from zero every single time. They are stuck in a loop of introductions, never reaching the stage of actual transformation.

The Accidental Hang-up as Metaphor

When I hung up on my boss today, the silence that followed was heavy. It was the silence of a severed connection. In an older world, I would have had to dial his specific number again, hear the clicks of the mechanical switch, and wait for him to pick up. There would be a moment of human recognition in the reconnection.

In the modern routing era, I just clicked “re-join.” I was put back into the “active session.” The software didn’t care that I had made a mistake. It didn’t care that I felt like an idiot. It just saw two data points that needed to be re-synced.

We have optimized for the “session” and forgotten the “person.” We have built a world where no one has to wait, but no one is ever truly met.

The most efficient load-balancer is the one that successfully severs every thread of human recognition.

The Path Back to the Direct Line

How do we fix this? It starts with acknowledging that “load balancing” is a technical solution for a human problem-and like most technical solutions, it has side effects.

We need to stop treating every interaction as an interchangeable unit of work. We need to value the “inefficient” 10-minute catch-up at the beginning of a call. We need to prioritize the direct line over the queue.

This is why small businesses and brand specialists continue to thrive despite the crushing weight of the Goliaths. They offer the one thing a load-balancer can never provide: the feeling that you are not just a ticket number waiting for the next available stranger.

The next time you find yourself in a routing system, forced to explain your life story to the third person in an hour, remember Erlang. Remember his beautiful 1917 math. And then remember that you are not a telephone call in Copenhagen.

You are a person with a history, and you deserve a thread that doesn’t break every time the system tries to “balance” you.

Efficiency is a tool, but continuity is the goal. Don’t let the balancer tell you otherwise. Or, if it tries, just “accidentally” hang up.

Sometimes, the only way to find a real connection is to refuse the one the machine is forcing on you.