Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

30620: Message couldn't be delivered


ERROR: 30620

error-30620 page anchor
MESSAGING
ERROR

This error occurs when the Sender ID used for the message does not align with the registered use case for that sender in the destination country. This commonly happens in countries where Sender IDs must be registered and used only for approved traffic types.

Possible causes

possible-causes page anchor
  • The Sender ID in your From value is registered for a different use case than the message content you sent.
  • Your Messaging Service selected a Sender ID that is valid for the destination, but that sender's registered use case does not match the intent of this message.
  • A default Sender ID is configured for the destination country, so the message was sent with that sender because the From value in your request did not match a registered Sender ID exactly.
  • The destination country requires Sender ID registration or enforces country-specific restrictions on approved Sender ID traffic.
  • Send the message with a different registered Sender ID whose approved use case matches the intent of the message.
  • Register or re-register the Sender ID for the business use case you need in the destination country before sending more traffic.
  • Review the Sender Pool in your Messaging Service and confirm that the sender available for the destination country is appropriate for this traffic type.
  • Check your default Sender ID configuration for the destination country. If you need to use multiple Sender IDs for different use cases in one country, remove the default Sender ID and provide the appropriate registered sender in From.
  • Make sure the From value exactly matches one of your registered Sender IDs for that country, including letter case.
  • Review the SMS guidelines for the destination country and align your sender registration and message content with the local requirements before retrying.
  • If the error continues, collect three or more Message SIDs from the last 24 hours that show This error and open a support request.

Additional resources

additional-resources page anchor