> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/errors-and-faqs.md).
# Errors and FAQs
Sometimes things don’t work exactly as expected. So here's what you can do!
A file might not upload, a draft may fail to load, or a process could take longer than usual. Most of the time these issues are temporary or caused by something simple, like file format, network interruptions, or very large document sizes.
It **doesn’t mean the platform is broken** - and we’re glad you’re here to quickly figure out what’s going on.
If you face an error or something feels off, you can **reach our support team** in just a few clicks. Sharing a quick **screenshot** (and, if relevant, the **file ID or matter name**) helps us diagnose and resolve your issue faster.
#### How to escalate a problem
1. **Support bot (bottom-left corner)**\
Click the chat widget on your screen to open our in-app support bot. You can describe the issue and upload screenshots directly.
2. **WhatsApp support**\
Message us on our dedicated WhatsApp support number - +91 91370 20567. This is great for urgent queries or quick troubleshooting.
3. **Email support**\
Write to **** with details of the problem and attach screenshots or screen recordings. Include the file ID or matter name if the issue is document-related.
---
# 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.jurisphere.ai/resources/errors-and-faqs.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.