Messages Statuses
This section presents the message states while being processed by the Digital Customer Engagement platform or carrier in the emission of campaigns, and their descriptions, for:
When a message is processed by the platform to be sent, it will progress through different steps, reflecting either a final outcome or a transient state.
SMS Statuses
| SMS Message Status | Description |
|---|---|
| SENT | SMS message was sent. |
| EXPIRED | Mobile operator was unable to deliver the message in the specified amount of time. A sample case is that the mobile device was turned off. |
| DELETED | SMS message has been deleted. |
| UNDELIV | Unable to send the SMS message. |
| ACCEPTD | SMS message is in the accepted status. |
| UNKNOWN | SMS message is in invalid status. Unknown error occurred with the mobile operator. This is very unlikely. |
| REJECTD | SMS message was rejected. |
| INVALID_ROUTING | Phone number is not valid. |
| CODE_NOT_ALLOWED | User does not have the short or long code assigned where the message is sent |
| BLACKLISTED | Recipient is blacklisted. |
| QUEUE | SMS message is queued. Acknowledged by internal delivery process but not yet sent. |
| DEQUEUED | SMS message has been removed from the queue and is ready to be published on the mobile operator. |
| DELIVRD | SMS message was successfully delivered. |
| INCOMPLETE | A personalized SMS message has been sent but the placeholder information is empty . Remember, a personalized message is a message that includes placeholders (dynamic fields) such as "Name", "Phone Number", "Last Name", among others. |
| ENROUTE | The SMS message is enroute. |
|
ON TRANSIT STATES
The platform considers Transit states those after the message has been sent to the carrier but it has had no response as to the message's outcome. It is a temporary state that should eventually result on a final outcome.
Email Statuses
| Email Message Status | Description |
|---|---|
| DEQUEUED | The Email has been dequeued. It is being prepared to be sent. |
| NOT_SENT | The notification has not been sent. |
| BAD_TO | Invalid To parameter. |
| BAD_FROM | Invalid From parameter. |
| BLACKLISTED | The email is blacklisted. |
| BLOCKED_DUE_BAD_BEHAVIOUR | Recipient temporarily blocked. |
| SENT | Email message was sent. |
| EXHAUSTED | Retry limit exceeded. |
| BOUNCED_PERMANENT | Recipient blocked. |
| BOUNCED | The email was rejected. |
| COMPLAINED | Recipient marked the email as spam. |
| OPEN | Recipient opened the email. |
| CLICK | Recipient interacted with the email. |
| INCOMPLETE | A personalized Email message has been sent but the placeholder information is empty . Remember, a personalized message is a message that includes placeholders (dynamic fields) such as "Name", "Phone Number", "Last Name", among others. |
Push notification Statuses
| Push notification Status | Description |
|---|---|
| SENT | The notification has been sent successfully. |
| DEQUEUED | The notification has been dequeued.It is being prepared to send. |
| AUTH_MISSING | The credential is not registered. |
| EXHAUSTED | Retry limit exceeded. |
| NOT_SENT | Notification could not be sent. |
| BAD_DEVICE_TOKEN | The device token is invalid. |
| BAD_PLATFORM | An invalid platform attempted to send a notification. |
| AUTH_ERROR | The server encountered an error in the credential while trying to process the request. |
| PAYLOAD_LIMIT_EXCEEDED | The message payload exceeds the limits. |
| INVALID_MESSAGE | The notification contains invalid parameters. |
| DEVICE_QUOTA_EXCEEDED | Too many notifications have been sent consecutively to the same device token. |
| SERVER_UNAVAILABLE | The server could not process the request in time. |
| SERVER_ERROR | The server encountered an error while trying to process the request. |
| UNREGISTERED | The device token is unregistered or inactive. |
| NOT_CONTEMPLATED_ERROR | There was an unexpected error, it is an unacknowledged error. |
| MISMATCHED_TOKEN | The credential does not have the permission to send messages to the device token. |
| INCOMPLETE | A personalized Push message has been sent but the placeholder information is empty . Remember, a personalized message is a message that includes placeholders (dynamic fields) such as "Name", "Phone Number", "Last Name", among others. |
RCS Statuses
| RCS Message Status | Description |
|---|---|
| SENT | A generated RCS Id was obtained and the message was sent. |
| DELIVERED | Message was delivered to the recipient's device . |
| READ | Message has been opened or acknowledged by the recipient. |
| FALLBACK | Message could not be generated by the RBM platform and some other delivery method will be used (this status is final). |
| NOT_SENT | Message delivery failed. |
| INCOMPLETE | A personalized RCS message has been sent but the placeholder information is empty . Remember, a personalized message is a message that includes placeholders (dynamic fields) such as "Name", "Phone Number", "Last Name", among others. |
WhatsApp Statuses
| WhatsApp Message Status | Description |
|---|---|
| SENT | Message was sent to the outbound delivery system. |
| DELIVERED | Message was delivered to the end-device of the recipient. |
| READ | Message has been opened or acknowledged by the recipient. |
| CODE_NOT_ALLOWED | Sender of the WhatsApp Business Account is not valid to send the message. |
| FAILED | Message delivery failed. |
| QUOTA_EXCEEDED | WhatsApp Business Account exceeded the message sending limit. |
| INCOMPLETE | A personalized WhatsApp message has been sent but the placeholder information is empty . Remember, a personalized message is a message that includes placeholders (dynamic fields) such as "Name", "Phone Number", "Last Name", among others. |
Updated about 1 year ago