KCS @ YORK

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

Today

Individual expertise

With KCS

Shared knowledge

03Knowledge in ticket work

The agent Solve Loop

Agent Solve Loop ticket flowReview the ticket and search for knowledge. If an article exists, reuse it, check accuracy, and improve or flag gaps. If no article exists, investigate, capture and create. Link useful knowledge to the ticket. If the requester can self-solve, share suitable guidance; otherwise continue agent-led resolution. Confirm the outcome and resolve. Reviewticket Searchknowledge Relevantarticle exists? Reusethe answer Accurate andcomplete? Improveor flag Investigate,capture and create Link articleto ticket Can requesterself-solve? Share suitableguidance Continue agent-ledresolution Confirm outcomeand resolve YesNoYesNoYesNo

04November 2026

Launch access

All Halo agents

Search, reuse
share and link

Search available knowledge.
See ticket suggestions

Onboarded pilot participants

Create and improve

SSB / OUR / CTS / CS

Training + authoring permissions

05York’s rollout

Rollout roadmap

Launch + pilot

Launch KB module & begin the pilot

All agents: reuse knowledgeOnboarded pilot agents: create and update knowledge

Launch preparation complete

Workflow + draft standard + pilot onboarding information + live training

06Communications & rollout resources

Rollout communications

Launch communications

  • Pilot manager briefing

    Before participant invitations

    Protect training and coaching time

  • All-agent announcement

    4 November

    Explain launch access and authoring boundaries

  • Pilot invitation

    Before training and launch

    Set responsibilities; invite training and feedback

Supporting websites

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.4

Shared standard

KCS combines structured knowledge with collective ownership and review during reuse

KCS principles and core concepts

Knowledge Council

KCS evaluates outcomes, observed practice and content quality together

Measure the right things · 7.1

What 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 wantHow 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

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

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

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

The detail behind the signals

Are agents searching for knowledge? Every search helps us understand adoption, support coaching and identify knowledge gaps

01 / WHO

Who is searching?

Participation by agent and team shows which members and teams are making search part of their workflow

We can run reports showing KB searches and identify which agents may benefit from coaching/training to increase the “search early and often” practice

02 / HOW OFTEN

Search frequency

Evidence of repeat searching, especially when multiple searches are performed for the same subject in a short window, can indicate agents are refining their searches as they learn more. It can also indicate difficulty finding relevant knowledge

03 / WHAT

Search terms

Recurring questions and customer language reveal context-aware searching and can show demand. Search terms can be compared against existing knowledge from Day 1, and increasingly as knowledge matures, to identify knowledge gaps. Mine these terms to improve article titles, tags and search metadata, and identify opportunities to create relevant articles

15Search signals · Interpretation

One signal, two possible stories

Fewer searches need context

A habit may be slipping
Search FallingTickets Steady

Investigate & coach

Check team patterns and agent feedback

Discovery may be improving
Search FallingReuse Rising

Check suggestions

Useful answers may be arriving earlier

Read search alongside demand, discovery and reuse

First 90 days Establish a baseline. Learn. Improve

The detail behind the signals

01 / ACTION

What we do with the data

Monitor KB search activity to ensure agents are looking for knowledge in the course of their work. If we start seeing an activity drop at odds with ticket volume, especially from multiple agents on the same team, we should investigate whether the practice is waning and reinforcement is needed

Individual searching habits can also be compared against reuse and creation activities to help assess process alignment

02 / HYPOTHESIS

Hypothesis

Search volume is a signal that needs to be assessed alongside ticket demand, results and agent feedback. As our process improves and knowledge matures, manual searching may go down as auto-suggestions become more accurate, while knowledge discovery and reuse remain strong

16All agents · Knowledge reuse

A link is only as good as its match

Ticket

The problem
or request

Relevant knowledge

The solution
or fulfilment steps

✓
A linked article that doesn’t help×
Linkage rateHow widely is knowledge reused?
&
Sampled accuracyDoes the article support the resolution?

First 90 days Establish a baseline. Learn. Improve

The detail behind the signals

