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

# History

## History Page Overview

The History page on Miatel’s platform is designed for tracking and analyzing SMS messages. It provides users with detailed information about each message, including its status, recipient, sender, and the operator involved. Users can filter messages by date, time, and status, allowing for precise monitoring of message delivery and identifying any issues that may have occurred.

<figure><img src="https://2191346667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKN2cbBlqJluXsELFSq2I%2Fuploads%2FKI3b0oXAMF9mMWmu41Fd%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202024-10-02%20%D0%B2%2018.12.58.png?alt=media&amp;token=44372f86-4304-4fe3-9eb0-de797d6c43b7" alt=""><figcaption></figcaption></figure>

## Table Columns

The table displays comprehensive data for each SMS message, allowing users to track important details such as time of sending, recipient information, and message status:

| **Date**               | Timestamp of when the message was sent, adjusted based on the user’s computer time              |
| ---------------------- | ----------------------------------------------------------------------------------------------- |
| **Country / Operator** | The сountry mobile operator to which the message was sent                                       |
| **Sender**             | [Identifier of the sender](/docs/sms/sender-id.md)                                              |
| **Recipient**          | Phone number of the message recipient                                                           |
| **Segment**            | [The number of message parts if it was segmented](/docs/sms/sms-segments-and-message-length.md) |
| **Message**            | Content of the SMS                                                                              |
| **Status**             | Current status of the message (as described above)                                              |
| **Account**            | The account used to send the message                                                            |

## Status

The status allow you to sort messages based on several criteria, including:

| **Pending**     | Message scheduled for sending                               |
| --------------- | ----------------------------------------------------------- |
| **Processing**  | Message being sent or in progress                           |
| **Sent**        | Message delivered to the mobile operator                    |
| **Low Balance** | Message not sent due to insufficient balance                |
| **Error**       | Sending failed due to an error                              |
| **Delivered**   | Message successfully delivered to the recipient             |
| **Undelivered** | Message not delivered (expired, rejected, or undeliverable) |


---

# 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.miatel.com/docs/miatel-platform-guide/history.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.
