> For the complete documentation index, see [llms.txt](https://docs.cloozo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloozo.com/common-errors/after-a-chatbot-has-been-created.md).

# After a chatbot has been created

{% hint style="info" %}
These error messages may come after you have embeded your chatbot on a website.
{% endhint %}

<details>

<summary>The chatbot window is all blank. Nothing is visible.</summary>

This issue is related to Starter Questions. Make sure you are not using any **Apostrophe (’)** in your words. For example, if you want to write a starter question as *Wha&#x74;**'s** the purpose of chapter 6.* This will throw an error later on. Rewrite it as *What **is*** *the purpose of chapter 6.*

</details>

<details>

<summary>The chatbot doesn't provide any response. It just keep on loading.</summary>

The most probable reason for this is the openAI API key not setup properly. Make sure you have added a valid payment method in your openAI account.&#x20;

:warning: *This is not related to your chatGPT subscription. ChatGPT subscription is a diffefrent thing. We are talking about openAI API keys.*

</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 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://docs.cloozo.com/common-errors/after-a-chatbot-has-been-created.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.