Outbound message logs

Introduction video

Rules will appear even if the message won't send due to the filters you have selected

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.

Outbound message logs breakdown

Each row on the message log table is explained on the table below:

Parameter

Description

Value

Status

The status explains whether the message is due to send, has been sent or is too late to send.

Sent is obvious, the message has been sent.

Pending means a message will send it if meets the criteria. Not all pending messages will send, this is expected. For example, if you create a message to send to bookings that haven't paid and this booking has been paid for. The message will display on the booking in a pending state but will not be sent.

Too late means the message will not send as it is past the sending window.

Pending, too late, sent.

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.

x
days/hours/minutes before/after
booking/arrival/departure

Due to send

The date and time the message is due to send.

August 11th 2022 @ 3:00 pm

Sent at

The date and time the message was sent.

This row is only displayed if the message has been sent

August 11th 2022 @ 3:00 pm

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.

August 12th 2022 @ 11:00 am

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

Reason not sent values

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

Expect booking#duration to be gt value (1)

The booking duration was not met.

This booking was not one day in length.

Expect booking#lead_time to be lt value (24)

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.

Expect booking_rental_agreement#successful? to be eq value (true)

The booking rental agreement has not been signed.

Expect security_deposit#successful? to be eq value (true)

Security deposit payment failed

Expect security_deposit#needs_payment_information? to be eq value (true).

The booking does not have a security deposit payment method.

Expect security_deposit#failed? to be eq value (true)

The deposit on this booking was captured successfully.

Expect guest_identity_verification#successful? to be eq value (false)

The guest has not verified their identity successfully.

FAQ's

Which Outbound messages appear on message logs?

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.

25162516

In this example, this message rule will appear in the message logs for all bookings on all properties except for the listing titled `Main.

I can't see an Outbound message on the log

There are two reasons you won't see an Outbound message on the log tab:

  1. The Outbound message is not enabled
  2. The property this booking is on has not been selected under the Outbound message rule

Did this page help you?