When Tech Support Isn’t Your Day Job: Tales of Reluctant SaaS Wrangling
There’s a special kind of dread reserved for those who inherit a system they never wanted, never asked for, and can never quite escape. If you’ve ever been the accidental admin of a tool no one else wants to touch, you know that feeling: equal parts obligation, resignation, and a dash of “how did I get here?”
Meet u/Erratic-Shifting, a reluctant SaaS task tracker admin who, for a decade, has carried the torch for a system that’s not their job… but somehow always their problem. Their recent Reddit post on r/TalesFromTechSupport is a masterclass in tech support limbo, complete with well-meaning but clueless users, Kafkaesque ticket loops, and the eternal struggle to just say “no.” The community? They’ve seen it all before, and they’ve got opinions.
The Inherited Burden: When “Not My Job” Becomes Your Job
Let’s set the stage: you’re minding your own business, juggling your actual (and very busy) real job, when a group—who probably should never have been allowed near your task tracker—decides they need a massive overhaul. Not just a tweak, mind you, but the “biggest rework I’ve done on a project scheme since I started.”
You stall. You beg for documentation. You gently (then not-so-gently) warn that their dream workflow is a Rube Goldberg machine waiting to collapse. None of it works. Meanwhile, your real workload is “going bananas.”
This is the plight of inherited tech support: you didn’t sign up for this, but you can’t quite walk away. As u/Erratic-Shifting puts it, “I can’t not help people when it’s doable for me. Ok. Mostly.”
But sometimes, the line has to be drawn. When Joy—the ever-kind, ever-clueless user—keeps pinging for help, the admin tries to gracefully disengage, suggesting she’ll be in better hands if someone else is trained. But Joy, an optimist, tries the classic move: “I’ll put in an IT ticket.”
Here’s the twist: IT can’t actually help. All roads lead back to the one person who knows the system. And every ticket just tanks IT’s metrics and cycles back to square one. “What’s the official way to get more support?” Joy asks. The answer? There isn’t one. Just the weary sigh of a lone admin.
The Community Chimes In: Laughter, Sympathy, and Hard Truths
Reddit’s comment section is where the real magic happens. Users came out in droves to share war stories, offer advice, and, of course, commiserate. The top comment by u/oxmix74 captures the escape fantasy many dream about: “I got out of support role by retiring. I highly recommend this solution.” The idea that true freedom only comes with retirement is both hilarious and, for some, painfully real.
But even in retirement, old habits die hard. As u/oxmix74 admits, the work calls kept coming—especially when they’d foolishly shared a personal cell number. Sometimes, helping out “brought me some joy,” especially when the tables turned and the retiree could answer with, “If I was still working for Acme I might have to pretend that I give a damn.”
The gallows humor continues with u/jeffbell’s observation: “And that is how Joy was put in charge of the task system.” It’s the classic tech support move—when you ask too many questions, you win the privilege of running the whole show. The original poster’s response? “I don't know how I feel about watching the system I shepherded against my will driven to insanity by a novice. But I do feel.” If you’ve ever watched your carefully balanced system land in the hands of a well-meaning but inexperienced user, you know that feeling is… complicated.
Ticket Loops and the Myth of “Official” Support
One of the most relatable moments in the post is the endless loop of support tickets. Joy tries to escalate, but every path circles back to the same overworked admin. u/GeneralJabroni nails it with a dose of truth: “This is the official way. You just gotta either wait for me to have time to deal with this or convince someone with power to hire more help.” Sometimes the “official” process is just waiting for the one person with the keys to the kingdom.
Others, like u/Geminii27, bring a pragmatic edge: if the company won’t pay for real support, it’s not a priority—and it shouldn’t be your problem to solve for free. “If I’m not getting paid, that time is better spent on the thousand and one other things clamoring for my attention.” The OP’s reply? “Ain’t got a corporate clock, ain’t got an internal clock. No clocks to be had. Personal problem though.” It’s a wry admission that boundaries are hard, especially for those cursed with a helping instinct.
The Reluctant Hero’s Dilemma: Why We Keep Saying Yes
So why do we keep stepping up, even when it’s not our job? Maybe it’s guilt. Maybe it’s pride. Maybe it’s just the knowledge that if we don’t, chaos will reign. But as this tale—and the comments—make clear, there are limits. Sometimes, the best you can do is look for a “new patsy,” pass the torch, and try to reclaim a little sanity.
The takeaway? If you’re stuck wrangling a legacy system you never wanted, you’re not alone. The struggle is real, the community feels your pain, and somewhere out there, another reluctant admin is fighting the same good fight.
Have Your Own Tale of Tech Support Woe?
Ever found yourself in a similar not-my-job nightmare? Share your stories in the comments! Or, if you’ve found the magic formula for escaping tech support purgatory (short of retirement), give the rest of us hope. Because as anyone who’s been “the only one who knows how it works” can tell you, sometimes just knowing you’re not alone is enough to keep you going.
Original Reddit Post: When it's not your day job