Release path
1.0.0Published Mar 4, 2026@pasar6987/hubspot-tickets
HubSpot CRM ticket dimensions and metrics — support pipeline, ticket status, priority, SLA compliance, response times, resolution rates, and customer satisfaction tracking.
Published package · Latest published 1.0.0 Mar 4, 2026 · 2 datasets / 10 measures in the latest review · Updated Mar 11, 2026
Publisher
@pasar6987Published Mar 4, 2026Structure snapshot
2 datasets10 measures · 25 dimensionsReference context
Secondary package facts stay compact
- Updated
- Mar 11, 2026
- Visibility
- Public hub listing
- License
- Apache-2.0
- Created
- Mar 4, 2026
Reference facts
Secondary package facts after the usage path is clear
Licensing, categorization, ownership, and linked metadata stay below the runnable path so the page reads in the right order.
Format
Upstream
Repository
Domain
Source
Owner
@pasar6987Organization
License
Visibility
Publisher
Latest published version
Tags
Schema preview
SDK handoff
Use this package in code and AI
After structure review, move straight into typed reads with load() or compact LLM context with to_prompt().
Python SDK
Python example for @pasar6987/hubspot-tickets
This example uses the current package ref and, when preview data is available, fills in real dataset names from the published summary.
import rawctx
model = rawctx.load("@pasar6987/hubspot-tickets")
prompt = rawctx.to_prompt(
"@pasar6987/hubspot-tickets",
datasets=["Ticket", "TicketSLA"],
max_tokens=2000,
)
print(model.datasets) # ["Ticket", "TicketSLA"]
print(model.measures) # [Measure(name="total_tickets", ...), Measure(name="new_tickets_created", ...), Measure(name="open_tickets", ...)]
print(model.dimensions) # [Dimension(name="ticket_id", ...), Dimension(name="subject", ...), Dimension(name="content", ...)]
print(model.relationships) # [Relationship(name='...', ...)]
print(prompt)README
Package narrative and examples
Use documentation after the package clears provenance, ownership, and runnable-path checks.
@pasar6987/hubspot-tickets
HubSpot Tickets — customer support and service operations tracking every inbound request from creation through resolution, with priority classification, channel attribution, SLA compliance monitoring, response time benchmarks, and resolution analytics that drive continuous improvement in customer service quality.
Overview
| Count | |
|---|---|
| Datasets | 2 |
| Dimensions | 25 |
| Metrics | 10 |
| Relationships | 1 |
Datasets
Ticket
Support ticket management — ticket subjects, descriptions, pipeline statuses, priorities, categories, owner assignments, source channels, creation and close dates, customer and agent reply timestamps, and conversation counts that track every support interaction.
- Dimensions: 17
- Metrics: 5
TicketSLA
Ticket SLA compliance and performance — first response times, time-to-close durations, SLA status indicators (on time, due soon, overdue), SLA due dates, and compliance tracking that ensure service level commitments are met.
- Dimensions: 8
- Metrics: 5
Metrics
- total_tickets — The total count of support ticket records in the CRM.
- new_tickets_created — The number of new support tickets created in a given time period.
- open_tickets — The count of tickets currently in an open (not closed) status.
- closed_tickets — The count of tickets that have been closed or resolved.
- tickets_by_priority — The distribution of tickets across priority levels (low, medium, high).
- average_time_to_first_response — The average elapsed time from ticket creation to the first agent response, in hours.
- average_time_to_close — The average elapsed time from ticket creation to resolution, in hours.
- sla_compliance_rate — The percentage of tickets resolved within the defined SLA targets.
- first_response_sla_met_rate — The percentage of tickets where the first response SLA target was met.
- customer_satisfaction_score — The average customer satisfaction rating collected from post-resolution surveys.
Install
rawctx snapshot-download @pasar6987/hubspot-tickets
Source
Structure review
Inspect package structure after the usage path is clear
Use the structural review when you need the package footprint, field counts, and model paths before a deeper explorer pass.
Topology
Semantic graph
Use the graph last, once provenance, documentation, and the runnable path are already clear.
Semantic Graph
Topology counts appear after the graph loads.
Loading graph
Semantic topology is still loadingCounts and graph nodes appear after the latest published summary has been fetched.
