> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/ai-agent/best-practices.md). # Best Practices #### Keep the agent focused Give each agent a clear, specific purpose. Use separate agents for different request types when needed. #### Maintain a reliable Knowledge Base Keep Knowledge Base content accurate, clear, non-duplicative, and organized into focused topics. #### Design natural conversations Avoid long questionnaires. Let customers provide several details in one message. Reuse information already provided. #### Set clear boundaries Define how the agent responds to unrelated requests and information it cannot access. #### Make handoff part of the journey Offer handoff when: * The customer asks for a human agent. * The request needs human support. * The required information is unavailable. * The agent is not configured to help. #### Keep data collection minimal Collect only information needed for the next customer-journey step. Mark a field as required only when the conversation depends on it. #### Choose the right model Match the model to the use case. Extra reasoning can increase response time and cost. #### Control cost and usage * Keep instructions and Knowledge Base content focused. * Enable reasoning only when required. * Set suitable conversation limits. * Avoid unnecessary follow-up messages. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.pickyassist.com/setting-up-guide/ai-agent/best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.