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

# Message 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/message-info.md).
{% endhint %}

Who has read one of your chat messages, and who it was delivered to.

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

* **Where:** web: "Info" in the menu of your own message in [Chat conversation](https://docs.snapfix.com/how-the-apps-work/screens/chat/conversation.md), a side panel titled "Message info". iOS: "Info" in the long-press actions, a screen titled "Message Info". Android: the info icon in the actions, a screen titled "Message info".
* **Who:** the sender. "Info" shows only on your own messages, on every platform.
* **Feature:** [Chat](https://docs.snapfix.com/product/features/chat/chat.md)

## Layout

1. Title and a close or back button.
2. The message as a bubble, under its day label ("Today", "Yesterday", the weekday, or the date): the text, a photo with its caption, or a voice note with its player, with "Forwarded" and "Edited" where they apply, and the sent time. On the web the text is set as HTML. The web bubble's read tick never shows, because its status is never set.
3. "Read By": everyone except you whose read time is stored in `read_by`, each with picture, name, date and time. The web sorts it newest first.
4. "Delivered To": the other members who are not in `read_by`, each with the message's own sent date and time, A to Z on the web. Delivery is not recorded: this list is the members who have not read it.

The members are all site users for the site chat, the group's members for a task group or custom group, and the two people for a direct chat. A member with no name shows the fixed English "Unknown". There is no reactions section.

In a direct chat, iOS and Android show one block instead of the two lists, with the delivered time and the read time ("--" until it is read). The web shows the two lists with one person.

Dates use a fixed English format: "Today", "Yesterday", the English weekday, or `dd/MM/yyyy`. The sent time is the short 12-hour time ("3:15 PM") while the list times are "HH:mm" ("Today 15:15"). Sorting "Read By" builds a date from those words, so "Today" and "Yesterday" entries do not sort by the real read time.

## Inputs

None.

## Actions

| Action            | Who        | What happens                                                                                                                   | API       |
| ----------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------ | --------- |
| Open              | The sender | Shows the message with the read data already on it. iOS and Android listen to the message, so the lists update as people read. | Firestore |
| Play a voice note | The sender | Plays the audio in the bubble. Android shows "View transcript" when the message has one.                                       |           |
| Close             | The sender | Closes the panel or the screen.                                                                                                |           |

## States

* **Loading:** the message comes from the conversation; the lists fill in once the members load.
* **Empty:** when nobody has read the message, "Read By" has no rows and every other member is under "Delivered To". Live, both headings showed with no rows under "Read By".
* **Error:** web: a failed member lookup is only logged and the lists stay empty. Android with a missing chat, site or message toasts "Something went wrong. Please try again." and closes.
* **No permission:** only your own messages offer "Info". iOS and Android close the screen if the message is deleted while it is open.
* **Offline (mobile):** no offline state of its own: the screen shows the message it was opened with, and live updates need the network.

## Platform differences

| Topic                           | Web                                                   | iOS                                                                                                                                           | Android                                                                                                                                       |
| ------------------------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Shape                           | side panel                                            | full screen                                                                                                                                   | full screen                                                                                                                                   |
| Title                           | "Message info"                                        | "Message Info"                                                                                                                                | "Message info"                                                                                                                                |
| Direct chat                     | the two lists, one person                             | one read and delivered block                                                                                                                  | one block, "--" until read                                                                                                                    |
| Read ticks agree with the lists | no: custom groups and the site chat stay at delivered | yes                                                                                                                                           | yes                                                                                                                                           |
| After an edit                   | read times kept                                       | read times cleared \[[ASK-45](https://github.com/snapfix/docs/blob/main/ASK.md#ask-45-should-editing-a-chat-message-clear-its-read-receipts)] | read times cleared \[[ASK-45](https://github.com/snapfix/docs/blob/main/ASK.md#ask-45-should-editing-a-chat-message-clear-its-read-receipts)] |


---

# 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/message-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.
