Ownership Lens

Inspiration

Service tickets are often routed using categories, static rules, or round-robin assignment. When ticket information is incomplete or ownership documentation is outdated, tickets can move between multiple teams before reaching the right resolver. We wanted to explore whether historical resolution patterns could provide stronger evidence for service ownership and routing decisions.

What it does

Ownership Lens aka Resolver Compass analyzes historical ticket resolution patterns and compares them with documented ownership information. It identifies possible ownership drift, recommends the most appropriate resolver group, provides an explainable confidence score, and presents the supporting evidence for human review before any action is taken.

How we built it

We designed an interactive workflow that combines ticket context, historical resolved-ticket data, and approved knowledge sources. The solution evaluates signals such as similar-ticket patterns, final resolver frequency, reassignment history, resolution performance, source freshness, and knowledge agreement to produce an evidence-backed recommendation.

Challenges we ran into

The biggest challenges were dealing with missing or incorrect ticket categories, tickets moving across multiple groups, noisy historical data, outdated ownership documentation, small sample sizes, and ensuring that every recommendation remained explainable and governed rather than automatically changing production routing.

Accomplishments that we're proud of

We created an end-to-end experience that detects ownership drift, shows the operational evidence behind a recommendation, calculates confidence, and provides a governed review workflow where recommendations can be accepted, deferred, or rejected.

What we learned

We learned that the team initially assigned to a ticket is not always the team that truly owns the issue. Historical resolution activity can reveal valuable operational ownership signals, but confidence, data quality, sample size, and human governance are essential when turning those signals into recommendations.

What's next for Ownership Lens / Resolver Compass

Next, Ownership Lens could integrate more deeply with service-management workflows and knowledge systems, continuously evaluate ownership health, learn from reviewer decisions, and eventually support smarter assignment within an approved resolver group using workload, expertise, availability, and existing routing policies.

Built With

• ai
• mcp
• python