When a message to one of your subscribers bounces, that means we were unable to deliver the message because it was rejected by the subscriber's wireless carrier. The reasons for a message to bounce greatly vary, but a few examples would be that the subscriber's wireless carrier turned their service off, the subscriber placed a black on short code messaging, etc.
Some bounces are more serious than others though, and Tatango will determine based on the type of bounce, and the amount of past bounces if it's worth it to continue to send messages to that specific subscriber in the future. If we determine that it's not worth it to continue to send messages to a subscriber, we'll automatically Clean them, which means that Tatango will no longer attempt to send that subscriber messages from your campaign. To learn more about how we clean subscribers, click here.
Below is a list of response codes that will trigger a message to a subscriber's mobile phone to bounce. To view the response codes received from a specific message, you need to download a sent message report.
- 351 - Transaction failed: Invalid destination address value
- 410 - Message recipient not found on carrier
- 1030 - External system error
- 368 - Invalid source address value
- 568 - Destination address not provisioned for SMS
- 573 - Short code blocked by subscriber
- 560 - Message recipient not authorized by carrier to receive the message
- 561 - Content blocked by carrier
- 566 - Destination address blocked by carrier
- 569 - Destination address suspended by carrier
- 581 - Prepaid subscriber out of credits
- 588 - Invalid T-Mobile subscriber. Possible causes: out of credits, suspended, content blocked, or not a T-Mobile subscriber
- 810 - Failed message delivery
- 811 - Message Delivery Error: Message expired by carrier
- 815 - Message Delivery Error - Message submitted to but not acknowledged by carrier