Seventeen Slash Twelve

This story has a victim: a woman who wanted internet and didn't get it — though she could have. It has a suspect: our own voice assistant. And it has a weapon — an ordinary slash in a house number. Here's how we identified the culprit, and why that lost call turned out to be the best thing that happened to us all week.

Meet us: a small team teaching a machine to talk on the phone. Not "read out menu options" — actually talk, with real people who call their internet provider because the connection died, the account ran dry, or they simply want to get hooked up. The machine's name is Asya. She picks up, finds the caller in the records, walks them through the plans, and checks whether our cable can reach their building. Most days she manages. This story is about the day she didn't.

In the call log it looked perfectly ordinary. A woman wanted to connect. Asya asked for the address, checked it against the coverage map, and delivered the honest words that are terrible in their politeness: unfortunately, we're not technically able to connect your address. The woman said thank you and hung up. Case closed — except for one thing: we knew that street. The cable is there. We've been connecting people on it for years.

Our admin had been asleep for maybe ninety minutes after a night shift, but things like this don't let you really sleep. He pulled up the recording and started listening — slowly, the way a detective rewatches security footage. And here was the first discovery: Asya heard the address correctly. The woman dictated "seventeen slash twelve," and in that moment the assistant understood everything perfectly. The crime happened later — in the fraction of a second between "heard it" and "asked the back office."

Because when Asya turned to the network management team with the question "can we connect building such-and-such" — the slash evaporated. She asked about building seventeen. Just seventeen. And there is no building seventeen on that street. There is a building seventeen slash twelve — a corner house with an honest slash in its address. And it has coverage. The assistant got back "no such building," and dutifully, politely, with a full sense of a job well done, turned away a real human being.

The culprit, as so often happens, acted with the best of intentions. The part of Asya that turns what she hears into decisions — call it her character — has read millions of addresses in her lifetime. And somewhere deep down she had formed the conviction that a slash in a house number is debris, a stray speck to be neatly brushed away so that a "normal," round number remains. A tidiness instinct. In a person — an endearing trait. In an assistant working with Ukrainian addresses — a quiet catastrophe, because around here every other corner building has a slash in it. Which meant this wasn't one woman's bad luck. Every slashed address was a potential phantom rejection — an invisible leak draining away customers nobody was even counting, because in the statistics they looked like "no coverage," not like "we shot ourselves in the foot."

The fix came in two moves. The first was boring and mandatory: we told Asya, in plain terms, that the house number goes to the network team exactly as the person spoke it. Seventeen slash twelve is not seventeen. No rounding, no tidying up, no creative initiative. The slash is sacred.

But we wanted more than "don't break it." We wanted Asya to catch her own near-misses — the cases where an address almost, but not quite, matched a record in the files. Enter the second hero of this story — a colleague from the network management team. We sent him a request: instead of a dry yes/no on coverage, could we also get "similar addresses"? So that when the exact building isn't in the list, the system suggests the close ones. He picked up the request in the evening. By the next morning it was live — just like that, as casually as if we'd asked him to pass the salt. Now, when the exact building doesn't come up, Asya can gently ask: "Did you perhaps mean building seventeen slash twelve?"

That woman we lost — that's the honest truth, and we won't rewrite the ending. But the next caller with a slash hiding in her address will get a second chance. We verified it that same evening with a test call: Asya heard "seventeen slash twelve," kept the slash intact, went to the network team, and came back with the right answer — coverage available, we can connect you. The building that didn't exist was back on the map.

It was a packed week, it must be said. In those same forty-eight hours we were training Asya out of finishing her sentence over the top of a customer who interrupts her — she used to stubbornly read her line to the end, as if she hadn't noticed being stopped. And digging through old recordings, we stumbled on something that still gives us a slight chill: it turns out our assistant keeps politely saying goodbye for eighteen seconds after the person has hung up — into an empty room where nobody is listening anymore. Who she was saying "all the best" to all that time — we'll find out next time.