> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/chat.md).

# Chat screens

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/chat/README.md).
{% endhint %}

Chat in groups and tasks. The chat inside a task is part of [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md).

Site, group and direct chats live in Firestore, so most of these screens have no Snapfix API endpoint behind them; the [Chat API](https://docs.snapfix.com/engineering-reference/api/chat.md) covers a task's chat and the few server calls these screens make. With chat off for a site, the apps show [My network](https://docs.snapfix.com/how-the-apps-work/screens/chat/my-network.md) in place of Chats, and the web sends `/chat/:id` to `/fix`.

| Screen                                                                                       | Platforms         | Where                                                               |
| -------------------------------------------------------------------------------------------- | ----------------- | ------------------------------------------------------------------- |
| [Chats](https://docs.snapfix.com/how-the-apps-work/screens/chat/chats.md)                    | web, ios, android | web `/chat/:id`; iOS and Android: Chat > "CHATS"                    |
| [Chat conversation](https://docs.snapfix.com/how-the-apps-work/screens/chat/conversation.md) | web, ios, android | web `/chat/:id?chatID=`; iOS and Android: a chat in Chats           |
| [New group chat](https://docs.snapfix.com/how-the-apps-work/screens/chat/new-group.md)       | web, ios, android | web and mobile: "+" in Chats                                        |
| [Group info](https://docs.snapfix.com/how-the-apps-work/screens/chat/group-info.md)          | web, ios, android | web and mobile: the header of a group chat                          |
| [Contact info](https://docs.snapfix.com/how-the-apps-work/screens/chat/contact-info.md)      | web, ios, android | web and mobile: the header of a direct chat                         |
| [Message info](https://docs.snapfix.com/how-the-apps-work/screens/chat/message-info.md)      | web, ios, android | web and mobile: a message, "Info"                                   |
| [Chat contacts](https://docs.snapfix.com/how-the-apps-work/screens/chat/contacts.md)         | web, ios, android | web `/chat/:id`, "MY NETWORK"; iOS and Android: Chat > "MY NETWORK" |
| [My network](https://docs.snapfix.com/how-the-apps-work/screens/chat/my-network.md)          | ios, android      | iOS and Android: the Chat tab when chat is off                      |


---

# 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.snapfix.com/how-the-apps-work/screens/chat.md?ask=<question>&goal=<user_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.
