Detect ticket patterns
What this guide helps you do
Section titled “What this guide helps you do”Find groups of related reports that may point to one recurring building problem.
Who can do this
Section titled “Who can do this”Organization admins and landlords on plans with pattern detection. Tenants and Observers never see pattern banners, scan controls, or pattern history.
Where to find it in Sicket
Section titled “Where to find it in Sicket”Go to Tickets, then use Detect pattern. When All Buildings is selected, choose the building to scan.
Before you start
Section titled “Before you start”Sicket automatically evaluates new or materially changed tickets in the background. The button starts a deeper check for the selected building. It does not automatically create an incident, contractor case, email, or tenant notification.
Step-by-step
Section titled “Step-by-step”- Open
Tickets. - Select the correct current scope.
- Choose
Detect pattern. - Wait for
Scanning tickets...to finish. - Open the compact banner when a shared-building pattern needs attention.
- Review the summary, confidence, date range, affected area, likely cause, and related tickets.
- Choose the appropriate action.
Field-by-field explanation
Section titled “Field-by-field explanation”Summary explains the repeated issue in plain language.
Pattern confidence is an estimate, not proof. Review lower-confidence results carefully.
Date range shows the first and latest related report. Tickets too far apart should not normally be treated as the same active pattern.
Related tickets always lists the reports counted for this pattern. Use View on Tickets page to close the modal and open a filtered ticket list.
Download PDF generates a temporary report when pressed. The PDF is returned immediately and is not stored as a persistent attachment.
Actions
Section titled “Actions”Create incident opens the incident workflow for coordinated resident and staff updates.
Create contractor case opens a prefilled contractor-sharing workflow. Preview it and choose exactly which ticket details the contractor may see.
Mark handled hides a pattern that no longer needs attention. Not a pattern rejects an incorrect match. A rejected pattern can return only after meaningful new independent evidence is added.
Closing the banner means Hide for me; another authorized staff user can still see it. It returns for you only when new evidence changes it.
What happens next
Section titled “What happens next”Staff can use patterns to communicate better, reduce duplicate work, create an incident, or prepare a contractor case. Multiple patterns remain available for review one at a time.
Common issues
Section titled “Common issues”Only one manual scan runs per building. A short cooldown prevents repeated scans and accidental provider costs. If a scan fails or is interrupted, Sicket stops it safely instead of repeatedly sending potentially billable requests.
Pattern detection uses minimized ticket evidence and does not send ticket codes or content to product analytics. See the in-app pattern-detection information page for the current privacy explanation.