Every outbound text message is recorded in the SMS log so that you can audit delivery, troubleshoot failed sends and report on usage and cost.
What Is Captured
Each log row contains the recipient phone number, sender ID, message body (or a token-summary if the message contains PII you have chosen not to retain), segment count, delivery status, gateway message ID, the originating user/template and the cost in your billing currency.
Common Statuses
- Queued: Accepted by the platform, awaiting gateway dispatch.
- Sent: Posted to the gateway successfully.
- Delivered: Confirmed received on the handset (where the gateway supplies delivery receipts).
- Failed: Gateway rejected the message — click the row to view the gateway's failure reason.
- Undelivered: Sent but never received (number off, blocked, invalid).
Example Investigations
- A user says they never got their 2FA code. Filter the log by their number and the last 10 minutes. If status is “Failed” with reason “invalid number”, the user has a typo in their stored mobile.
- This month's SMS bill jumped. Group the log by template and date. You will spot the new welcome-flow that started sending three texts to every signup.
- Audit request for GDPR. A data subject asks what SMS you have sent to them. Filter by their number and export to CSV.
Note: Delivery receipts are only as reliable as the destination carrier. Some networks (notably certain pay-as-you-go SIMs) never return a delivery confirmation — status may remain “Sent” indefinitely even though the message was received.