Read SMS send-attempt logs

Open Logs → SMS logs to review SMS send attempts made through the store connection. Use this log first when a customer says a text did not arrive, but remember that it records StoreMink's initial send result rather than confirming receipt on the phone.

Test this on your own account first. Before relying on SMS for customers, complete one test message to a number you own and have consent to use and confirm the StoreMink attempt, Twilio acceptance, handset receipt, exact text, sender, and segment count. This log alone is not that end-to-end proof.

What the log shows

• The notification event, recipient, sender header, message body, and attempt time.
• A sent, failed, or skipped state.
• The segment count used to understand provider cost.
• The initial error recorded when StoreMink could not confirm a send, or the reason an attempt was skipped.

When Twilio accepts the request, StoreMink stores the provider message SID internally for support and reconciliation, but the current SMS log screen does not display that SID or the historical DLT template ID.

Understand the three states

• Sent means Twilio accepted the initial request and returned a provider SID. It does not confirm delivery to the customer's phone.
• Failed means Twilio rejected the initial request or StoreMink could not confirm its outcome. Read the recorded error before trying again.
• Skipped means StoreMink did not send the request, for example because the body or phone number was missing.

Why sent may still not arrive

An Indian carrier can later drop a Twilio-accepted message for a DLT mismatch. StoreMink does not currently ingest later Twilio or carrier status updates, so this log remains at the initial result and cannot prove that the phone received the message. Compare the body and sender shown in the row with the currently configured template under Notifications and with the DLT portal; the row itself does not expose its historical template ID. Use the store's Twilio account when a provider-side check is needed.

Before retrying

1. Open the failed log row.
2. Confirm the mobile number and consent.
3. Check the Twilio balance and connection status.
4. Compare the sent body with the DLT record.
5. Repeat the originating action only after fixing the cause and checking that another message will not create a duplicate.

Repeated attempts can create duplicate customer messages and additional Twilio charges. A sent row may still reach the customer later, so do not send a second copy merely because StoreMink has no later carrier state.