Knowledge Base articles are the building blocks of self-service support: long-lived answers your team authors once and many customers reuse—paired with the help desk so readers browse and search without opening a ticket for every repeat question.
Articles vs. tickets
A ticket is a one-off conversation about a specific incident or request. An article captures the durable answer: prerequisites, steps, policy notes, and attachments that stay valid until you update or retire the content.
What goes into an article
- Title and summary so search and category browsing surface the right page quickly.
- Rich body content from the article editor—headings, lists, code or examples where needed.
- Optional form-template fields when you want consistent metadata (severity, product area, related links) across many articles.
- Placement in the category tree so authors and readers navigate a hierarchy instead of a flat list.
How end users see articles
Published articles appear in the help desk (help center) experience: customers move through sections you define, open an article, and follow the guidance. That reduces load on the service desk for “how do I…?” questions while keeping complex issues in the queue.
Next steps
When you are ready to go deeper, follow the tutorials on creating, updating, and deleting articles, and read how the category tree and form templates fit together.
Explore Service Management
Knowledge Base and help desk are part of ISMSVision Service Management—workflows, forms, and permissions included.
Knowledge Base & help desk