When the Helpline Can’t Help: Surviving the Great Divestiture Support Mix-Up
Ever had a stranger knock on your door asking you to fix their plumbing, only to realize they don’t even live in your building? Welcome to the world of tech support after a corporate divestiture—where you’re expected to solve problems for people you technically no longer support, and everyone’s a little confused about who’s supposed to do what.
Recently, a tale from Reddit’s r/TalesFromTechSupport captured this chaos perfectly. A helpline agent for a system we’ll call \(plmSystem recounted how, long after their company (\)bigCompany) spun off a division ($littleCompany), users from the old team kept submitting tickets, expecting help… even though support had been handed off months ago. It’s the tech support equivalent of your ex texting you to fix their Wi-Fi.
The Divestiture Dilemma: When Goodbye Isn’t Goodbye
In theory, when two companies part ways, everyone should know where to turn for help. In reality? Not so much. As the original poster, u/DrHugh, explained, “This happened legally over two years ago, but last fall was when $littleCompany switched to their own copy of $plmSystem.” That was supposed to mean fewer tickets and less confusion. Supposed to.
Instead, a ticket lands in their queue: users at $littleCompany can’t log in, can’t access networked PCs, and are generally having a rough tech day. The twist? The helpline can’t help—these aren’t their users anymore. As u/DrHugh put it with a hint of resigned amusement, “It’s nice that they think we have the power to do something. I wonder how long it will take for them to realize they have to stop sending tickets to us.”
Acquisitions vs. Divestitures: The Good, the Bad, and the Disorganized
The community pounced on a key point: why do divestitures seem to breed more chaos than acquisitions? Top commenter u/KelemvorSparkyfox summed it up: “I swear, divestments are worse than acquisitions...” The OP agreed, explaining that when companies are acquired, things usually go smoothly—there’s a clear path to introduce and train new support teams, ensuring everyone knows what’s what.
But with a divestiture, it’s a whole different beast. Early attempts at training $littleCompany’s new support leads were met with silence. “I offered to train whomever they wanted as a lead for their helpline, but never heard back from them,” DrHugh lamented. During their own $plmSystem “go-live,” users didn’t even know the change was happening or how to reach their new support line. The result? Tickets and phone calls kept flowing back to the old helpline, like a river stubbornly refusing to change course.
One commenter, u/porpoiseoflife, hilariously described the resulting dance as “the ever polite dance around the issue of ‘Not my fucking problem’ without getting memos from HR.” It’s a delicate art: you want to help, but you can’t—and saying so too bluntly can land you in hot water.
The Ghosts of Helpdesks Past: Why Old Habits Die Hard
“Seventeen years.” That’s how long u/fatmanwithabeard claims to have gotten support calls for systems they no longer supported. Tech support, it seems, is haunted by the ghosts of users past. The OP chimed in with their own record: “Ten years later, we got a call from someone wanting to access that division's data. We told him no, because—even if we had it—it belongs to another company.” The lesson? Users will always try the old number first, even if it’s been gathering dust for a decade.
And the communication breakdown isn’t just a post-divestiture issue. As u/Filosifee recounted, even in the world of SaaS (Software as a Service), users sometimes confuse the software vendor’s helpdesk with their own IT department. “I once had someone submit a ticket asking us to connect their printer,” they wrote. It took multiple emails to clear things up—proving that, in tech support, clarity is king and assumptions are dangerous.
Of course, some of this confusion is technical. As u/Geminii27 asked, how do these tickets keep coming through? The answer: old phone numbers and lingering network access. DrHugh explained, “Our phone number works externally, so some of them still call us directly. In addition, some…still have a need to access other $bigCompany systems that haven't migrated yet, so they are on our network and can submit tickets.” Even the act of submitting an “I can’t access things!” ticket is a paradox—how do you ask for help with logins when you’re logged in enough to submit the ticket?
Lessons Learned: Communication, Boundaries, and a Dash of Humor
What can we learn from this saga? First, never underestimate the staying power of an old helpdesk number—users will keep dialing it until the sun burns out. Second, communication during divestitures is critical. As the OP’s “tingly feeling of disorganization” suggested, not being able to reach users directly spelled trouble from the start.
But perhaps the third lesson, as the Reddit comments show, is to keep your sense of humor. From jokes about “Software as a Disaster” to the gentle ribbing of companies that can’t let go, the tech support world survives on camaraderie and the shared knowledge that sometimes, all you can do is shrug and say, “We’ll get right on that for you”—even when you’re not sure who “we” is anymore.
Have you ever gotten a call from a user you haven’t supported in years? Or been caught in the crossfire of a corporate split? Share your own tales of helpdesk confusion in the comments below!
Original Reddit Post: We'll get right on that for you