Ticket follow-ups and patterns
Next actions
Section titled “Next actions”Open a ticket and set what it is waiting for, an optional follow-up date, and an internal note. Waiting states can include tenant response, contractor action, a scheduled visit, or other follow-up.
Residents can see the waiting state. The reminder date and internal follow-up note remain staff-only. Clear or update the next action when work moves forward.
The Tickets page highlights missing, due, and overdue follow-ups. Stat cards and dashboard metrics open the matching filtered records in the current building scope.
Automatic pattern checks
Section titled “Automatic pattern checks”Sicket checks new and materially changed tickets in the background for recurring building issues. An actionable pattern can appear as a compact banner to landlords and organization admins.
Manual pattern scan
Section titled “Manual pattern scan”Use Detect pattern on the Tickets page for a deeper check of one building. If All Buildings is selected, choose which assigned building to scan.
Only one scan runs for a building at a time, and a cooldown prevents repeated scans. A scan never creates an incident, contractor case, email, or tenant notification automatically.
Review a pattern
Section titled “Review a pattern”Review the summary, confidence, date range, likely cause, and all related ticket previews. From the review you can:
- open a filtered Tickets page
- create an incident
- prepare and preview a contractor case
- download a temporary PDF report
- mark it handled
- mark it not a pattern
AI-assisted results can be wrong. Review the related reports before taking action.