Format
OSI
Registry packagePublic
@rawctx/zendesk-tickets
Zendesk ticket dimensions and volume metrics — statuses, priorities, types, channels, tags, assignments, and timeline tracking for the complete ticket lifecycle.
OSISchema 1.0Domain customer-supportSource developer.zendesk.comOwner @pasar6987
Native (downloadable) · Latest 1.0.0 published Mar 4, 2026 · 4 datasets / 10 measures in the latest preview · Updated Mar 10, 2026
Snapshot
Registry facts before deep inspection
Format, origin, ownership, and release context surface first so the package can be qualified quickly.
Latest release
1.0.0Published Mar 4, 2026
Origin
Native (downloadable)Managed directly in rawctx
Installability
DownloadableDirect rawctx snapshot download
Domain
customer-support
Source
Owner
@pasar6987Organization
Independent
Repository
Not linked
License
Apache-2.0
Visibility
Public
Tags
Schema preview
OSI 1.0
Model preview
Structure before documentation
Preview the package footprint first, then open the dedicated explorer if you need field-level inspection.
models/zendesk-tickets.osi.yamlAI context included
4 datasets10 measures31 dimensions3 relationships
README
Package narrative and examples
Use documentation after the package qualifies on source, preview, and installability.
@rawctx/zendesk-tickets
Zendesk Ticket Core — the central hub of customer support capturing every inbound request with its lifecycle status, priority escalation path, type classification, channel origin, tag taxonomy, assignment routing, and temporal progression from creation through resolution.
Overview
| Count | |
|---|---|
| Datasets | 4 |
| Dimensions | 31 |
| Metrics | 10 |
| Relationships | 3 |
Datasets
Ticket
The heart of Zendesk Support — every customer request, question, problem report, and task represented as a ticket with its lifecycle status, urgency classification, type categorization, channel origin, brand context, and form configuration.
- Dimensions: 14
- Metrics: 10
TicketTags
Tag associations applied to tickets for flexible categorization, intelligent routing, and topic-based filtering that extends beyond structured ticket fields.
- Dimensions: 2
- Metrics: 0
TicketAssignment
The routing and ownership context of each ticket — who requested help, who submitted it, which agent owns it, which group handles it, and how many collaborators and followers are engaged.
- Dimensions: 7
- Metrics: 0
TicketTimeline
Critical milestone timestamps in the ticket lifecycle — from creation through first assignment, status changes, latest activity, and final resolution, enabling time-based cohort analysis and aging reports.
- Dimensions: 8
- Metrics: 0
Metrics
- ticket_count — Total number of tickets created in the selected period
- new_ticket_count — Number of tickets currently in new status awaiting initial triage
- open_ticket_count — Number of tickets in open status actively being worked on by agents
- pending_ticket_count — Number of tickets in pending status waiting for customer response
- hold_ticket_count — Number of tickets placed on hold awaiting internal action or third-party input
- solved_ticket_count — Number of tickets that have been resolved by agents
- closed_ticket_count — Number of tickets that have been permanently closed and archived
- backlog_ticket_count — Number of unsolved tickets in the backlog (new + open + pending + hold)
- escalated_ticket_count — Number of tickets that were escalated to higher-tier support or management
- reopened_ticket_count — Number of tickets that were reopened after being solved
Install
rawctx snapshot-download @rawctx/zendesk-tickets
Source
Topology
Semantic graph
Use the graph last, once the package has already qualified on release state, preview, and documentation.
Semantic Graph
Datasets 0 / Measures 0 / Dimensions 0 / Relationships 0
Loading semantic graph...
PackageDatasetMeasureDimensionRelationship