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

# Help

Here are the various ways to receive additional assistance while using OpenText Fortify Software Composition Analysis.

You can get in touch with our team through two channels:

* **Our instant live chat:** Our instant live chat is available on weekdays from 9:00 AM to 5:00 PM CET. Connect with our Fortify SCA experts, who are ready to answer any questions you may have. You can access the chat through the [Fortify SCA tool](https://debricked.com/app/en/login) or [our website](https://debricked.com/) by clicking the **Chat** button.
* **Email:** Send an email directly to <support@debricked.com>. You can expect a reply from us within 1 business day.

### **Unable to access live chat**

To access our live chat or the Help widget in the tool, accept the *Support and Functional* cookies. These cookies are essential for specific support features, onboarding tools, service notifications, and more. For additional information about the cookies we use, refer to our [Privacy Policy](https://debricked.com/privacy-policy/).


---

# 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://docs.debricked.com/overview/help.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.