Skip to content

Resident Relations research

Resident portal message audits: a method note

A method note on auditing resident portal messages, covering the response record, the review cadence, and the limits of a message audit.

| 3 sources sources

Resident portal message audits: a method note
Table of contents

A resident sends three messages through the portal in a week and receives one automated reply. The portal reports a response on every message. The resident calls the office to ask whether anyone read them.

A portal message audit checks whether the messages were answered by a person and whether the issue moved. This method note describes what to record and what the audit cannot prove.

The message record

The portal usually stores the message, the sender, the timestamp, and the reply. The audit should add the owner and the resolution state.

Without the owner, a message can sit in a shared inbox that everyone can see and no one owns. The record should show who is responsible.

Separate the reply types

Classify each reply as automated, human acknowledgement, or substantive response. An automated reply is not a response to the resident's question.

Record the type and the time. The classification turns a misleading "100 percent responded" into a useful picture.

What the audit can show

The audit can show whether messages received a human reply and how quickly. It can show the topics that generate the most messages.

It can show whether the same issue is reported repeatedly. A repeat message is a sign that the first response did not resolve it.

What the audit cannot show

The audit cannot show whether the resident was satisfied. A polite reply can still leave the problem open.

It cannot show whether the message was understood. A reply that answers a different question is a response in the record and a failure in practice.

It also cannot show whether the issue was fixed. That needs the work order or the resolution note.

Methodology and limits

This note is an operating design informed by public guidance on internal control, housing standards, and small-business operations. It does not report an empirical study or establish a response standard.

The fields were tested against common messages: a repair request, a billing question, a noise complaint, and a document request. The design keeps the reply types and the resolution state distinct.

Draw a sample

Audit a fixed sample each month, plus every message that escalated. Record the rule so the sample is repeatable.

A convenience sample tends to pick the easy messages. The rule makes the audit defensible.

Record the resolution

For each sampled message, record whether the issue was resolved, pending, or referred. Add the owner and the date.

A message that is answered but not resolved is the most useful finding. It shows where the process stops.

A worked example

A sample of 30 messages finds 28 automated replies, 20 human acknowledgements, and 12 substantive responses. Six issues are still open after two weeks.

The finding is not a response problem; it is a resolution problem. The review focuses on the work orders behind the six open messages.

Automated replies

If the portal sends an automatic reply, label it as automatic in the audit. A resident who receives an automatic reply may believe no one has read the message.

Record the label and the time. The audit should be honest about what the resident experienced.

Escalations

Record the messages that were escalated and the time to escalation. A message that needed a manager should show that the route worked.

A slow escalation is a process finding. The audit should point to the step, not the person.

Topics and buildings

Group the messages by topic and by building. A cluster of repair messages in one building is a maintenance signal, not a portal problem.

Record the topic and the building. The pattern should point to the process that needs attention.

Sample size

A fixed sample of 25 to 30 messages a month is enough for a small property. Record the rule and the exception list.

A larger sample is not automatically better if it is not reviewed. The audit should fit the reviewer's time.

Reporting

Report the sample size, the reply types, the open items, and the topics. Add one recommendation.

Keep the report to one page. The detail stays in the portal and the work orders.

Review cadence

Audit monthly and review the pattern quarterly. The monthly pass catches the gaps; the quarterly pass looks at the topics and the buildings.

Keep the categories stable. A changing audit cannot be compared.

Privacy and tone

Messages contain personal information. Limit access and keep the notes factual.

A resident who feels monitored will stop using the portal. The audit is about the process, not about the resident.

Limits and appropriate use

This note is a method design, not an empirical study. It does not establish a response standard or a satisfaction measure. Results depend on the completeness of the portal record.

Small properties may not have a portal, and the audit should say so. The absence of a record is a finding about the channel.

Conclusion

A portal message audit shows whether messages received a human reply and whether the issue moved. It does not prove satisfaction or resolution. Used with a resolution field and a monthly sample, it turns a response metric into a service review.