Knowledge is the shared foundation under the entire Popscale platform.

Popscale · Knowledge

The customer interaction is only as good as the knowledge behind it.

Popscale Knowledge collects the knowledge customer-facing teams need to be able to use – products, services, processes, ways of working, customer situations and quality criteria – as a reviewed, versioned foundation for training and assessment.

Your knowledge, reviewed · Versioned with sources · The foundation for training and Assessments

Example of a knowledge object

The object

Knowledge object: Returns and exchanges – how we handle them
Type: Process · tagged for customer service and checkout
Status: Active · version 3 · reviewed and approved
Sources: The service handbook · linked excerpts from the source document

When it changes

The change: Version 3 → 4: the return window changes and a new exception is added. The difference is summarized automatically.
Affected content: Training content that builds on the object is flagged for review – with a summary of what differs.
The action: You decide item by item: confirm that the content still holds, or mark it as needing an update.

The boundary.

Knowledge is not a new intranet.

Most organizations already have documents: product sheets, handbooks, presentations, process descriptions, policies. What Popscale needs is not a copy of everything the company knows. It needs the knowledge that should be able to:

Be explained to the customerBe used in a customer interactionBe trained in a JourneyBe assessed in an AssessmentServe as the basis for the AI's feedbackStay current as the business changes

Knowledge is the part of your organization’s knowledge that needs to become usable in and around the customer interaction.

What goes in.

Knowledge is more than product facts.

What decides a customer interaction is rarely just what a product is called or what it costs. Employees may also need to understand:

Products and services

What do we offer, for whom, and on what terms?

Processes

What happens when something deviates from the standard flow?

Methods

How do we want needs, advice, service and follow-up to be handled?

Customer questions and objections

What keeps coming up – and what knowledge needs to be there when the question comes?

Quality criteria

What characterizes a good customer interaction or a correct answer in this exact situation?

Experience-based knowledge

What do experienced employees do that isn't written down anywhere yet?

In Popscale, it is structured as distinct objects:

Product factsProcessesPlaybooksFrequently asked questions and answersObjectionsPolicies and guidelinesCustomer profilesReal casesTalk tracksChecklists

That makes Knowledge more useful as a foundation for capability than as yet another document archive.

How it works.

From scattered sources to a reviewed foundation.

Collect the knowledge

Import documents you already have, write directly, or use material from a Study when knowledge lives with people rather than in files.

Structure it

The knowledge is broken into distinct objects – for example a product, process, objection, advisory principle or playbook – with relevant tags and source links.

Review and approve

New versions can be reviewed before they become active. Drafts should not be mixed up with approved knowledge.

Use it as the foundation

Active knowledge can be used when Episodes, Coaching, Roleplays, Journeys and Assessments are built.

Keep it alive

When an object changes, content that builds on that knowledge can be identified for review.

Popscale flags. You decide what needs to change.

When the knowledge changes.

So does the next customer interaction.

A price is adjusted. A term changes. A campaign starts. A new product launches. A complaints process is updated. A new way of working is introduced. The hard part isn’t just updating the document – it’s understanding where the old knowledge is already in use.

With Knowledge, a change can become visible in relation to the training content that builds on the object, so your organization can decide what still holds and what needs a second look.

A shorter path from changed knowledge to a team that can handle the next customer interaction.

Where the knowledge comes from.

The most important things aren’t always in the documents.

Some of the most valuable principles live with people. An experienced advisor knows which questions quickly separate two customer needs. A store manager knows what tends to go wrong when a campaign launches. A technician knows which explanation helps the customer understand why a job turned out bigger. A receptionist knows which handover often creates friction in the guest journey.

It can be captured through a Study where experienced employees are interviewed about a concrete customer moment. After review, the relevant parts can become structured Knowledge.

Understanding becomes knowledge. Knowledge becomes training.

The same knowledge can do several jobs.

One source. Several ways to make the knowledge usable.

An approved knowledge object doesn’t have to be used just once. Example: a new membership. Knowledge can describe prices, terms, target groups, differences from existing options, common questions and relevant advisory principles. The same foundation can then be used to:

Episode: Explain what's new.
Flashcards: Repeat the facts.
Coaching: Practice explaining or reasoning.
Roleplay: Let the employee use the knowledge with an AI customer.
Assessment: Assess whether the employee can recall and explain what needs to stick.

The control is yours.

You decide what the AI gets to build on.

The knowledge comes from you: Training and Assessments should build on what you have entered and approved about your business.
Versions with traceable sources: Objects can carry history and source links, so it's possible to understand where a statement comes from.
Review before use: New versions can be reviewed before they become active.
Popscale doesn't decide what's true about your business: The AI can help structure and use the material. Your organization is responsible for the knowledge.
Extra caution where mistakes can cause harm: For things like allergens, legal matters, medical questions or other sensitive areas, Popscale should not replace your organization's own approved sources, procedures or professional responsibility.

Different roles in the same system.

Knowledge, Studies and Assessments do different jobs.

Studies: Help you discover what happens in the customer interaction and capture perspectives or experience that may be missing from existing documents.
Knowledge: Is the reviewed foundation you want to keep using.
Assessments: Use defined knowledge and criteria to assess what participants can articulate and reason about.
Journeys: Use the knowledge to develop the capability.

Discover → Review → Assess and train.

Frequently asked questions.

About Popscale Knowledge.

What is Popscale Knowledge?

Knowledge is the layer where the knowledge that should support the customer interaction is collected, structured and reviewed – for example products, processes, playbooks, objections and quality criteria.

Is Knowledge a general company wiki?

No. The purpose is not to store everything the organization knows. Knowledge focuses on the knowledge that should serve as the foundation for customer-facing training, Assessments and AI feedback.

Does the AI make up its own facts about our business?

Training and assessment should build on the knowledge you have entered and approved. In areas where a wrong answer can cause harm – for example allergens, legal matters or medical questions – Popscale should not replace your organization's own sources or professional processes.

Does Knowledge replace our intranet or LMS?

No. Knowledge is Popscale's knowledge foundation, not a complete document archive, intranet or LMS.

What happens when the knowledge changes?

When a knowledge object is updated, training content that builds on the object can be identified for review. You decide whether the content still holds or needs updating. Popscale should not automatically change customer-specific content without control.

Who reviews the knowledge?

You do. Your organization decides what counts as active, approved knowledge.

How do we bring in documents we already have?

Existing documents can be imported and used as the basis for structured knowledge objects with source links.

Can knowledge come from Studies?

Yes. A Study can capture experience-based knowledge from, for example, customer-facing experts and leaders. After review, the relevant parts can be structured in Knowledge.

Is Knowledge used in Assessments?

Yes. Where the Assessment concerns knowledge or ways of working, your organization's approved Knowledge can be an important basis for questions, correct answers and assessment criteria.

Book a demo.

What knowledge needs to work in your next customer interaction?

We’ll show you how knowledge becomes a reviewed foundation for training and assessment in Popscale. Before we meet, think about what today lives with only a few people – a product catalog, a service process or a new offer.

Start from the knowledge you already have

We’ll show you how documents you already have become structured knowledge objects with traceable sources.

See the review flow

Versions, approvals, and what happens when the knowledge changes.

Connect the knowledge to training and assessment

From knowledge objects to Episodes, Coaching, Roleplays, Journeys and Assessments built on your reality.