The escapement wheel caught on a burr I hadn’t seen, a microscopic snag that turned a 28-second interval into a grinding halt. I was hunched over a 1708 mahogany longcase, the kind of piece that demands you hold your breath while you work, or else the humidity from your lungs might rust the steel pivot. My tweezers slipped. It was a minor mistake, a tiny scratch on a brass plate that nobody but another restorer would notice in 58 years, but it stung because my mind wasn’t on the clock. It was on the screen in the corner of my workshop. I needed a specific gauge of suspension spring, a simple request that used to take a ten-second phone call to a man named Arthur in Lancashire. But Arthur retired, and his company replaced him with a ‘Service Portal.’

I tried to make small talk with my dentist yesterday while he was excavating a cavity-just a muffled attempt to ask if he liked his job-and he just grunted and adjusted his headlamp. We have become a society of redirected queries. When I tried to order that spring, I didn’t get Arthur. I got a dropdown menu. I was forced to choose between ‘Technical Support,’ ‘Billing Inquiry,’ or ‘Order Status.’ None of them fit. I just needed to know if the 0.008mm spring was back in stock. I picked ‘Technical,’ and the system rewarded me with a confirmation: Ticket #99008. Your request is important to us. Expect a response in 48 business hours.

Ticket #99008

“Your request is important to us. Expect a response in 48 business hours.”

There is a peculiar violence in being turned into a number when you are trying to solve a human problem. This clock, this 318-year-old machine, operates on the principle of direct physical contact. One gear pushes another. If there is a gap, the time dies. But our modern systems are built on gaps. They are built on the ‘buffer,’ a polite term for the purgatory where requests go to cool off so the provider doesn’t have to deal with the heat of a real-time person. It’s a standardization of indifference. They tell us it’s for fairness-that everyone gets their turn in the pipe-but when the pipe is 1288 miles long and narrowed to a pinhole, fairness just means everyone suffers equally.

Take the marketer I met at the coffee shop last week. He needed a high-res logo for a campaign that was launching at noon. He knew exactly where the file was on the server, but his permissions had been reset. He called IT. They told him to open a ticket. He explained the urgency, the 18-minute window before the client meeting. The voice on the other end, likely reading from a script updated 88 days ago, said, ‘I can’t bypass the queue, sir. It creates an imbalance in the workflow.’ He watched his deadline go dark while a server somewhere prioritized a password reset for someone who was on vacation. It’s the institutionalization of delay. We have built cathedrals of efficiency that are actually mausoleums for momentum.

I spent 38 minutes filling out that form for the spring. It asked for my ‘Client ID,’ which I haven’t used since 1998, and my ‘Hardware Revision Number.’ It’s a spring, for God’s sake. It’s a piece of flat steel. But the system doesn’t care about the object; it cares about the data entry. If I don’t provide a valid revision number, the ‘Submit’ button remains a taunting shade of grey. I ended up typing ‘88888’ just to bypass the gate. I lied to a machine so I could talk to a person who would eventually tell me they were out of stock anyway.

Standardization has its place, I suppose. You don’t want a surgeon improvising a new type of knot in your gut because he’s feeling creative. But when we apply that same rigid, ticket-based logic to every interaction, we lose the ‘grease’ of human society. We lose the ability to say, ‘Hey, I know this is technically a support request, but I just need a yes or no.’ By forcing every request through the same narrow pipe, companies aren’t managing work; they are managing their own comfort. It is easier to look at a dashboard showing 108 open tickets than it is to listen to 108 frustrated voices. The dashboard doesn’t have a tone of voice. The dashboard doesn’t sound like a man whose grandfather’s clock has stopped ticking.

I remember once, about 28 years ago, I broke a sapphire pallet jewel. I called the supplier, and the owner’s wife answered. She heard the panic in my voice, walked into the warehouse while we were still talking, and said, ‘I’ve got one in my hand, Luca. I’ll drop it in the post before the 4 o’clock pickup.’ That was the system. The system was her legs and her empathy. Today, she would be required to tell me to log in and upload a photo of the damage.

It’s a strange contradiction. We have faster tools than ever, yet it has never been slower to get a simple answer. We have ‘Live Chat’ bots that are neither live nor capable of chatting. They are just automated labyrinths designed to make you give up. If you persist, you get the ticket. The ticket is the participation trophy of the digital age. It says, ‘Congratulations, you exist in our database. Now go away.’ This is why people are increasingly drawn to platforms that prioritize actual accessibility over bureaucratic hurdles. Whether it’s a niche hobby or a specialized service like tded555, there is a premium on directness now. We are starving for the ‘yes’ or ‘no’ that doesn’t require a login.

I look at the 18 clocks on my wall. None of them are synced perfectly. One is always a few seconds ahead, another a few seconds behind. They have character. They have quirks. If I tried to make them all exactly the same, to ‘standardize’ their heartbeat, they would lose the very thing that makes them valuable to the families that own them. But corporations want the world to be a single, synchronized clock where every tick is a ticket and every tock is a ‘resolved’ notification. They forget that the pendulum only swings because of gravity and friction. When you remove the human friction-the messy, unscripted, direct interaction-the whole thing eventually loses its swing.

I eventually got an email back about my spring. It arrived 48 hours later, just as promised. The email was a ‘No-Reply’ address. It told me that my ticket had been closed because I had provided an invalid Hardware Revision Number. The system didn’t even read my question. It just saw the ‘88888’ and rejected the soul of the request because the data was ‘dirty.’ I sat there in the silence of my workshop, surrounded by the ghosts of 208 years of mechanical precision, and realized that I was the only thing in the room that was truly frustrated. The clocks didn’t care. They just waited for a human hand to fix them, unaware that the human hand was currently tied by a digital string.

I went back to the mahogany clock. I found a way to polish out the burr myself. I didn’t need the new spring; I just needed to stop expecting the system to help me. That’s the real danger of the ticket-number culture. It doesn’t just make things slower; it makes us stop asking. We stop trying to communicate because we know the gate is closed. We settle for ‘good enough’ or ‘broken but quiet’ because the alternative is a three-day wait for an automated rejection.

Last night, I dreamt I was at the dentist again. He asked me to open wide, and instead of teeth, he found a series of QR codes. ‘I need to scan these to see which tooth is hurting,’ he said. I tried to tell him it was the one on the upper left, the one that had been thumping for 8 hours, but he just shook his head. ‘I can’t look at the upper left without a referral code from the front desk.’ I woke up and checked the time. It was 3:08 AM. The mahogany clock was silent. It was waiting for a part that was stuck in a queue, in a database, in a server farm cooled by fans that don’t know my name. We are building a world that is perfectly organized and completely unreachable. And the worst part is, we’re the ones who keep hitting ‘Submit.’