Resident Communication SLAs That Prevent Disputes

Most disputes are not about the leak. They are about silence after the leak was reported. An SLA is a promise of the next update, not a promise that the plumber is already in the driveway.

Write the times down. Staff and residents should see the same numbers.

The SLA board

Hang this in the office and put it in the portal. If you cannot staff it, do not publish it.

“We got it” without a next-update time is not an acknowledgment.

One official thread

Residents will still text. That is fine for a ping. It is not fine as the only history.

Rules that prevent reconstruction-from-memory:

• Every request becomes a ticket or a logged notice the same day
• Photos live on the ticket
• If you agree to something on the phone, you send a two-sentence confirmation in the portal

Payment and collections language should stay consistent with consumer-facing norms; the CFPB is a reasonable reference when you write reminder copy.

Templates you actually send

Four maintenance templates cover most volume. Keep them short.

Received: what you heard, what you still need (photo, access), when they will hear from you next.

Scheduled: window, how access works, what to do if they cannot be home.

Delayed: the honest reason, the next date you will write again. Do not say “soon.”

Complete: what was done, whether they should test something, how to reopen if it fails.

Add entry-notice, rent-reminder, and renewal templates so tone does not depend on who is on shift.

Welcome packet (one page)

Send it at move-in and store it where they can find it in month 11:

• How to submit maintenance and what counts as emergency
• Office hours and the SLA table above
• Rent methods, grace period, late fee (as written in the lease)
• Parking, trash, noise
• How to report move-in defects (give a deadline)

De-escalation without a script committee

Staff need two sentences they are allowed to use:

• “I understand why that’s a problem. I will update you by [time] with the next step.”
• “Here is what we can do by [date], and here is what we cannot do.”

Empathy without a date is another form of silence.

Weekly 15-minute audit

Pick five random threads. Check:

• Was the first response inside the SLA?
• Was the next-update time kept?
• Would a new PM understand the story from the ticket alone?

If three fail, you have a staffing or template problem, not a “soft skills” problem.

Unitz keeps the resident message, the work order, and the notice history on one timeline so the SLA is visible. If you want that board and the four templates set up on your portal, book a consultation.