Outbound message logs include all messages that could be sent. Don't be alarmed if you see several pending or failed messages, as that message may not be relevant. For example, a rule dependent on a deposit payment failing will appear here as pending even if the security deposit has not failed. The message could have been sent, but it wasn't, as the deposit had not failed.
Each row on the message log table is explained on the table below:
|Status||The status explains whether the message is due to send, has been sent or is too late to send.|
|Name||The name of the Outbound message rule as displayed on the Outbound page.|
|Rule ID||All Outbound message rules have a unique ID. This ID is helpful for Uplisting customer support.|
|Trigger||When the message is due to send. 1 day before arrival, for example.|
|Due to send||The date and time the message is due to send.|
|Sent at||The date and time the message was sent.|
This row is only displayed if the message has been sent
|Event time||The event trigger time.|
For example, if the message rule is scheduled to send one hour after arrival, the event time displays the arrival time on the booking.
|Reason not sent||This note explains why a message was not sent.|
This is only displayed when the status is 'too_late'.
|Values explained in the table below|
Messages may not be sent due to the booking not meeting your set filters. For example, if you require a rental agreement to be signed, which is not, then that message will not send.
A message may fail to send due to multiple reasons. Each reason will be displayed on the message log.
|Reason not sent output.||Reason not sent in friendly form|
|The booking duration was not met.|
This booking was not one day in length.
|Booking lead time not matched.|
In this example, the booking lead time is set to be over 24 hours. However, the booking was created only 16 hours before arrival.
|The booking rental agreement has not been signed.|
|Security deposit payment failed|
|The booking does not have a security deposit payment method.|
|The deposit on this booking was captured successfully.|
|The guest has not verified their identity successfully.|
|We attempted to deliver the message, but we don't have API access to the Airbnb account.|
|Booking.com rejected this message due to some word, phrase or link in the message.|
Unfortunately, Booking.com don't provide a list of words, phrases or links that trigger an error like this.
From experience we know Booking.com don't like the words
If it's not clear why Booking.com blocks the message please reach out to them direcltly.
|Sending messages requires full Airbnb account access.|
|Airbnb rejected the message without specifying a reason.|
|No email address on the booking.|
Add a guest email address to send messages.
|No specific error was provided, please get in touch with support.|
If a property is selected on an Outbound message rule, that message rule will be displayed on the message logs tab for all bookings on that property.
There are two reasons you won't see an Outbound message on the log tab:
- The Outbound message is not enabled
- The property this booking is on has not been selected under the Outbound message rule
On 14th December 22 we pushed a frequently asked for feature; the ability to toggle on and off scheduled messages per booking.
If you need to turn off a particular automated message for a guest,
- Click on to your Calendar view
- Find the relevant Booking & click to open the detail page
- Click "Logs"
- Scroll to the relevant message & click the Toggle to the left of the Message Title
Once the message is turned off the Status will show as Disabled.
Updated about 2 months ago