Start with a useful description.
A request starts with a category and a description. A photo can help explain the problem, but it is optional. Owners can also record a complaint received by phone so the work does not disappear into a separate conversation.
Keep the request connected to the resident and the relevant property. Avoid putting private details from several residents into one shared update.
Say what happened and what comes next.
Bunkfox uses three request states: Open, In progress and Closed. The timeline carries the detail: the action taken, a delay, the person contacted and the next step.
“The plumber has been contacted; we are waiting for a visit time” explains more than a status change alone. It gives the resident context without promising a time that has not been confirmed.
Choose who an update is for.
An internal note helps the property team coordinate. A resident-visible update tells the resident what is happening. Keep these separate before posting.
When several reports concern one issue, owners can link the reports. The connection should help coordinate work while keeping each resident’s private records separate.
Close with a reason. Reopen if needed.
The owner closes the request with a reason explaining what was done. The resident can reopen the same ticket if the problem remains, so the earlier conversation stays available.
This is a record of the work, not a guarantee of response or repair time. Clear updates help people understand the current situation.