> 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/the-room-brief.md). # The room brief Understand what the room brief tells every character that joins a chat experience, where it appears, and which page answers which question. A chat experience holds one brief, and every character in the room is given it the moment it joins. The brief is written from the room type and the purpose you set while creating the experience, and it is settled at that moment. These pages cover what the brief contains, how its wording is put together, and the one moment that wording is yours to write. ### What the brief is made of A brief is a room type, a purpose, and one briefing written from the two. The room type sets the pattern the conversation runs on. In a room of two or more characters it supplies the sentence the briefing opens with, the rules it closes with, and the short rules chips shown beside it. A room holding one character is briefed in single-character wording instead: its own opening sentence, its own closing rules, and the same three rules chips whichever type the experience was created under. Six types are available, and they differ in who leads the conversation and whether anybody leads it at all. See [How the room brief is written](/api-docs/no-code-experiences/chat-experiences/the-room-brief/how-the-room-brief-is-written.md) for both forms in full. The purpose is the description of what this conversation is about. The five preset room types fill one in for you to edit, and Custom starts empty. You write it in the **Purpose** field of the [create dialog](/api-docs/no-code-experiences/chat-experiences/create-a-chat-experience.md), and it sits in the middle of the briefing written for you. The briefing is the paragraph the characters actually receive. It is written for you from the room type and the purpose, and the create dialog is the one place where you can replace that wording with your own. ### What each character receives when it joins Each character receives the briefing on top of the persona it already has. The character itself is not edited, and a character needs no extra setup before it can be briefed. See [What you need to use Chat Experiences](/api-docs/no-code-experiences/chat-experiences/prerequisites.md) for which characters a room accepts. The side panel states this in the empty room: "Each character receives the room brief the moment they join." Once characters are in, the thread names the persona each one is carrying alongside the briefing. The rules chips beside the briefing restate those rules in short form for you to read. The briefing paragraph is what the characters are told. ### Where the brief appears in the product From the create dialog to the room and its **Previous sessions** page, the brief is visible at five points, and the wording of the briefing itself is shown at two of them: | Where | What it shows | | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The **Create a chat experience** dialog | **What each character will be told**, holding the briefing as an editable box | | The thread, in a room with nobody in it yet | A pinned **Room brief** card: the room type, the purpose, and the rules chips | | The room's side panel | A **Room brief** section below the roster, with the room type and the purpose, for the whole conversation | | The thread, once characters have joined | **What each character was told on joining**, holding the briefing itself and a persona line per character. In a room of one the heading reads **What ⟨character name⟩ was told on joining** | | The experience's [**Previous sessions**](/api-docs/no-code-experiences/chat-experiences/sessions-and-transcripts/review-a-past-session.md) page | The room type, the purpose, and the rules chips, beside the list of past sessions | On **My Experiences**, an experience's card and its list row carry the room type and the purpose as well, but not the briefing. The side panel, the pinned card, and the **Previous sessions** page each carry a **Fixed at creation** label beside the brief. ### Which page answers which question
How the room brief is written
How the room type and the purpose become one briefing, what a room of one receives instead, and what is trimmed when it runs long.		How the room brief is written
Room types reference
All six room types, the rules each one sets, and the purpose it fills in for you.		Room types reference
Write your own briefing
Replace the briefing written for you with your own wording, and put the written-for-you version back.		Write your own briefing
Why the brief cannot be changed
What is settled at creation, and how to run the same characters against different wording.		Why the brief cannot be changed
To set a brief for the first time, start from the create dialog. For what to do about a brief you cannot edit, see the troubleshooting page. {% content-ref url="/pages/Th74Pt0L3LuXdoZaQU34" %} [Create a chat experience](/api-docs/no-code-experiences/chat-experiences/create-a-chat-experience.md) {% endcontent-ref %} {% content-ref url="/pages/shUmFFbGwwR9Qw8p3eov" %} [Briefs and transcripts](/api-docs/no-code-experiences/chat-experiences/troubleshooting/briefs-and-transcripts.md) {% endcontent-ref %} --- # 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://docs.convai.com/api-docs/no-code-experiences/chat-experiences/the-room-brief.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.