Source
Ticketing, queues & SLA — found from sitemap — Freshdesk
Checked for Freshdesk on 5 Oct 2026
- Page
- https://support.freshworks.com/support/solutions/articles/50000011587-how-to-use-the-unresolved-tickets-metric-
- Checked
- 5 Oct 2026, 03:29 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:7adaa213c8254f574c6a02969a96306f803e3bccfb861cd54f990994bcd8e297
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Unresolved tickets metric Report an error
“The Unresolved Tickets metric displays all tickets that are still unresolved as of the end date of the chosen date range.”
-
Analytics date range required Report an error
“That’s why selecting a time period is mandatory for this metric.”
-
Underlying data latest status Report an error
“The underlying data always reflects the latest ticket status. If a ticket was unresolved at the end of the selected time period but got closed later, it will still appear in the underlying data as Closed.”
-
Grouping widget level only Report an error
“Grouping works only at the widget (visualization) level — for example, in line or bar charts. The underlying data view does not duplicate tickets across weeks or months.”
-
Analytics usage limits Report an error
“usage limits are implemented in Freshservice Analytics, especially on the reporting duration. These limits differ by plan type.”
Scores citing this record
- The Agent Advocate Ticketing, queues & SLA
- The Data Protection Officer Ticketing, queues & SLA
- The Shop Operator Ticketing, queues & SLA
- The Integrator Ticketing, queues & SLA
- The Skeptic Ticketing, queues & SLA
- The Support Lead Ticketing, queues & SLA