Overview

DoorLoop's Communications feature allows you to send messages to your tenants via email, text, voice message, and posts to their tenant portal. The Communications Log allows you to check the status of these communications.

The Steps

Step 1

Navigate to Communications > Communications Log in the main navigation menu on the left side.

Step 2

Find the message you want to view. By default, the newest messages show up at the top of the list.

You can also sort the list by the various columns, or use filters and the search bar to narrow down the list.

  • Use the calendar filter to view messages from a certain time period.

  • Use the filter to the right of the calendar icon to filter by Status or Type. For example, you could filter to see all failed messages or all text messages.

  • Use the search bar to search by the subject for the message. For example, you could search for all rent reminders or a specific message you sent.

Step 3

After finding the message, you can review the recipient, the sent date, and the current status of the message.

The Status icons show the tenant's interaction with the announcement. For all messages, you can see if the send was successful. For emails, you can also see whether the recipient opened the message and if they clicked on a link to open their tenant portal.

Hovering over the open and clicked link icons gives you the time and date the tenant read or clicked the link in the email.

Step 4

If necessary, click on the message to review what it said. You can also click the three vertical dots on the right side of the message line and choose View.

You can delete the status record of the message by clicking the Delete button in the lower left corner. Keep in mind that this doesn't actually delete the message for the recipient, only the log of the message.

We don't recommend deleting these records as they aren't recoverable, but we understand that people might want to.

Now that you know how to use the Communications Log, feel free to review DoorLoop's Communication feature using this article.

Did this answer your question?