Is the right knowledge being reused? Ticket–article links help demonstrate that existing knowledge is being used to resolve real problems. Link the solution to the problem, or the fulfillment steps to the request

01 / MEASURE

Measure reuse

Report on which tickets are resolved with linked knowledge. We expect the share of applicable tickets with linked knowledge to increase as we generate more relevant knowledge articles, while accounting for the types of tickets we handle

02 / VERIFY

Check the connection

Linkage alone is not an indicator of good practice. We need to sample linked tickets to ensure that the right knowledge is being linked. Does the article match the issue and support the resolution? It’s easy to click a button to show false adherence

We can also compare linkage with searching and ticket context to identify patterns worth reviewing, rather than assuming someone linked without looking

17Linkage signals · Action

No link? Find out why

Unlinked ticket
01

Not applicable

Knowledge would not help this ticket

No link needed
02

Hard to find

A useful answer exists but is missed

Improve findability
03

Knowledge gap

The answer is missing or incomplete

Capture & improve

Recurring demand sets priorities. Sampled practice guides coaching

First 90 days Establish a baseline. Learn. Improve

The detail behind the signals

03 / INVESTIGATE

Learn from missing links

As our knowledge expands, the percentage of applicable tickets without links should decrease. We can start analyzing unlinked resolutions to identify true knowledge gaps or evidence of poor practice. Why was there no linkage: was it a case where knowledge wouldn’t apply, was the knowledge poorly created and hard to find, or was it absent altogether?

04 / IMPROVE

Act on the evidence

Coach agents whose linkage rates and sampled accuracy suggest they need support. Improve articles with low linkage rates compared with the volume of related tickets. Prioritize gaps based on recurring, unlinked demand

Success means relevant, accurate reuse.

We must pair linkage rate with linkage accuracy. A higher rate alone can reward the wrong behaviour

18All agents · First 90 days

KPIs for KCS: Article feedback

Read ratings alongside response volume and reuse

First 90 days Establish a baseline. Learn. Improve

The detail behind the signals

What we measure

Use Halo’s article upvotes and downvotes to track positive and negative feedback by article and over time. Review the number of ratings as well as the balance between likes and dislikes. A few responses provide a limited view; no ratings do not mean an article is poor

What the feedback tells us

Likes suggest that readers found an article useful. Dislikes identify articles worth investigating for missing steps, unclear wording, outdated guidance or a mismatch with the reader’s issue. Ratings are signals for review, rather than proof of accuracy or successful resolution

How we act

Read feedback alongside article views, ticket reuse and available comments or ticket context. Ask the content owner to investigate patterns, improve the article where needed, then check whether later feedback and reuse suggest the change helped. Use repeated patterns to prioritize content improvements and coaching

19Pilot knowledge workers · Process Alignment Review

Getting up to PAR ⚑

A coach-led review of real work, followed by an agreed improvement

The payoffTargeted coachingBetter knowledgeEvidence to scale

01 / Sample

Select a small, representative sample of completed tickets and their articles

Start with five tickets monthly. Use reliable ticket, search and article data

02 / Review

Check search, relevant reuse, capture, improvement and creation against a shared checklist

Record aligned, needing coaching or not applicable. Assess article quality separately against the Content Standard

03 / Coach

Discuss unclear decisions, identify workflow barriers and agree a practical improvement together

Allow 20–30 minutes for the coaching conversation

04 / Follow up

Revisit the agreed action at the next review. Use recurring findings to improve knowledge, training and support

Consistent sampling, clear definitions and calibrated reviews make trends trustworthy

20Questions before expansion

Questions for discussion

Leadership question / 01

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

KCS AT YORK / OUR KNOWLEDGE PROGRAM

Briefing sections

Choose a section. Explore at your own pace.

← → navigate sections Esc closes this window
MADE TO BE EXPLORED

Presentation controls

← →
Previous / next slide
Space
Next slide
PgUp PgDn
Presentation remote navigation
M
Open section overview
F
Toggle fullscreen
R
Toggle reading view
P
Print the slides
Home End
First / last section

Tab moves between controls. Arrow keys move within tab groups.