# Best Practices #### Q: How should I structure my knowledge base? A: Best practices: * Use clear, descriptive titles * Include comprehensive content * Add relevant tags (comma-separated) * Organize by topic/category * Update regularly as your product changes * Include troubleshooting guides * Add FAQs for common questions #### Q: What makes a good knowledge base entry? A: Good entries have: * Clear title describing the topic * Detailed content explaining the solution * Relevant tags for searchability * Step-by-step instructions when applicable * Examples where helpful #### Q: How often should I update the knowledge base? A: Update whenever: * Your product/service changes * New features are added * Common questions arise * Troubleshooting steps change * Documentation is outdated #### Q: How can I improve AI response quality? A: Improve quality by: * Training the bot with comprehensive documentation * Using descriptive tags * Including FAQs * Adding troubleshooting guides * Testing responses and refining entries * Using continue responses for complex processes --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ansari-labs.gitbook.io/ansari-labs/products/ai-powered-ticket-tool/faqs/best-practices.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.