Messaging platforms commonly distinguish submission, provider acceptance and final delivery status. The exact labels and meanings depend on the route, operator and provider.
Common status meanings
- Accepted or queued: the provider received the request for processing.
- Pending: no final delivery result has arrived yet.
- Delivered: a delivery receipt reported successful delivery to the destination network/handset path as defined by the provider.
- Failed or rejected: the route or downstream system reported a failure.
Diagnose a missing message
- Confirm the recipient number and country code.
- Check the message ID and submission timestamp.
- Review route, sender/header and template configuration.
- Inspect provider error codes and callback/webhook events.
- Check whether the report is delayed rather than absent.
Monitoring and reporting
Report delivery as a rate based on a clear denominator and time window. Separate queued messages from confirmed deliveries. Avoid promising a universal delivery percentage because delivery depends on operator, destination and route conditions.
Use message IDs, timestamps and masked recipients when contacting support. Do not send customer OTPs or unnecessary personal data in diagnostic logs.
Let us know if you still need help with this topic.
