Post by account_disabled on Dec 7, 2023 1:36:47 GMT -6
This means that your article should be organized into chapters and subsections. For example, in the knowledge base, you can search by product, resource type, or various topics such as blogs, dashboards, emails, integrations, and sales templates. Knowledge Base Example: Image Source's Business Knowledge Base (pictured above) groups articles into simple categories such as Create a Store, Advertise, and Create Content to help users quickly identify articles of interest. Use categories to keep your knowledge base organized and ensure that every article has a place and purpose. If required, please attach a table of contents. Sometimes, an article can become very long, especially when you update it with added information. When dedicated customers want a deep, complete understanding of the problem and solution, they scroll to the end.
Knowledge Base Example: Table of Contents However, the length of the article may Phone Number List deter some readers. So, for longer articles, consider adding a table of contents that allows users to jump to chapters like the article above. This will help people find parts of the article that are of particular interest to them and skip any information they don't need. Describe the problem (if applicable). For problem-solution-based scenarios, first state what the problem is. Not all Knowledge a problem; some may simply explain how to complete a task. In these cases, you can skip this step..
Identify symptoms of the problem to clearly communicate what customers should be looking for. For example, list what error messages should pop up if the problem does exist. You want to use basic language and make it as clear and concise as possible. The shorter this section is, the better, as the person reading it is likely to be looking for quick steps to solve the problem. Continue through the steps to complete the task at hand. After stating the problem, you should immediately show the reader how to solve the problem. This section is laid out in easy-to-read steps that can be read and followed sequentially.
Knowledge Base Example: Table of Contents However, the length of the article may Phone Number List deter some readers. So, for longer articles, consider adding a table of contents that allows users to jump to chapters like the article above. This will help people find parts of the article that are of particular interest to them and skip any information they don't need. Describe the problem (if applicable). For problem-solution-based scenarios, first state what the problem is. Not all Knowledge a problem; some may simply explain how to complete a task. In these cases, you can skip this step..
Identify symptoms of the problem to clearly communicate what customers should be looking for. For example, list what error messages should pop up if the problem does exist. You want to use basic language and make it as clear and concise as possible. The shorter this section is, the better, as the person reading it is likely to be looking for quick steps to solve the problem. Continue through the steps to complete the task at hand. After stating the problem, you should immediately show the reader how to solve the problem. This section is laid out in easy-to-read steps that can be read and followed sequentially.