You can use articles to provide help guides, how-to information, FAQ answers - any information that you want users to be able to look up for themselves.
To create an article from scratch:
Note Saving a new article as **draft** is useful if you don’t want to publish it straight away; for example, if you haven’t finished it yet, or you want to get someone else to check it over before you publish it. Because draft articles appear in the **Pending** section, saving them with draft status makes it more obvious to other agents that there is an article in progress.
When you have finished creating your article, you should consider helping users find it by linking it to related articles, setting search terms, or adding labels. See Helping users find content for details.
Pending articles are a way to keep track of which articles need to be written.
Select the Pending Articles filter (at the top of the Pending section) to view all pending articles.
From this view, you can use the Add button at the top left of the list pane to create a new pending article.
Enter a brief description of the article and click Add.
Often an article that needs to be written will be about an issue that has come up in a ticket. You can make a pending article based on a ticket using the Create a new pending article action available from the ticket Actions menu.
A pending article created this way is linked to the ticket.
When you click Create Article, the new article takes the title of the original ticket, and the first message from the ticket is inserted into the article, formatted as a question.
You can edit the content from the ticket as the basis for the beginning of the article.
If you want to refer to more details of the original ticket, click the link to it at the top of the new article window to open it in the content pane.
Note that when editing an article, you can’t use drag and drop to add attachments or images as you can with a ticket message.
You can attach a file to the article using the Attachments section at the bottom.
To help you keep content up to date you can add a review date to article properties:
When the article reaches its review date, it is moved into a pending status visible in the publish area. An agent with sufficient permissions will be able to edit the content and re-submit this for review.
You should make sure to review your Knowledgebase regularly and update articles.
Some Knowledgebase articles will eventually become obsolete: for example, because they’re about a product that hasn’t been available for a long time, or they explain how to solve a problem that doesn’t happen any more.
It’s best not to have obsolete articles visible in your Knowledgebase. It makes it seem as if your content is not being updated regularly, as well as making it harder to find articles that are more likely to be relevant. On the other hand, there may still be users who want to read an ‘obsolete’ article - for example, die-hard users of an old product who don’t want to upgrade.
There are several ways to deal with outdated articles:
If you are using approach 2 or 3, you could also edit obsolete articles to add a disclaimer saying that they relate to an older product/issue, perhaps with a link to more up to date articles on a similar issue.