> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/content/virtual-platform/programme/speakers/conversations.md).
# Conversations (Virtual event)
{% hint style="success" %}
A [chat ](https://eventinsight-consultants.gitbook.io/let-s-get-digital/platform-features/chat)is displayed by default on the right side. Therefore, the conversations tab might be redundant and is disabled by default. You can activate the conversations tab in the [settings](https://eventinsight-consultants.gitbook.io/let-s-get-digital/the-admin-panel/content/programme/speakers/settings).
{% endhint %}
## The menu section
In conversations, speakers have the option to toggle between two chats. The first chat includes everyone in the session. The 'Speakers' chat only includes the speakers. The attendees are not able to see what is being said in the 'Speakers' chat.
In every programme item, a chat is implemented on the right-hand side.
{% hint style="danger" %}
You can at all times delete chats from our platform (lobby, exhibitor or in the virtual program items except the samba conversations) by typing a message "/clean" in the chat.
{% endhint %}
---
# 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://knowledge-base.letsgetdigital.com/the-admin-panel/content/virtual-platform/programme/speakers/conversations.md?ask=&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.
