> For the complete documentation index, see [llms.txt](https://emotiv.gitbook.io/flex-2.0-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emotiv.gitbook.io/flex-2.0-user-manual/support/emotiv-support.md).

# EMOTIV Support

### EMOTIV Support

If you are encountering problems with your FLEX or have any technical questions, the EMOTIV Support team can assist you. Visit the [Contact Support](https://www.emotiv.com/contact-support/) page of the EMOTIV website and submit your query.&#x20;

### &#x20;EMOTIV Knowledge Base

[EMOTIV Knowledge Base](https://www.emotiv.com/knowledge-base/) provides useful information and solutions for common tasks related to EMOTIV’s headsets, software and user accounts.&#x20;

### &#x20;FAQs

[EMOTIV’s FAQs](https://www.emotiv.com/faq/) provide answers to some of the most common questions asked by the EMOTIV community.&#x20;

<br>


---

# 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://emotiv.gitbook.io/flex-2.0-user-manual/support/emotiv-support.md?ask=<question>&goal=<endgoal>
```

`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.