Chris Rothbauer (redfarmer) wrote in suggestions,
Chris Rothbauer

FAQ references in error messages.

FAQ references in error messages.

Short, concise description of the idea
Add FAQ references to certain error messages that are fixable by the user.

Full description of the idea
Certain error messages are consistantly asked about in support. These error messages could have the appropriate FAQ referenced to give the user the information they need to quickly fix the problem. These error messages include: Log in error. Reference to FAQ 162 if they are having trouble staying logged in. Date/Time & backdate error. Reference to FAQ 33 and FAQ 91, where appropriate. Username/password error. Reference to FAQ 17 if they have forgotten their username or password. Errors in entry length, number of interests, etc. Reference to FAQ 148. Of course these are just a few examples. References could be used for invite code errors, validation errors, and many other error messages, as the need arises.

An ordered list of benefits

  • Newbies who often lack the knowledge of what error messages mean will quickly be able to fix the problem themselves.
  • Hopefully there will be fewer questions in support regarding these issues. Support volunteers will be able to more fully dedicate their time to other issues.
  • An ordered list of problems/issues involved

  • If the FAQ ever changes drastically the reference on the error message would also need to be changed. Fortunately, most of the FAQs involved don't change dramatically on a regular basis.
  • An organized list, or a few short paragraphs detailing suggestions for implementation

  • Code for error messages would need to be changed.
  • Possibly the creation of a system to allow lj_userdoc staff and others to edit the text of an error message?
  • Tags: support, usability, user interface, § historical
    • Post a new comment


      Anonymous comments are disabled in this journal

      default userpic

      Your reply will be screened

      Your IP address will be recorded