SMS Log
The SMS Log lets you select and view the status of sent and received SMS messages. It is the place to confirm whether a specific message was actually delivered by the SMS Gateway, to troubleshoot failures, and to see message activity per user or number. Because it records the gateway result for each message, it is your first stop when a user reports “my text never arrived.”
You can specify a selection filter. You can filter by various fields, including user, range of dates, phone numbers, status, and SMS Gateway.
Running queries against a large database table creates high load on the server, so we strongly recommend minimizing SMS Log record retention with “Keep SMS Log records for” in Tenant or system-wide Preferences where you can also specify “Maximum date range” to limit the date range allowed in records selection in Configuration Manager. We recommend moving any reporting to a different database or a separate server.
Best practices
- Filter by status when diagnosing failures. Narrowing to failed messages quickly reveals whether the problem is one number, one user, or the gateway as a whole.
- Check the gateway column when delivery is inconsistent - a single misbehaving SMS Gateway often explains a cluster of failures.
- Keep a date range on every query over a large log to protect server performance.
Related documentation
- SMS Gateways - configure the gateways referenced here
- Message Detail Records - higher-level SMS and WhatsApp message log
- Messaging Setup Guide - end-to-end messaging configuration