திருத்தங்களை ஒப்பிடு
Answering questions on the Support Forum
Revision 7343:
Revision 7343 by KadirTopal on
Revision 12236:
Revision 12236 by tsmall on
முக்கிய சொற்கள்:
தேடல் முடிவுகளின் சுருக்கம்:
Answering support questions
Answering support questions
உள்ளடக்கம்:
<!-- I think we should rename this to Answering support questions -->
It's easy to get started answering support questions. Don't worry, you don't have to be a Firefox expert to make a difference. Most questions are already answered by a Knowledge Base article and you can just post a link. If you have questions about the support process, just ask us in the [https://support.mozilla.com/en-US/forums/contributors Contributors forum] or in the [irc://irc.mozilla.org/sumo #sumo IRC channel].
Below are some tips on becoming a question-anwsering pro.
__TOC__
= Help wanted =
'''Android helper'''<br>Currently we are looking for contributors who have access to Firefox Mobile on an Android smartphone. With the latest beta we added Firefox Mobile to the Android market place and many many people started using Firefox Mobile for the first time. If you want to help us answering their questions and pointing out what needs to be documented in the KB, please send an email to atopal (at) mozilla dot com
'''Firefox Home helper'''<br>Firefox Home is the Firefox Sync app for iOS. Tens of thousands of people are using it already, but we are just starting to build a community to support it in our forums. If you are interested in helping out you can join the developes in answering user questions and finding out what needs to be improved or better documented in Firefox Home. Please send an email to atopal (at) mozilla dot com and I'll get you started.
= Finding questions =
As mentioned above, use [https://support.mozilla.com/en-US/questions the thread list] to find users in need. Pay special attention to threads that have no replies or where the last poster wasn't another contributor (contributors have names marked in green). If you're on Mac or Linux, watch out for users on the same OS; they may have questions that Windows users wouldn't be able to answer.
= Finding answers =
Rather than trying to figure out the user's problem by yourself every time, first search to see if it's come up before. Try to use the Knowledge Base articles before anything else. These articles have been quality reviewed and have info for all supported systems. Remember, you're not only helping the person who's asking the question, you're helping people who read the thread in the future.
{note}'''To link to an article in the Knowledge Base, put the article's name in double brackets. <nowiki>[[</nowiki>Safe Mode<nowiki>]]</nowiki> becomes [[Safe Mode]]. Don't separate words with + signs; use spaces instead.'''{/note}
If the Knowledge Base doesn't have your answers, you can use any other source you want. Some good ones:
* [/search.php?q=&lang=en&where=all&refine=1#forum Forum threads]
* [http://kb.mozillazine.org/ mozillaZine Knowledge Base]
* [http://forums.mozillazine.org/ mozillaZine Forums]
{note}'''To link to a URL, put the URL in single square brackets, with a space separating the URL from the text. <nowiki>[</nowiki>http://www.getfirefox<!-- -->.com Download Firefox] becomes [http://www.getfirefox.com Download Firefox].'''{/note}
If you find yourself using external resources, consider adding their information to an existing article or proposing a new article – see [[How the Knowledge Base works]]. Because this site is the first line of Firefox support and a Knowledge Base search is the first thing most users will do, having the info in a Knowledge Base article will let the user find the info more easily by themselves.
= Doing investigation =
If you can't find previous cases of the issue happening, here are some tips on figuring out the problem yourself.
* Consider the user's OS and Firefox version.
* Take a look at the user's extensions and plugins. In particular, watch for the [[ActiveX]] plugin (which causes all sorts of problems) and duplicate instances of other plugins.
* Try to isolate the cause of the problem.
** Does the problem happen on your computer? This is useful for determining whether it's a problem with the user's set up or with Firefox or a website in general.
** Does the problem happen in IE as well? If so, it's a problem on the system, not Firefox.
** Does the problem happen when security software is temporarily disabled?
** Does the problem happen in [[Safe Mode]]?
** Does the problem happen in a new profile?
Again, if you find out the solution, consider adding it to the Knowledge Base.
= Posting replies =
* Be nice. It's not your job to defend yourself, others, or even Firefox or Mozilla. Users may just be venting because their problems are frustrating. The best thing to do is to help the user get his or her answer. If you feel that a post has crossed the line, report it to a moderator.
* Make a judgment on a user's experience based on their posts. For example, not all users know how to get to about:config. When in doubt, err on the side of explaining more.
* Look at what OS the user is using and cater your reply to that. For example, Linux users won't have a {filepath C:\Program Files} and Mac users may not be able to right-click.
= Following up =
The answers you give may not be correct, or the user may have some follow up questions for you. In either case, it's useful to both you and the user that your conversation continues. Consider checking "Send me an e-mail when someone replies" on threads you post in so you know about any replies. You may also find [https://support.mozilla.com/en-US/questions?filter=my-contributions the list of threads you posted in] useful.
<!-- I think we should rename this to Answering support questions -->
It's easy to get started answering support questions. Don't worry, you don't have to be a Firefox expert to make a difference. Most questions are already answered by a Knowledge Base article and you can just post a link. If you have questions about the support process, just ask us in the [https://support.mozilla.com/en-US/forums/contributors Contributors forum] or in the [irc://irc.mozilla.org/sumo #sumo IRC channel].
Below are some tips on becoming a question-anwsering pro.
__TOC__
= Help wanted =
'''Android helper'''<br>Currently we are looking for contributors who have access to Firefox Mobile on an Android smartphone. With the latest beta we added Firefox Mobile to the Android market place and many many people started using Firefox Mobile for the first time. If you want to help us answering their questions and pointing out what needs to be documented in the KB, please send an email to atopal (at) mozilla dot com
'''Firefox Home helper'''<br>Firefox Home is the Firefox Sync app for iOS. Tens of thousands of people are using it already, but we are just starting to build a community to support it in our forums. If you are interested in helping out you can join the developers in answering user questions and finding out what needs to be improved or better documented in Firefox Home. Please send an email to atopal (at) mozilla dot com and I'll get you started.
= Finding questions =
As mentioned above, use [https://support.mozilla.com/en-US/questions the thread list] to find users in need. Pay special attention to threads that have no replies or where the last poster wasn't another contributor (contributors have names marked in green). If you're on Mac or Linux, watch out for users on the same OS; they may have questions that Windows users wouldn't be able to answer.
= Finding answers =
Rather than trying to figure out the user's problem by yourself every time, first search to see if it's come up before. Try to use the Knowledge Base articles before anything else. These articles have been quality reviewed and have info for all supported systems. Remember, you're not only helping the person who's asking the question, you're helping people who read the thread in the future.
{note}'''To link to an article in the Knowledge Base, put the article's name in double brackets. <nowiki>[[</nowiki>Safe Mode<nowiki>]]</nowiki> becomes [[Safe Mode]]. Don't separate words with + signs; use spaces instead.'''{/note}
If the Knowledge Base doesn't have your answers, you can use any other source you want. Some good ones:
* [/search.php?q=&lang=en&where=all&refine=1#forum Forum threads]
* [http://kb.mozillazine.org/ mozillaZine Knowledge Base]
* [http://forums.mozillazine.org/ mozillaZine Forums]
{note}'''To link to a URL, put the URL in single square brackets, with a space separating the URL from the text. <nowiki>[</nowiki>http://www.getfirefox<!-- -->.com Download Firefox] becomes [http://www.getfirefox.com Download Firefox].'''{/note}
If you find yourself using external resources, consider adding their information to an existing article or proposing a new article – see [[How the Knowledge Base works]]. Because this site is the first line of Firefox support and a Knowledge Base search is the first thing most users will do, having the info in a Knowledge Base article will let the user find the info more easily by themselves.
= Doing investigation =
If you can't find previous cases of the issue happening, here are some tips on figuring out the problem yourself.
* Consider the user's OS and Firefox version.
* Take a look at the user's extensions and plugins. In particular, watch for the [[ActiveX]] plugin (which causes all sorts of problems) and duplicate instances of other plugins.
* Try to isolate the cause of the problem.
** Does the problem happen on your computer? This is useful for determining whether it's a problem with the user's set up or with Firefox or a website in general.
** Does the problem happen in IE as well? If so, it's a problem on the system, not Firefox.
** Does the problem happen when security software is temporarily disabled?
** Does the problem happen in [[Safe Mode]]?
** Does the problem happen in a new profile?
Again, if you find out the solution, consider adding it to the Knowledge Base.
= Posting replies =
* Be nice. It's not your job to defend yourself, others, or even Firefox or Mozilla. Users may just be venting because their problems are frustrating. The best thing to do is to help the user get his or her answer. If you feel that a post has crossed the line, report it to a moderator.
* Make a judgment on a user's experience based on their posts. For example, not all users know how to get to about:config. When in doubt, err on the side of explaining more.
* Look at what OS the user is using and cater your reply to that. For example, Linux users won't have a {filepath C:\Program Files} and Mac users may not be able to right-click.
= Following up =
The answers you give may not be correct, or the user may have some follow up questions for you. In either case, it's useful to both you and the user that your conversation continues. Consider checking "Send me an e-mail when someone replies" on threads you post in so you know about any replies. You may also find [https://support.mozilla.com/en-US/questions?filter=my-contributions the list of threads you posted in] useful.