What it means
Read means someone viewed a message or conversation. Resolved means the issue was addressed against a closure criterion. These are independent states: opening a message can remove an alert but does not deliver a towel, fix a lock or confirm a refund.
Why it matters
The distinction makes pending work and shift handovers reliable. If the inbox clears simply because someone read a message, the next shift loses open needs. Closure should depend on an action and its verification rather than message state alone.
An example in practice
A guest requests a pillow. Reception reads the message and promises delivery. The issue remains pending while the team prepares it. It can close once delivery is confirmed under the property’s procedure. “We replied” does not establish that outcome.
A mistake to avoid
Treating archived, read and resolved as interchangeable across tools causes confusion. Systems may define these differently. Specify what changes when someone replies, what a new reply does and when an issue reopens.
Put it into practice
- Turn each outstanding promise into an action with an owner.
- Keep a target time and evidence of completion.
- Close against a shared criterion and reopen for a new need.
A common question
Does every conversation need a task?
No. An informative reply may answer a question immediately. Add follow-up when the answer depends on later work, another person or a check that has not happened yet.