Skip to scenario
Back to the business caseKnowledge hub search · Implementation

Clarify, retrieve, and connect the right work

The hub needs both a useful retrieval corpus and an explicit way to handle missing scope. Source citations must support the answer rather than merely point to related pages.

Follow the process
Business goal
Increase efficiency
Business metric
Cost to serve

Follow a question through the hub

Establish a maintained corpus, consistent edition and role facets, and an evaluation set. Preserve the user’s access rights throughout retrieval.

The task in this example

How do I add a second site to a customer’s system?

  1. Step 1

    Receive the question

    The hub records the request and available context.

    System

    The search experience passes the query and permitted scope to retrieval.

  2. Step 2

    Interpret terms

    Map “second site” to the multi-site feature.

    Taxonomy

    Maintain requester language alongside approved feature names.

  3. Step 3

    Retrieve candidate topics

    Find maintained tasks and supporting know-how.

    Content team

    Topics must state the task they answer and retain necessary prerequisites.

  4. Step 4

    Establish edition and version

    Use supplied context or ask a clarifying question.

    Taxonomy

    Facets identify what is missing and prevent mixed-edition answers.

  5. Step 5

    Connect tasks and roles

    Follow the scoped feature to the work and permissions involved.

    Ontology and knowledge graph

    Typed relationships identify the task set rather than relying on page similarity alone.

  6. Step 6

    Generate with evidence

    Present scoped instructions and their supporting topics.

    Model

    The answer must preserve source scope and avoid filling gaps with unsupported steps.

  7. Step 7

    Apply and report gaps

    The account manager checks the sources and proceeds.

    People

    Capture unresolved questions and misleading answers for review by the relevant content or system owner.

This framework provides a practical baseline shaped by experience. Every organization operates under distinct technical and operational realities that require tailored design and governance. While you can adapt these measures independently, we frequently partner with teams to customize governance, integrations, and rollout. Performance outcomes will naturally vary.

Why these content layers matter

Intelligent content

Move maintained support know-how into self-contained task topics with sources and review ownership.

Taxonomy

Classify edition, version, role, and feature consistently. Those facets also identify the clarifying question to ask.

Ontology and knowledge graph

Connect a feature to its tasks and required roles across topics so retrieval can assemble a complete scoped answer.

Verify the result and handle exceptions

Score simple, ambiguous, and cross-topic questions. Check that every citation supports the associated instruction and that access filters remain in force.

If scope cannot be established, ask before presenting edition-specific actions. If related tasks are missing or contradictory, expose the gap and route it to the owner.

How we work
with your team

We can guide your team, work alongside it, or deliver the work for you. Combine these approaches as your needs and capacity change.

Lead

Build capability

We guide your people through the work, building capability that stays with your team.

Support

Add specialist backup

Your team owns the work. We provide experienced backup and specialist help where you need it.

Do

Delegate delivery

We handle work that is one-time, specialized, or outside your core business, without adding an ongoing burden to your team.

Which questions still send your team out of the hub?

Intuitive Stack can help structure support knowledge, define useful scope facets, and connect the tasks needed for answers staff can verify.