# Publishing changes

As you build through the chatbot you will reach a point where you are ready to rollout the changes to your website. This is where Publishing comes in. The chatbot and flows have two states **DRAFT** and **PUBLISHED**

### Publishing the Chatbot

All changes you do such as to add intents, update the responses and sentences all the changes remain in the DRAFT state of the chatbot. Once you are ready with the intents you can click **Publish Changes** to make them live. 

{% hint style="warning" %}
Publishing the chatbot does not publish the associated flows. You will need to publish the flows separately. If a flow doesn't have a Published version it will default to using the latest draft version.
{% endhint %}

<figure><img src="/files/PKSovox157j9eNmD4Juy" alt=""><figcaption></figcaption></figure>

### Publishing the Flows

Any new changes made to the flow are saved in a new DRAFT version of the flow. Once you are ready you can go ahead and publish the changes.&#x20;

The Published version of the flow is used in the Published chatbot version. If there are no published version the latest draft version is used.

<figure><img src="/files/hr2eq8fjMn0VCbeuJDEC" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.deepconverse.com/product-docs/chatbots/basics/publishing-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.