> For the complete documentation index, see [llms.txt](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/6.-reports/6.1-statistical-reports/6.1.5-sms/sms-history-report.md).

# SMS history report

## Definition

SMS history will list all messages sent to the Customer by the system according to various fields of information so that users can easily follow the operation status and performance.

<figure><img src="/files/GmiP6Wk6wNQhsHTdOrDv" alt=""><figcaption><p>Image 1: SMS history report</p></figcaption></figure>

## Filter of SMS history report

To serve the management and monitoring of information of the process of sending SMS to customers, the system has the following information filters:

<figure><img src="/files/garkExOxI4CKJWcC6684" alt=""><figcaption><p>Image 2: Filter of SMS history report</p></figcaption></figure>

**(1) Contact name:** Customer's name is stored on the system according to the contact phone number.&#x20;

**(2)** [**Company**](/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/2.-company.md)**:** the Customer's company name.&#x20;

**(3) Time:** users can filter SMS statistics by time periods including: hour, day, month (Note: the maximum number of days selected in each filter are 31 days).&#x20;

**(4) Customer phone number:** the phone number of the customer.&#x20;

**(5) Content:** users can enter keywords or full SMS content needed to filter out messages with desired content.&#x20;

**(6) SMS status:** includes 2 statuses (Sending successfully and Sending failed).&#x20;

**(7)** [**Agent**](/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/9.-settings/9.2-hr-and-team-management/9.2.1-personnel.md)**:** select an agent from the list of all agents.

## Result table of SMS history report

Data table SMS history report will show details about 1 SMS through information fields.

<figure><img src="/files/9UOlwiiRd4Yl5EElf0ro" alt=""><figcaption><p>Image 3: Table of SMS history report</p></figcaption></figure>

**(8) SMS ID:** each SMS will have its own code to manage.&#x20;

**(9) Customer phone number:** the Customer's phone number.&#x20;

**(10) Contact name:** Customer's name is stored on the system according to the contact phone number.&#x20;

**(11)** [**Company**](/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/2.-company/2.1.-company-management.md)**:** the Customer's company name.&#x20;

**(12) Brand name:** is the business name registered with the carrier of the hotline number. This name will be displayed instead of the hotline number on the Customer's device.&#x20;

**(13) Agent:** Agent sent SMS to Customer.&#x20;

**(14) Time to send:** is the time the system sends SMS (not the time when the Customer receives SMS on the device).&#x20;

**(15) Content:** detailed content of the sent SMS.&#x20;

**(16) SMS status:** includes 2 states of success and failure.&#x20;

**(17) SMS fails to send reasons:** the cause of the failed SMS delivery.


---

# 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://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/6.-reports/6.1-statistical-reports/6.1.5-sms/sms-history-report.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.