> 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/conversations-list-screen.md).
# Conversations List Screen
Similar to a text messaging feature on any present-day phone, the User Chat Feature template allows users to interact with one another simply through one-on-one communication. The Conversations List Screen contains all the open conversations between two users, as well as a way to begin a new conversation.
The feature template contains a side navigation component, text components, button components, and a list component that displays information found in the database.
## The Components
### **Side Navigation**
The side navigation will appear on most screens in the template as a means for the user to navigate to other areas of the app. It is important to note that if you change something about the side navigation, it must be changed on other screens, as well.
The ‘Active Menu Item’ for this screen is Menu Item 5.
### Text Components
These two components are static text — meaning they are written in plain text and are not being pulled from the database. You can change this text at any point and it will not impact anything found in the database.
### Button Component — New Button
This button will connect to the ‘New Chat Modal’ screen when clicked so users can begin a new chat with someone.
⚡ **Button Action**
Link Action to the ‘New Chat Modal’ Screen.
### List Component — Conversations List
This component will display a list of all open conversations for the Logged In User.
⚡ **List Action**
Link Action 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 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://help.adalo.com/feature-templates/user-chat/conversations-list-screen.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.