Curious about the Customer Support of Pirates of the Burning Sea? Then a very recent article published by Flying Lab might be just what you're looking for.
Overall, things have improved a great deal, I think. We’re still not where we want to be! Trust me when I say we’re still not satisfied with a number of aspects of our overall support. For example, we still have a backlog of incidents submitted months ago. That’s totally unacceptable. The backlog has shrunk considerably since my last devlog, but it still exists and I’m still losing sleep over it. Also, it still happens periodically that a CSR will give a suboptimal response. Whether it be something that would seem to imply they didn’t read your question or request or whether it be just flat out the wrong info, it still happens. That’s also unacceptable. Most CSRs have improved a great deal over time with experience and training. A couple CSRs no longer respond to customer reports but instead help out in other ways.
And that’s actually one of the improvements we’ve made. For every shift, there’s typically a CSR or multiple CSRs on the front line, focusing on responding to tickets in a timely fashion. They spend their time teleporting people out of locked rooms and banning gold spammers and answering tickets. Then there are 2nd-tier CSRs focusing on doing research. Can we repro the bug this player reported? How best to help this customer who has somehow gotten his missions out of order? Did we just uncover a gold-farming ring? That sort of research takes time and the CSRs doing it can’t really pay attention to the queue. But they can be called in to help with the queue if it starts getting out of hand. Similar to how a grocery store will open another lane, pulling in someone who had been stocking shelves a few minutes ago, when the lines get long. When we first launched, cashiers didn’t know how to stock the shelves so, if there was no line, they tended to stand around bored. Now the front-line folks are better trained and can help the 2nd-tier folks with the research and vise versa.
Also, we have a meeting weekly to discuss top issues. We’ve done this since the start of Beta. Before each meeting, I look through our bug database and list the bugs having the biggest impact on the players. We discuss plans for fixing each one what additional data needs to be gathered before we can do so; which Dev is best suited to do so; whether it’s a complicated enough problem that the fix needs to be in the next milestone to ensure sufficient testing. Recently, Aether and I have made tweaks to how we process incoming high priority incidents so that we’re more likely to ensure they’re on this list as well, even if they are simply in the rumor stage and not yet in our bug database.
Read the full article here.
Comments