> 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/staff/sms-email-delivery.md).

# SMS/E-mail delivery

{% 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. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/staff/sms-email-delivery.md).
{% endhint %}

Staff look up the SMS and email messages Snapfix sent: when, to whom, the provider's status and response, and for SMS the cost.

* **Where:** admin app `/sms-email-delivery`; menu "SMS/E-mail Delivery".
* **Who:** any signed-in staff user. The route checks only that a session exists. The two log routes check no staff flag, so any signed-in user of any customer can read every customer's logs, and they put the filter values into their SQL.
* **Feature:** [Support tools](https://docs.snapfix.com/product/features/staff/support-tools.md)

## Layout

The title "SMS/E-mail Delivery", then the tabs "SMS" and "Email", on "SMS" at first. Each tab has the same layout:

1. At the right, "Add/Remove columns" with a round button that opens the column menu.
2. The table, paged on the server: 10 rows by default, with 10, 20, 50 or 100 rows per page and a page jump. It scrolls sideways.

**SMS columns.** Shown by default: "Sent At", "Recipient Phone", "Status", "Message ID", "SMS Type", "Cost (USD)" and "Source". Hidden by default: "UUID", "Carrier", "Message Parts", "Provider Response" and "Created".

**Email columns.** Shown by default: "Sent At", "Delivered At", "Recipient", "Subject", "Event Type" and "Status Detail". Hidden by default: "UUID", "From Email", "From Domain", "Message ID", "Processing Time (ms)", "Recipient ISP", "Source IP", "Outgoing IP", "Sender Identity", "Sent By IAM", "Operation", "All Recipients" and "Created".

* Searchable: SMS "Recipient Phone", "Message ID", "Source" and "Carrier"; email "Recipient", "Subject", "From Email", "Message ID" and "Status Detail".
* Sortable: every searchable column, and "Sent At", "Status", "SMS Type", "Cost (USD)", "Delivered At", "Event Type" and "Created" (webadmin\_angular @ db972390b8, `src/app/services/sms-email-delivery/sms-email-delivery.service.ts:52-168`).
* "Sent At" and "Delivered At" show the time text the API sends, in UTC ([`GET /email-logs`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-email-logs)). "Created" is converted to the browser's time zone and shown as "MM/dd/YYYY HH:mm:ss". No heading names the zone.
* On the Email tab, "Status Detail" is blank on rows whose event type is "Delivery", compared without case (`src/app/pages/sms-email-delivery/components/delivery-table/delivery-table.component.ts:112-118`).

## Inputs

| Field                              | Type                                | Required | Default            | Rules and messages                                                                                                                                                                                                                                                                                                                                       |
| ---------------------------------- | ----------------------------------- | -------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Column search (searchable columns) | Text, from the column's search icon | No       | Empty              | Placeholder "Search name". "Search" is disabled while the box is empty, and Enter also searches; "Reset" is disabled while the column has no search, and clears it. The trimmed text goes to the server as that column's filter, a contains-match; blank text is not sent. Searches on several columns apply together. A new search goes back to page 1. |
| Column menu ("Show Columns")       | Checkboxes                          | No       | The defaults above | Shows or hides a column at once, with no request. The choice lasts only while the page is open.                                                                                                                                                                                                                                                          |

## Actions

| Action                | Who   | What happens                                                                                                         | API                                                                                                                                                                                                        |
| --------------------- | ----- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Show a tab            | Staff | Lists the first page of that tab's log.                                                                              | [`GET /sms-logs`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-sms-logs) (SMS), [`GET /email-logs`](https://docs.snapfix.com/engineering-reference/api/staff.md#get-email-logs) (Email) |
| Page or page size     | Staff | Loads that page. The row count is taken from the first page; later pages keep it, because the API counts only there. | Same as the tab                                                                                                                                                                                            |
| Sort a column         | Staff | Reloads the page sorted by that column, one column at a time; the column's key is sent as `sort_field`.              | Same as the tab                                                                                                                                                                                            |
| Search a column       | Staff | Reloads from page 1 with the filters (see [Inputs](#inputs)).                                                        | Same as the tab                                                                                                                                                                                            |
| Show or hide a column | Staff | Changes the table only.                                                                                              | None                                                                                                                                                                                                       |

## States

* **Loading:** the table shows its loading state while a page loads.
* **Empty:** the table's empty placeholder.
* **Error:** these calls show no error message. An answer that is not a success empties the table. A failed request keeps the rows shown before.
* **No permission:** none in the app.

## Dialogs and sheets

None. The column search and the column menu are dropdowns.


---

# 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/staff/sms-email-delivery.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.
