Rental Delinquency Contact Attempt Log

A contact attempt log should establish what communication was authorized, sent, delivered, and answered. It should not characterize a resident or substitute for legal and policy review.

Quick Overview

Record the approved template or purpose, channel, destination reference, sent time, delivery state, response state, owner, and next action. Keep account details in the controlled system and expose only the minimum operational status.

Common Mistakes

Do not equate sending with delivery, silence with refusal, or a promise with payment. Avoid improvised language and repeated outreach outside approved timing. Never place sensitive balances or personal circumstances in a broadly visible queue.

Separate the communication states

Use discrete states for prepared, authorized, sent, delivered, failed, responded, and escalated. Link each status to the system event or note that supports it. Retain failed delivery evidence because it changes the next action.

Review the next action

At each review point, confirm that the action is allowed, proportionate, and assigned. Pause automation when a dispute, accommodation request, representation notice, or other protected circumstance requires specialist handling.

Common Questions Answered

Does a sent email prove notice was received?

No. Record the send event and delivery evidence separately, subject to the applicable process.

Should the log decide enforcement steps?

No. It supports an authorized workflow but does not decide legal remedies or deadlines.

Ready to use this routine

Pair it with the resident communication log and payment plan review queue. The CFPB provides public debt collection resources: review CFPB information.

Published September 2, 2026. Review one active queue and remove any field that exposes more information than the handoff needs.