> 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/contact-info.md).

# Contact info

{% 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)). Platforms: web, iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/chat/contact-info.md).
{% endhint %}

The other person in a direct chat, and the switch that mutes that chat for you.

![Contact info](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-1fae47032e3bd8cd3fd6aafe56c0ba417869aaf3%2Fcontact-info.png?alt=media)

* **Where:** web: the info button in the header of a direct [conversation](https://docs.snapfix.com/how-the-apps-work/screens/chat/conversation.md), a side panel titled "Contact Info" (the same panel as [Group info](https://docs.snapfix.com/how-the-apps-work/screens/chat/group-info.md), retitled). iOS: the header's info button opens the group info screen in one-to-one mode. Android: the header's info button opens its own small screen.
* **Who:** either person in the chat. Nothing here depends on roles; each person sets their own mute.
* **Feature:** [Chat](https://docs.snapfix.com/product/features/chat/chat.md)

## Layout

1. Title "Contact Info" with a close button (web).
2. The other person's picture, or initials without one, and the name. With no name the web shows "Contact Name". The name is the person's current name in the site's user list.
3. "Notifications", with the switch "Mute Chat Notifications".

No email, phone number, member list, leave or delete. Removing the chat from your list is "Delete Chat" in [Chats](https://docs.snapfix.com/how-the-apps-work/screens/chat/chats.md). On iOS the group info screen hides its description, members and task-group card in one-to-one mode, and keeps the picture, the name and the switch.

## Inputs

| Field                   | Type   | Required | Default                                 | Rules and messages                                                                                                                                                                                |
| ----------------------- | ------ | -------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mute chat notifications | Switch | No       | Your current `mute_group` for this chat | Takes effect at once, for you only. Web: "Chat muted successfully" or "Chat unmuted successfully"; "Chat not found" when your chat entry is missing; "Failed to update mute settings" on failure. |

## Actions

| Action         | Who           | What happens                                                                                                                                                                                                                                                                                                       | API       |
| -------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------- |
| Mute or unmute | Either person | Writes `mute_group` on your member record for this chat (created if missing) and on your chat entry. While on, you get no push for new messages in this chat (not checked live \[[ASK-49](https://github.com/snapfix/docs/blob/main/ASK.md#ask-49-can-the-live-passes-use-a-second-qa-test-user-on-the-qa-site)]). | Firestore |

## States

* **Loading:** the switch takes its state once your member record loads.
* **Empty:** none; a direct chat always has its two people.
* **Error:** the web toasts above.
* **No permission:** none beyond being in the chat.
* **Offline (mobile):** no offline state of its own. The name and picture come from the device's copy; the mute write needs the network.

## Platform differences

| Topic      | Web                               | iOS                                                                     | Android                                 |
| ---------- | --------------------------------- | ----------------------------------------------------------------------- | --------------------------------------- |
| Shape      | side panel shared with group info | the group info screen, one-to-one mode                                  | its own screen (`UserChatInfoActivity`) |
| Mute label | "Mute Chat Notifications"         | "Mute Chat Notifications" (in a group: "Mute Chat Group Notifications") | "Mute Chat Notifications"               |


---

# 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/contact-info.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.
