> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/doc-chat/why.md).

# Why?

### **Why use Doc Chat?**

Doc Chat lets you interact with your documents using AI, so you can quickly get clear answers and find relevant parts without manually searching. It turns complex document review into a fast, interactive conversation.

✅ **When you *****should***** use it:**

* **To get quick answers from long or complex legal documents**\
  You don’t need to read the entire document, ask questions and get concise replies.
* **To find exact sections related to your questions**\
  Clickable references help you jump straight to relevant parts.
* **To rewrite or draft text directly in your document**\
  Layout-aware AI suggestions can be inserted with formatting intact.
* **To work with multiple files simultaneously**\
  Useful for understanding bundles of documents or transactions.
*  **To focus on legal content with a built-in filter**\
  The chatbot limits responses to legal topics, avoiding irrelevant answers.

***

❌ **When you *****shouldn’t***** use it:**

* **If you need fully reliable legal advice without verification**\
  Always double-check AI-generated answers before relying on them.
* **If you're working with non-legal topics or unrelated content**\
  The chatbot’s legal filter blocks non-legal queries, so it won’t help here.


---

# 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.clausebuddy.com/doc-chat/why.md?ask=<question>&goal=<user_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.