support writing

This started the way most rabbit holes start: browsing Instagram for remote problem-solving roles, I bumped into a job post. I clicked through — and stayed on the company’s site far longer than any application process justifies. It didn’t look like other careers pages. It was playful, confident, and built with a level of care…

Two incidents from my years in payments support look nothing alike on a ticketing system and are, underneath, exactly the same story. One: the login that “couldn’t” be our fault A customer lost front-end access shortly after onboarding. Everything on our side said this should be an easy escalation: they’d completed onboarding a week earlier,…

As platforms grow, support volume grows with them. The reflex is to grow the team with it — more tickets, more people. But teams don’t scale linearly: coordination costs eat the headcount, quality drifts, and six months later you’re hiring again and resolving slower anyway. I ran that experiment from the inside. At Tracom Services,…

The most common — and most frustrating — situation in technical support: a customer reports a bug, and it simply will not reproduce. Not in staging. Not on your machine. Not even on theirs, an hour later. The ticket sits there, mocking everyone. At AZA Finance, a payments and FX platform, being the first responder…

Three teams watch the same failure and count it three ways. The support team counts a ticket. The QA team counts a leaked defect — a bug that escaped testing and reached production. The customer success manager counts a churn-risk moment: a customer who just lost trust in the platform. They’re the same event. And…