> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/sms/sms-api/incoming/incoming-list.md).

# Incoming list

In the **Incoming** tab, under the **Incoming SMS List** view, you'll find a collection of information about recipient replies—useful if you're using two-way communication (2way), meaning your recipients can reply to the messages you send. This tab allows you to monitor and review incoming messages from recipients.

<figure><img src="/files/Mt6cV1pj9HaBu85IRRwB" alt=""><figcaption></figcaption></figure>

In the **Search** section, you can specify:

* Date range
* Phone number
* 2way SMS header

This allows you to locate recipients based on your selected criteria and either export the results using the export button in the top right corner or analyze them directly within the panel.

The view available in the panel includes details such as:

* Phone number
* Message content
* 2way SMS header
* Time of receipt

<figure><img src="/files/IdWEoLSv9q6zT7hEJ36m" alt=""><figcaption></figcaption></figure>

This section helps you analyze recipient responses by message content and the time they were received.


---

# 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://docs.messageflow.com/sms/sms-api/incoming/incoming-list.md?ask=<question>&goal=<endgoal>
```

`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.
