> For the complete documentation index, see [llms.txt](https://help.reekolect.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reekolect.ai/reekolect-resource-center/frequently-asked-questions-faqs/chatgpt-faqs.md).

# ChatGPT FAQs

Find the answers to the most asked questions about Reekolect's integration with ChatGPT

<details>

<summary>Can I train Reekolect chatbots on my own data with ChatGPT?</summary>

Yes, Reekolect state-of-the-art integration with ChatGPT brings you the power of Natural Language Processing, AI, with business intent. You can train your bots to give answers based on the selective data you provide.

</details>

<details>

<summary>Do I need to use API key for ChatGPT powered bot ?</summary>

Yes, You will need your own ChatGPT for running the AI-powered bot. By Default, We give 100 messages for free for demo purposes.

</details>

<details>

<summary>I am not able to use ChatGPT4, as it is greyed out. how can I use ChatGPT4?</summary>

ChatGPT 4 access is enabled only for the user whose API key has access to ChatGPT4. If your API key does not have GPT Model 4 Access, Then It will show greyed out in your account. Here is the official documentation which can help with ChatGPT 4 access.

Link: <https://help.openai.com/en/articles/7102672-how-can-i-access-gpt-4>

</details>


---

# 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.reekolect.ai/reekolect-resource-center/frequently-asked-questions-faqs/chatgpt-faqs.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.