The SMS Logs page provides a read-only view of SMS messages sent by the system. It is intended for monitoring, auditing, and troubleshooting SMS delivery by allowing users to search and filter SMS records.

The page is divided into two main sections:

The header contains tools that help you locate specific SMS records.

• Header features:*

• Search bar – Search SMS logs using keywords such as recipient number, message content, or reference values.
• Advanced filters – Narrow down SMS logs using available filter criteria.
• Action / page buttons – Contextual actions depending on your role (if applicable).

Any change to the search query or filters updates the table immediately.

The grid displays a paginated list of SMS log entries.

• Grid characteristics:*

• Read-only table (no row selection)
• Client-side pagination
• Fixed default page size of 25 rows
• Loading indicator shown while data is being prepared

If no records match the current search or filters, the table will appear empty.

• Each row represents a single SMS message.
• Columns show key details such as recipient, message content, status, or timestamps (depending on configuration).
• Rows are not clickable and cannot be selected.

• Use the paginator at the bottom of the table to move between pages.
• You can change the number of rows displayed per page:

• 25
• 50
• 100

• Enter text into the search bar to quickly locate specific SMS messages.
• Use advanced filters to refine results by criteria such as date range or status.
• Filters apply instantly to the table results.

• Open the SMS Logs page
• Use search or filters to find a specific SMS record
• Review message details directly in the grid
• Navigate through pages to view older or newer logs

• SMS records are read-only and cannot be edited or deleted from this page.
• Bulk actions and row-level actions are not supported.

• Combine search with filters to quickly narrow down large volumes of SMS logs.
• Increase the page size when reviewing logs over a specific time period.
• Use this page primarily for verification and troubleshooting purposes.