1. Open Support > Knowledgebase. Review existing categories and search for the topic before adding a new article.
2. Use Add Category for a missing area. Choose its parent, clear name, slug and description. Select Admin Only only for material intended for staff.
3. Use Add article and choose the category, title, slug and appropriate visibility. Public instructions, registered-client material and direct-link-only articles have different discovery and access behaviour.
4. Write the outcome first, followed by prerequisites, numbered steps and verification. Include a focused question and answer for a likely failure or decision.
5. Select relevant published articles in Related articles and add useful tags. Link to the actual instructions for a prerequisite instead of copying a second version that will drift over time.
6. Preview the article, test its links and confirm its visibility while signed out and as an ordinary client. Check any enabled language versions.
7. Use responsive images only when they clarify the current interface. Keep every displayed image at or below 900 pixels wide and provide useful alternative text.

Review feedback and article statistics alongside support-ticket patterns. An often-viewed article can still be confusing, so investigate poor feedback and repeated follow-up questions. Assign a product owner and review date to topics affected by module or control-panel updates.

When merging duplicates, preserve a route from old links to the maintained article where your publishing tools support it. Confirm that related articles and ticket macros no longer point to removed content.

• Organize HostBill ticket status assignment and escalation
• Brand and test the HostBill client area
• Give HostBill staff appropriate administrator permissions
• Customize HostBill customer email templates

• HostBill knowledgebase management
• HostBill support ticket management
• HostBill staff and staff team privileges