Hey everyone! I'm not a tech admin, but I've been doing some basic tech support and customer onboarding for the products we sell in my job. Most of my time goes into assisting specialists who have been having trouble in the field, especially since my company currently doesn't have a designated tier 1 support team in my country. Right now, we're relying on distributors for this, but they often don't have the capacity to help. Our higher-ups suggest reaching out to our headquarters for tech support. However, the process has been frustrating. They require a detailed form to be completed for support requests. Despite filling these out thoroughly, their follow-up questions often ask for information we've already provided or are completely irrelevant to the issue at hand. For instance, they once asked about the Windows version for a project that didn't even use a client PC. This back-and-forth can take weeks, and the requests for documentation are also confusing since the projects don't need any. I contacted a support team member to clarify a request and got reprimanded for discussing it outside the ticket—making it tricky and unsustainable for me and my customers. I've heard from someone who worked at Microsoft that performance is often based on how quickly tickets are closed rather than the actual resolution. I'm concerned this is a common practice, so I'm curious: what should a good tech support workflow look like for it to benefit both the company and the customers?
5 Answers
You need to set clear boundaries. If you continue to take on the responsibility for managing all these processes, nothing will change. Stick to the established procedures, and let the flaws of the system become visible. Over time, they might realize the system isn’t working.
Honestly, it sounds like a classic case of the support team being judged on metrics like tickets closed instead of actual user satisfaction. It's not your problem to fix their inefficiencies—remember, you’ve done your part by making the sale. It's on them to provide solid support. Your HQ really needs to get their act together if they're dragging you into their mess!
It’s essential to close tickets promptly, but the customer’s happiness is what really counts. Your HQ support is failing to deliver that. If they keep rewarding speed over effectiveness, it’s going to be an uphill battle to shift that culture. My own team doesn’t track turnaround times because we just focus on solving issues properly!
There are frameworks out there that designate a single point of contact for support issues, which helps streamline communication. The challenge is that even if teams are trained on these frameworks, they often fail to follow them. Your position allows you to shine a light on these issues without being part of the tech support team. If your customers are unhappy because their issues aren’t resolved, that feedback can help press for change.
Tech support workflows can vary a lot, depending on resources and company culture. Sometimes, it helps to gather data on how the lack of efficiency is costing the company in wasted time or lost clients. If you can show that there's a financial downside to their processes, you might spark some motivation for change.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures