V
ViagraFalls
Guest
Marco|MindArk said:That was along my thoughts also...
Cheers
It crossed my mind as well, and would work just fine. If you want some more ideas or possibilities to look into, we can hold brainstorming sessions. You'd only have to pick what you think would work best/would be most cost efficient to implement etc
I think some of the key issues people have with support can be summed up easily:
- Cases are closed without the actual problem being addressed. Support shouldn't decide when a case is closed; we should.
- Too many copy and paste replies. Possible way to prevent this from happening is categorising stuff better. Game suggestions/improvements could be a handed a seperate category.
Another way to prevent repetitive questions from being asked could be using a FAQ covering the most common questions. Before submitting a support ticket, the user can look through the FAQ to see if they issue has been covered yet.
Yet another thing might be showing titles of the last 5 submitted support requests. If another user wants to submit the same problem, they can use a '+' sign next to the issue, to indicate they, too, experience it. Easy way to see whether a bug is stand alone, or affects numerous people (and should thus be prioritised).
- Open issues list so the community has insight into what is being dealt with.
Possibly combine this with the above "+" thing.
- Support staff ought to be identifyable. We deserve to at least know who we are dealing with. Perhaps a reputation system for support people? Support ought to be judged by how helpful they are. It's in MA's best interest to ensure the customer base perceives support as pleasantly as possible. (The same thing should apply to the coders, by the way. Screw up too many times, and you'll face consequences. Harsh, yes. Neccessary? Very much so).
I am sure there's more. This just was stuff I just quickly came up with.