Mega (mega) wrote in suggestions,

Join Support, Acknowledgment Page (support licence?)

Join Support, Acknowledgment Page (support licence?)

Short, concise description of the idea
Have users signup to help in support, to acknowledge that they have read certain terms etc...(read full description)

Full description of the idea
Currently there is a code system for account creation. More and more users are trying to help out in support in order to gain points in order to get an extra code.

If users wish to help out, they can, try to and do. There are some users who plainly couldn't care less about helping, or have no idea how to help in support. There is a guide for support but, unless people read it they wont and don't know. If all they want is their 20 points they probably wouldn't bother reading it.

Support now has hundreds of people volunteering off and on. It is becoming increasingly difficult to spot a short and concise GOOD answer from a really BAD one through the masses of responses (not in all instances, but enough to warrant this). Users without privs do wonder why they are not approved, and now there is two communities in which support volunteers can discuss support type discussions. BUT most of the people who wouldn't bother with those communities as well as reading the faqs are the one's who are only in it for codes.

Now, to the actual suggestion..

Instead of having support as a free for all, I suggest that people sign up for it. What I mean by this is that if a user wants to help out, they go to a specific page and fill out a small questionare. Originally I thought of a mini-TOS type page for people to read, except we all know that people scroll to the bottom without reading and press the button. So, instead have a series of paragraphs detailing a couple of things out...alongside them checkboxes, which one would hope would prove they read the document. Once the page is done, they submit. After then they are able to reply to support requests.

An ordered list of benefits

  • Saves the support board from seeing "yeah I get that too, doesn't it suck?" responses.
  • Saves additional clogging up of the system so that other peoples replies are easier to see and therefore approve.
  • It is possible for someone to skip the first and correct answer if it sits nested in a heap of replies, and the next in turn for being the best and correct gets approved, all because of the other 10 or so POOR replies.
  • Gives more control back to support, making it more professional.
  • Helps out the dedicated screened users, as well as those who are ready to approve answers.
  • An ordered list of problems/issues involved

  • Whinging from those who feel that professionalism isn't as important as getting codes.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • An approved (questionare) page would need to be implemented as well as some form of coding or database that can define who has registered as a support volunteer and who hasn't.
  • Tags: support, § implemented differently
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded