Knowledge is
coming to Halo
November 2026
KCS
Solve and Evolve
Use knowledge in each ticket. Improve the system through shared learning
02Our purpose
Why share knowledge
Make service knowledge available in ticket work so our community gets consistent help, agents avoid repeat investigation and York retains what its teams learn
Individual expertise
Shared knowledge
03Knowledge in ticket work
The agent Solve Loop
04November 2026
Launch access
Search, reuse
share and link
Search available knowledge.
See ticket suggestions
Create and improve
SSB / OUR / CTS / CS
Training + authoring permissions
05York’s rollout
Rollout roadmap
Launch KB module & begin the pilot
All agents: reuse knowledgeOnboarded pilot agents: create and update knowledge
Workflow + draft standard + pilot onboarding information + live training
06Communications & rollout resources
Rollout communications
Launch communications
Pilot manager briefing
Before participant invitationsProtect training and coaching time
All-agent announcement
4 NovemberExplain launch access and authoring boundaries
Pilot invitation
Before training and launchSet responsibilities; invite training and feedback
Supporting websites
- KB project page yorku.ca/uit/cio/opex/kb/
Announce the change & the tool
- KCS @ York yorku.ca/uit/cio/opex/kb/kcs
Explain the methodology
- Pilot Hub yorku.ca/uit/cio/opex/kb/pilots
Prepare our pilots
07Practical support for pilot testing
Pilot hypercare
Led by staff trained in KCS v6 Fundamentals and Practitioner practices
- Live & asynchronous KCS training for pilot participants
- Live sessions and self-paced training covering the Halo workflow and KCS practice
- Coaching during real work
- In-person and virtual drop-in coaching for individual agents and teams. Work through actual tickets to understand the practice, build the habit, identify which tickets need knowledge, and learn techniques for creating it efficiently and consistently
- Weekly open drop-ins
- Weekly virtual stand-ups for anyone with questions or feedback. Participation will help identify candidates to become coaches or join the KCS Council
- Urgent questions and help
- Our pilot lead will create and monitor the Knowledge Workers @ York Teams chat for urgent questions and requests for help
08Interactive illustration
Expected knowledge effort to value over time
09Our knowledge program
Committing to future success
Coaching
- Coach with real tickets
- Develop judgement and proficiency
- Reinforce search, reuse and improvement
Council
- Bring frontline evidence together
- Co-create our shared content standard
- Remove cross-team workflow barriers
Support active participation
Let’s protect time for our teams to participate in our knowledge program and co-create our shared content standard
10KCS practice evidence
Why these supports matter
Coaching
KCS links contribution rights to demonstrated proficiency, supported by coaching
Roles and proficiency · 6.4Shared standard
KCS combines structured knowledge with collective ownership and review during reuse
KCS principles and core conceptsKnowledge Council
KCS evaluates outcomes, observed practice and content quality together
Measure the right things · 7.1What this means for us
Practise with real tickets and feedback before expanding authoring
Agree a usable article structure, then improve it through real work
Our council can use that evidence to fix shared gaps and workflow barriers
11Behaviours and recognition
Celebrate knowledge work
| Behaviours we want | How we recognise them |
|---|---|
| Search and reuse Build on relevant knowledge before creating more | Recognise it Highlight an answer that helped resolve a request |
| Improve and capture Fix gaps and keep reusable learning from tickets | Recognise it Thank the people who made an answer clearer or more useful |
| Coach and collaborate Help others learn and share expertise across teams | Recognise it Celebrate coaching and teamwork in our team updates |
| Co-create our standard Bring examples, test guidance and suggest improvements | Recognise it Show teams how their feedback changed our shared standard |
Let’s recognise and celebrate these behaviours
In team meetings and one-to-ones, name the contribution, explain its impact and thank the people involved. Recognise useful work without article quotas or leaderboards
12Expected benefits
Who benefits
Immediate
Launch + pilot
Resolutions in tickets
Share suitable steps in one click
Short term
Winter/spring 2027
Consistent resolutions
Shared knowledge improves practice and resolution
Long term
Summer 2027 onward
Self-service portal
Our best knowledge, available for self-service
13Three aims for our knowledge program
What success looks like
01
Better support
Does knowledge help resolve the issue?
Evidence to review
- Known-issue resolutions
- Relevant reuse
- Requester experience
What we do with it
Improve answers and workflows that do not help
02
Healthy knowledge
Can people find and trust the answer?
Evidence to review
- Failed searches and feedback
- Relevance, duplication and gaps
- Audience and service accuracy
What we do with it
Prioritise knowledge people need and use
03
Sustainable adoption
Is the practice becoming part of the work?
Evidence to review
- Search and contribution in practice
- Coaching needs and workflow friction
- Team readiness and coach capacity
What we do with it
Continue, adjust or expand based on evidence and capacity
14All agents · First 90 days
KPIs for KCS: Searching
Search
The first adoption signal
Who?
KB searches reported by agent & team
How often?
Habits, frequency & repeat searches
What?
Mine customer terms & knowledge gaps
Improve titles, tags & search metadata. Identify articles to create
First 90 days Establish a baseline. Learn. Improve
15Search signals · Interpretation
One signal, two possible stories
Fewer searches need context
Investigate & coach
Check team patterns and agent feedback
Check suggestions
Useful answers may be arriving earlier
Read search alongside demand, discovery and reuse
First 90 days Establish a baseline. Learn. Improve
16All agents · Knowledge reuse
A link is only as good as its match
The problem
or request
The solution
or fulfilment steps
First 90 days Establish a baseline. Learn. Improve
17Linkage signals · Action
No link? Find out why
Not applicable
Knowledge would not help this ticket
No link neededHard to find
A useful answer exists but is missed
Improve findabilityKnowledge gap
The answer is missing or incomplete
Capture & improveRecurring demand sets priorities. Sampled practice guides coaching
First 90 days Establish a baseline. Learn. Improve
18All agents · First 90 days
KPIs for KCS: Article feedback
Likes
What’s working?
Dislikes
What needs attention?
Read ratings alongside response volume and reuse
First 90 days Establish a baseline. Learn. Improve
19Pilot knowledge workers · Process Alignment Review
Getting up to PAR ⚑
A coach-led review of real work, followed by an agreed improvement
20Questions before expansion
Questions for discussion
Is this extra work?
We’ll need time to learn and practise during the pilot. Our aim is to reduce repeat investigation while building and maintaining shared service knowledge
The University of Copenhagen reported about a 70% reduction in average resolution time over three years