Cloudbeds Guest Experience SMS Troubleshooting

Messages may occasionally fail to send. Below are some of the most common SMS delivery errors that may appear in the Guest Experience delivery status report and how to troubleshoot them.

Background

Every message in Cloudbeds Guest Experience includes a Delivery Status Report. Most messages will show as Delivered, but when a message fails you may see an Error status explaining the reason for the failure.

Common Errors

Error Description & Troubleshooting
Error 1 – Failed to Send

Generic sending failure. This may occur due to missing template variables, disabled SMS services, incorrect Twilio configuration, or OTA/channel messaging restrictions. 

Troubleshooting:

  • Confirm SMS is enabled in Messaging Services
  • Check the message template for missing variables
  • Multiple channels have rules for guest communication, verify OTA/channel messaging restrictions. 
Error 1001 – Failed to Upload Media

The media file attached to the message could not be uploaded. This usually happens when the file type or size is unsupported. 

Troubleshooting:

  • Use only supported formats:
    • image/jpeg (and image/jpg)
    • image/png
    • image/gif
    • image/webp
    • image/heic
  • Verify the file size and resolution are within allowed limits
  • Check that file storage limits have not been exceeded
1300 – SMS is Disabled

SMS messaging is disabled or not fully registered for the property. 

Troubleshooting:

  • Enable SMS in Messaging Services
  • Complete SMS registration and regulatory compliance
  • Verify that the sending number is properly configured
5000 – Variables Missing

The message template references a variable that does not have a value for the reservation. 

Troubleshooting:

  • Check the reservation details to confirm the variable exists
  • Verify integrations (RemoteLock, Chekin, Operto, etc.) are syncing data
  • Remove or replace the variable if the value is unavailable
5100 – Contains Links Not Approved

The message contains a URL that has not been approved by the Cloudbeds messaging link security system. 

Troubleshooting:

  • Identify the URL included in the message
  • Check formatting or punctuation around the link
  • Enter only the base domain (for example: example.com) - do not include http://, subpaths, or UTM parameters.
  • If that is not the case, contact Cloudbeds Support to have links reviewed/whitelisted if messages are blocked.
  • Once the base domain is approved, all links from that domain (including pages and UTM variants) will send normally.
T30007 – Message Filtered

The message was filtered or blocked by the recipient's carrier or messaging provider due to policy or spam detection. 

Troubleshooting:

  • Confirm the phone number is valid and not a landline
  • Review message content for spam-triggering language
  • If links are included, verify they are approved. Contact Cloudbeds Support to have links reviewed/whitelisted if messages are blocked.
T30032 – Failed to Send

Multi-factor sending failure that can be caused by disabled SMS, missing variables, unapproved links, or carrier filtering. 

Troubleshooting:

  • Confirm SMS is enabled in Messaging Services
  • Check for unapproved links (Error 5100). Contact Cloudbeds Support to have links reviewed/whitelisted if messages are blocked.
  • Verify message templates do not contain missing variables
Twilio T21619

The message body or media content was not provided. This error can also appear when SMS is disabled at the property level. 

Troubleshooting:

  • Confirm SMS is enabled in Messaging Services
  • Verify the message template contains content
  • Check for missing message variables
Unknown error The recipient's carrier returned a generic error message.
Unknown destination handset

The phone number is invalid or no longer active. 

Troubleshooting:

  • Verify the guest's phone number and country code
  • Confirm the number is still active
Unreachable destination handset The recipient device is currently unreachable, usually because the phone is powered off or outside network coverage.
Carrier Violation

The carrier blocked the message due to filtering or policy restrictions. 

Troubleshooting:

  • Review the message content for spam-like language
  • Check that any included links are approved. Contact Cloudbeds Support to have links reviewed/whitelisted if messages are blocked.
  • Confirm the sending number is properly registered
Message Blocked The message was blocked by the carrier before reaching the recipient.
Landline or Unreachable Carrier The destination number is a landline or the carrier cannot receive SMS.

 

Reach out to our support if you need assistance with the error encountered.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.