# Best Practices #### Define the audience first Before creating a status page, decide: * Is it public? * Is it internal? * Is it for partners? Audience defines content and tone. #### Public vs Private status pages Public status pages should: * Include only customer facing services * Be updated during incidents * Build trust through transparency Private status pages can: * Include technical detail * Track internal incidents * Be protected by password, IP or SSO Do not mix internal and customer facing information. #### One board, one status page Each board maps to one status page. If you need different audiences, you likely need different boards. --- # 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://help.isdown.app/status-page/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.