> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/user-chat/new-chat-modal-screen.md).
# New Chat Modal Screen
The New Chat Modal Screen is a modal window that allows the logged in user to select another user to begin a conversation via text with them.
The New Chat Modal Screen allows for the Logged In user to select another user to begin a conversation with. This screen is made up of several components that have already been discussed in previous screen help docs, except for one, with a unique filter and several actions.
## New Components
### **Simple List**
This list displays all the names of the users inside the app except for the name of the Logged In User. The list is filtered by ID is **not equal** to the logged-in user ID.
⚡ **List Actions**
1. Create a conversation in the Conversations Collection with the names of the two users (Logged In and Current User)
2. Update the newly created conversation with the Users and ‘Add Current User.’
3. Update the newly created conversation and add the ‘Logged In User’ to “Users”
4. Link to the ‘Chat Screen’
---
# 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://help.adalo.com/feature-templates/user-chat/new-chat-modal-screen.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.
