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:
The status explains whether the message is due to send, has been sent or is too late to send.
The name of the Outbound message rule as displayed on the Outbound page.
All Outbound message rules have a unique ID. This ID is helpful for Uplisting customer support.
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.
The date and time the message was sent.
This row is only displayed if the message has been sent
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.
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
Updated about 1 month ago