From the Campus Operations edition of November 7, 2026
Runshaw College's IT head reports AI-assisted ticket triage at about 95% accuracy through a September peak of 3,240 tickets, with every result human-reviewed
Runshaw College (UK further education), IT Services · Further education IT service management · United Kingdom (Lancashire, England)
- Publisher
- Service Desk Institute
- Original publication
- 22 October 2026 (Service Desk Institute resource)
- Source retrieved
- 2026-11-08
What happened
Alex Harding, Head of IT Services, reports that in September 2026 the service desk handled 3,240 tickets, 23% more than the previous September, with average triage time of 7.89 minutes, 99.88% triaged within target and CSAT of 4.99/5. An IT Services agent, 'Bobbie', built on Microsoft Copilot capability and Jira Automation, suggests category, assignment, title and summary; it was trained on a year of previous tickets and is reported at around 95% accuracy. Every result is human-reviewed and team leaders control the rules. Time released was described as equivalent to about two staff, without removing people. Bobbie also reviews proposed changes before the Change Advisory Board, and AI-assisted problem management clusters incidents every few hours for the team to decide on action.
Why it matters
Directly transferable pattern for campus IT service desks facing start-of-term peaks: AI suggests triage fields inside the existing ITSM tool, humans confirm, and gains are framed as released capacity rather than headcount reduction.
Evidence and measured results
Self-reported operational metrics from the institution's IT head; no baseline triage time, no accuracy method, no independent audit. Published on the Service Desk Institute site (an industry body that also audits the college's service desk).
Limitations and uncertainty
Single institution, self-reported and published by an industry body with an audit relationship; '95% accuracy' and 'two staff' equivalence are not methodologically explained; incident-ratio improvement since 2016/17 has several contributors.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Start-of-term ticket peaks overwhelm triage capacity on small college service desks.
- Stakeholders
- Head of IT Services
- Service desk team leaders
- CIO/IT director
- Student services leads
- Discovery questions
- What share of desk time goes to categorising and assigning tickets?
- Do you have a year of reliably labelled tickets?
- Which AI capabilities are already licensed in your ITSM and productivity suite?
- Value hypothesis
- AI-suggested triage may release desk capacity during peaks; Runshaw reports about two staff-equivalents but no monetary saving.
- Potential engagement
- A one-term shadow-then-assist triage pilot in the existing ITSM tool with human review.
- Unsupported claims
- Guaranteed headcount or cost savings
- 95% accuracy on another institution's tickets
- Autonomous ticket resolution
Pre-sales engineering
Role takeaway
- Fit
- Colleges with a mature ITSM tool, consistent categories and Copilot or equivalent automation already licensed.
- Architecture and integration
- Classifier suggests category, assignee, title and summary via ITSM automation; results written to ticket fields; problem clusters posted to a collaboration channel.
- Prerequisites
- Labelled historical tickets
- Stable service catalogue categories
- ITSM automation and API access
- Constraints
- Estate-specific Microsoft/Atlassian build
- No published accuracy method
- UK FE context
- Security
- Review personal data in historical tickets used for training and restrict access to model outputs and logs.
- Proof of value
- Per-category accuracy versus human final routing
- Override rate during shadow period
- Triage time before and after on a comparable peak
Delivery
Role takeaway
- Work
- Configure suggestion-mode triage, run a shadow period, then enable assisted triage with leader-owned rules and reporting.
- Dependencies
- ITSM admin access
- Clean category taxonomy
- Desk staff time for review
- Ownership
- Service desk team leaders own rules; Head of IT Services owns outcomes.
- Skills and adoption
- Train agents to review and correct suggestions and feed corrections back.
- Governance checkpoints
- Data protection review of training tickets
- Go/no-go after shadow accuracy review
- Termly review of override and error rates
- Acceptance criteria
- Proposed: at least 90% suggestion acceptance on in-scope categories in shadow mode
- Proposed: triage-within-target rate maintained at peak
- Proposed: no reduction in satisfaction score
- Risks
- Automation complacency in human review
- Drift when categories change
- Overstated savings claims
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Agent built from existing Microsoft Copilot, Jira Automation and Microsoft Foundry AI within the current estate; writes suggested fields back into Jira; problem clustering routes summaries to a Teams channel.
Governance
Who approves, reviews and stays accountable for outcomes?
College AI guardrails applied; team leaders own triage rules; AI does not decide root cause or raise Problem records. Mapped to SDI Global Best Practice Standard v9 Concept 10.
Security and privacy
What data, permissions and controls need testing?
Model trained on a year of historical tickets, which can contain personal data; the article does not describe data minimisation, retention or access controls.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Explicitly positions AI as releasing time for customer work during peak demand rather than reducing staff.
Procurement
What should contracts, pricing and exit terms secure?
Uses capabilities already within the Microsoft and Atlassian estate rather than a new point product.
Operating model
Which teams own the service once it runs?
Human-in-the-loop triage with leader-owned rules, scheduled problem-cluster reviews and pre-CAB change review shifts staff time from sorting to resolution.
Publication history
- 2026-11-07Campus Operations · Issue 604 resources
Stable resource ID: runshaw-college-bobbie-ai-ticket-triage-september-peak-20261022