In 1876, a man named William from Lowell, Massachusetts, reportedly received the first “wrong number” in the history of the telephone. The story goes that he was trying to reach a local grocer to inquire about the price of flour, but because the wires were tangled and the operator was overwhelmed, he ended up speaking to a confused woman three blocks away who was trying to find her cat.

For a brief, crackling moment, two lives that had no business intersecting were fused by a technical glitch. William didn’t have a script for this. The woman didn’t have a menu to offer him. They simply hovered in the static, two human beings suddenly aware that the system meant to connect them was also perfectly capable of stranding them in the wrong category.

We like to think we’ve moved past William’s frustration. We live in the era of “frictionless” design, where every interface is smoothed down like a river stone. But the smoother the stone, the harder it is to find a handhold when you aren’t a standard shape.

01

The Friction of Being Human

Take Adrian. Adrian is currently sitting in his car, the engine idling, staring at a pharmacy window while his phone is pressed to his ear. He needs to do two things that, in his mind, are a single event: he needs to reschedule an appointment for a physical, and he needs to inform the office that they have his insurance provider listed as “Blue Cross” when it is actually “Aetna.”

To Adrian, these are intertwined. He can’t really confirm the new appointment until he knows they’ll accept the corrected insurance, because the “Blue Cross” error might mean they think he’s out of network.

But the system Adrian is currently navigating was not designed for Adrian-the-Human; it was designed for Adrian-the-Input. The automated voice, a calm, synthetic woman who sounds like she’s never had a bad day in her life, gives him a choice. “Press 1 for scheduling. Press 2 for billing and insurance.”

The Silos of Exhaustion

This is the beginning of the invisible tax. It is the mental labor of carving oneself into pieces to fit the mouth of a machine. If he presses 1, he gets a scheduler who will tell him, “I can move the date, but I don’t have access to the insurance screen. You’ll need to speak to billing for that.” If he presses 2, the billing agent will say, “I’ve updated your carrier, but for the actual calendar, you’ll need to go back to the main menu and select scheduling.”

There is a specific kind of exhaustion that comes from being told your life is a series of unrelated silos. It’s a feeling I’m intimately familiar with lately, perhaps because I’ve spent the last week realizing I’ve been pronouncing the word “hyperbole” as “hyper-bowl” for the better part of a decade.

I said it in a room full of professionals. The silence that followed wasn’t just a correction; it was a realization that I had been operating with a fundamental miscategorization of a common concept. I felt like a “wrong number” myself-a glitch in the conversation that no one quite knew how to route.

The problem with modern service is that it often mistakes “fast” for “simple.” We have spent billions of dollars making sure that the 80% of people who have a standard request can get in and out in seconds. But in doing so, we have offloaded the complexity of the remaining 20% onto the customers themselves. We have made the customer the unpaid “interpretive laborer” of the organization.

Mixed-Use Buildings, Mixed-Use People

Mia T.-M., a building code inspector I know, deals with this in the physical world every day. She’s the person who has to tell a homeowner that their new “she-shed” is technically a “secondary dwelling unit” because it has a sink, or that their porch is actually a “fire egress” because of its proximity to the neighbor’s fence.

“People hate the code, not because the rules are bad, but because the rules assume every building is just one thing. But houses are like people-they’re messy. They’re ‘mixed-use’ by nature. And the moment you have a mixed-use problem, the bureaucracy starts to smoke.”

– Mia T.-M., Building Code Inspector

Why does the system demand a single identity for a multi-faceted problem?

1. The Logic of the Silo

   Modern databases are built on “relational” structures that require a primary key. An agent must select a reason for the call before they can close the file. If the reason is “both,” the computer often won’t let them proceed.

2. The Economy of the Script

   Training a human to handle every possible variable is expensive. Training them to follow an SOP-a “Standard Operating Procedure”-is cheap. It’s easier to teach an agent to transfer than to empower them to look at the whole person.

3. The Resolution of the Paradox

   Companies value “AHT,” or Average Handle Time. If an agent spends twenty minutes untangling Adrian’s knot, their metrics tank. If they transfer him, the timer resets. The “smoothness” for the company is bought with the “friction” of the customer’s afternoon.

The Trust Deficit

The cost of this is higher than we realize. There is a counterintuitive statistic often cited in customer experience circles: nearly 74% of people feel their loyalty to a company is based on how that company handles a mistake or a complex “non-menu” request, yet only about 18% of businesses prioritize training for those specific scenarios.

To put that in human terms: if you have a group of one hundred people, seventy-four of them are waiting to see how you act when the “script” fails before they decide if they trust you. Meanwhile, eighty-two of those businesses are still focusing all their energy on making the 1-through-5 menu buttons slightly faster to press.

Human-Centric Routing

This is particularly true in sensitive sectors like legal intake or medical scheduling. If you are calling a law firm because you’ve been in an accident, you aren’t just a “new lead.” You are a person in pain, possibly in shock, and almost certainly confused. If the AI chatbot demands you choose between “Personal Injury” and “Property Damage” before you’ve even had a chance to catch your breath, the relationship is damaged.

The companies that thrive in the next decade won’t be the ones with the fastest menus; they will be the ones that have invested in “human-centric routing.” This means having a front line that can listen to a complex, messy, “mixed-use” story and say, “I hear both of those things, and I’m going to stay on the line until they’re both fixed.”

Services like

Go Answer

attempt to bridge this gap by offering a blend of human intelligence and technological reach. The goal isn’t just to answer a call; it’s to provide a point of contact that can navigate the nuance that a rigid IVR tree ignores.

The Power of the “And”

Whenever we force a person to choose one “and” over the other, we are telling them that their complexity is a nuisance. We are telling them that they are William in 1876, shouting into a wire that wasn’t built to hold the weight of his real life.

I think back to my “hyper-bowl” mistake. The person who corrected me didn’t do it with a menu. They didn’t tell me to press 1 to hear the correct phonetic pronunciation. They just smiled, said the word correctly in their next sentence, and kept the conversation moving. They absorbed my “glitch” and turned it back into a connection.

We can choose to build systems that recognize the “mixed-use” nature of human existence. We can choose to hire and train for the “messy middle” instead of the “smooth edge.” Because at the end of the day, no one wants to be a data point. We all just want someone to listen to the whole story, insurance errors and all, and tell us that we’ve finally reached the right number.

The menu is a map that refuses to acknowledge the mountain because it wasn’t there during the last meeting.

The real test of a business isn’t how it handles the person who fits the menu; it’s how it treats the person who doesn’t. When we prioritize the “frictionless” experience above all else, we often end up creating a world where the only way to get help is to pretend you’re simpler than you actually are.