> For the complete documentation index, see [llms.txt](https://docs.mosofin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosofin.com/troubleshooting/contact-support.md). # Contact support Before contacting support, collect the information needed to identify the issue without exposing private financial or account data. Include: * A short description of what you expected and what happened. * The affected feature, such as Data sources, Claude, API Tools, or Billing. * The workspace name only when it is safe to share. * The approximate date and time of the issue, including your time zone. * A task identifier from Activity when one is available. * The browser and device you were using. Do not include: * Your MosoFin or QuickBooks password. * Verification codes, access tokens, or authorization links. * Card or bank details. * Unredacted client financial data. * Screenshots that expose email addresses or private company information. Email from the address associated with your account. Include one issue per message so the expected result, observed result, and task identifier stay together. > **Important:** Support should not ask you to send your password or a full payment card number. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mosofin.com/troubleshooting/contact-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.