I Love the Job. I Hated Every Tool I Used to Do It.
Ten years. That's how long I spent in customer support before I snapped — not at a customer, at a dashboard.
I was staring at a metrics panel that some product team had clearly built after interviewing exactly zero support agents, and I had this moment of absolute clarity. The kind of moment that in an RPG would trigger a cutscene. The music changes. The camera pulls back. Your character makes a decision they can't undo.
I love support. The puzzle-solving. Taking someone from furious to grateful in twelve minutes. The bizarre, hilarious, sometimes heartbreaking humanity of it. I genuinely love the work — still do it every day.
The software, though? The software made me want to walk into the ocean.
The Clark Kent Problem
Support agents are living double lives.
Customers see Clark Kent — calm, professional, measured. "I completely understand your frustration, and I'm going to take care of this for you." Polite. Composed. Maybe even a little boring.
Behind the screen? Superman. Juggling six conversations, de-escalating someone who's been transferred four times, troubleshooting a bug that engineering swears doesn't exist, and somehow maintaining a CSAT score that would make most people weep with pride.
Every support agent I've ever worked with has this duality. And every piece of support software I've ever used treats Superman like a data entry clerk.
That's the problem. That's the whole problem.
What a Decade of Bad Software Looks Like
I could write a book about this. (Maybe I will. Working title: Tickets and Trauma: A Memoir. Kidding. Mostly.)
Year one, you're optimistic. "Oh, we're switching to a new platform! Maybe this one won't make me want to throw my laptop out the window." Year three, you've accepted that every tool has the same disease: it was built for the person who reviews your performance, not for you. Year seven, you start sketching alternatives on napkins during lunch. Year ten, you quit and build the thing yourself.
Gartner's research puts agent attrition at 30-45% annually. They list "tools" as a major factor. I could have told them that for free.
Average handle time. First response time. Resolution rate. These metrics aren't evil — they're supposed to be proxies for customer experience. But somewhere around year four, they stopped being measurements and started being weapons. "Your AHT is 47 seconds above target." Cool. So I should rush the customer who's crying about their dead grandmother's account? That'll boost the numbers.
And the interfaces. My god, the interfaces. Dashboards designed for executives who glance at them once a week, presented as the homepage for agents who live in the tool eight hours a day. That's like designing a cockpit for air traffic control instead of the pilot. The controller needs information, sure — but maybe put the throttle where the person flying the plane can reach it.
The Feeling That Died (But Didn't Have To)
Remember your first week in support? Before the burnout ate through the novelty?
There was something genuinely exciting about it. Someone had a problem. You figured it out. They were happy. You were happy. It was puzzle-solving with real stakes and real gratitude. Like being a hero in a game where the NPCs actually remember what you did for them.
That feeling didn't die of natural causes. The software killed it. Slowly, methodically, one soul-crushing interface at a time.
What if it didn't have to die?
So I Built the Thing on the Napkin
cStar exists because of a question I couldn't stop asking: what if the software actually respected the people using it?
On the outside, your customers see clean, professional support. They don't know what's happening behind the scenes. They don't need to. They just get great service.
On the inside? Agents see XP bars filling up. Boss battles against brutal ticket queues. Achievements that unlock because you actually earned them. Streaks that build because you keep showing up.
A reason to care about Monday morning. That's it. That's the whole pitch.
(If you want the deep dive on why this works — the neuroscience, the behavioral psychology, the part where I ramble about Chrono Trigger for three paragraphs — read The Psychology of Gamification: Why XP Actually Works.)
"Oh Great, Another App With Badges"
I've seen the eye-roll. I've done the eye-roll. Badge fatigue is real, and most gamification deserves the skepticism it gets.
But we're not decorating broken software with stickers. We rebuilt the whole thing with human psychology baked into the foundation. XP isn't arbitrary — it's tied to the things that actually matter. Helping customers quickly. Maintaining quality. Going beyond on the difficult tickets. Plus Ultra, if you know.
Boss battles aren't random — they're challenging queues that genuinely need attention. Clear one, and you haven't just leveled up. You've actually helped the business. The game and the work are the same thing.
For the Me Who Was Grinding Ten Years Ago
I built cStar for a specific person. The version of me who was sitting in that desk chair, loving the work, hating the tools, sketching alternatives on napkins, wondering why nobody who'd actually done the job had ever built the software for it. I still answer tickets. I still sit in that chair. The difference is now the software doesn't make me want to walk into the ocean.
Support work doesn't have to feel like drowning. The answer was always right there — build for the agents, not the executives. Don't panic. Don't overthink it. Just build the thing that should have existed all along.
If that sounds like you — or sounds like your team — welcome home.
Josh built cStar after a decade in customer support and still answers tickets daily — because the best way to build support software is to actually use it. He has "geek" tattooed on his arm and zero apologies about it. His office has a neon sign that says "Don't overthink shit." He lives by both.