> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/no-code-experiences/chat-experiences.md). # Chat Experiences Understand what a chat experience is, what a moderated text room does and does not do, and where to start in this section. A chat experience is a text room built from your own Convai characters. You name it, pick a room type, and write a purpose, and every character that joins is briefed with what you set. Read this page before you create one: it sets out what a room does, what it does not do, and what is kept once the conversation ends. Chat Experiences is in beta, so read **What a chat experience does not do** before you plan around it. {% hint style="info" %} **Before you begin:** If **My Experiences** does not show **Create a Chat Experience**, see [What you need to use Chat Experiences](/api-docs/no-code-experiences/chat-experiences/prerequisites.md). {% endhint %} ### What a chat experience is A chat experience is a saved brief, not a saved conversation. Its name, its room type, and the purpose you write are stored together with the briefing each character receives the moment it joins. That briefing is written for you from the room type and the purpose, and the create dialog is the one place it is yours to reword. Open the experience as often as you like: every session starts a new room from the same brief. You write to the room and the characters answer in it. A character replies when it is addressed—by name, or because the brief says the turn is theirs—and otherwise stays quiet. The room notes who stayed quiet rather than filling with replies. A room holds one character or several; with one, it is a conversation between the two of you. The characters come from your own workspaces, or by character ID when someone has given you access to one. Six room types are available: **Focus group**, **Classroom**, **Meeting simulation**, **Brainstorm**, **Friends chatting**, and **Custom**. Each type sets a different pattern for the conversation—some put you in charge and have the characters answer when they are called on, others have no leader at all—and the purpose you write tells the characters what the conversation is about. ### What a chat experience does not do * **A session is not resumable.** Opening a chat experience always starts a new room. A conversation that has ended cannot be rejoined. * **Characters are chosen for each session.** The room opens empty and you add the characters you want this time. The roster from your last session does not carry over. * **The brief is fixed at creation.** The room type, the purpose, and the briefing are set once, in the create dialog, and cannot be changed afterwards. There is no control anywhere that edits them. To run the same characters against different wording, open the menu on the experience's card or row on **My Experiences** and choose **Duplicate with a new brief**. * **The room is text.** The characters answer in writing, and the room carries no voice. A message can carry a file attachment. ### What is kept when a session ends Finished conversations are kept and can be read again. A chat experience records the rooms opened from it, and each recorded room can be reopened as a read-only transcript from **Previous sessions** in that same menu. A session that nobody wrote in is still listed, and reads **No messages recorded** in place of a first question. Not resumable does not mean not recorded. You can read a finished conversation in full, but you cannot rejoin it or add to it—a new message needs a new room, with characters added again. ### Where to start Work through these pages in order the first time. Together they take you from the hub to a room with characters in it and a first reply on screen.


Open My Experiences Reach the hub where chat experiences and 3D experiences are both created and reopened.	Open My Experiences
What you need to use Chat Experiences The account and character requirements, and what to do if the controls are missing.	What you need to use Chat Experiences
Create a chat experience Name the room, pick its type, write its purpose, and read the briefing before it is fixed.	Create a chat experience
Add characters to the room Seat characters from your workspaces or by character ID, and watch each one join and be briefed.	Add characters to the room
Send your first message Write to the room, address a character so that it answers, and read what the thread reports.	Send your first message
Manage your chat experiences Find, rename, duplicate, and delete the chat experiences on your account.	Manage your chat experiences
Share files with the room What reaches the characters when you attach a file to a message, and what the room keeps afterwards.	Share files with the room

--- # 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.convai.com/api-docs/no-code-experiences/chat-experiences.md?ask=&goal= ``` `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.