What's an internal knowledge base?

An internal knowledge base is a built-in knowledge base, i.e., one whose content you can create and manage directly within the Knowledge Base application. You can:

  • Start from scratch, and add articles directly within the Knowledge Base application.
  • Do a one-time import of articles from a CSV file, and maintain the articles thereafter within the Knowledge Base application.
  • Link the knowledge base to a Google sheet. You can maintain the Google sheet and sync the knowledge base to overwrite the knowledge base with the sheet’s contents. Or, you can add the knowledge base using the Google sheet and work thereafter entirely within the Knowledge Base application.

An internal knowledge base always makes use of a Natural Language Understanding (NLU) engine to evaluate the articles in the knowledge base against the consumer’s utterance (the intent). The articles, which have associated intents, are matched and scored by the engine, and the most accurate article is sent to the inquiring consumer.

High-Level Workflow

When adding an internal knowledge base, follow this workflow:

  1. In Knowledge Base:
    1. Add the internal knowledge base. In this step you can import articles from a CSV file or link to a Google sheet that contains them.
    2. Add the articles if necessary.
    3. Train the articles to match consumer utterances.
  2. Expose the articles to consumers by:

Domain intents versus Knowledge Base intents

Domain intents

When dealing with a knowledge base, an intent is the question that the consumer has ("What's your return policy?") or a problem the user needs to solve ("I can't remember my password.").

While the article's title represents the intent of the article, you can also specify the intent using alternate formats. You define these alternate formats in Intent Builder, within an intent in a domain. Here, they're called "training phrases":

Once you've created your domain of intents for the knowledge base, over in the Knowledge Base application, you create the knowledge base and specify the associated domain when you do:

Within the newly created knowledge base, you then link each article to an intent in the domain.

With Domain intents like these, you can use any of the following NLU engines for intent matching:

  • LivePerson
  • LivePerson (Legacy)
  • A third-party NLU engine

Domain intents make it possible for you to use the same domain in multiple ways, i.e., in knowledge bases, bots, or other features like Intent Analyzer.

Knowledge Base intents

As of March 5, 2021, you can no longer create a knowledge base that uses Knowledge Base intents.

If you created your knowledge base before March 5, 2021, you might have chosen not to define the intents in a domain in Intent Builder. Instead, you might have specified the intent's alternate formats directly within the article itself. In this case, these alternative formats are called "intent qualifiers":

Knowledge Base intents like these are a legacy feature that uses the LivePerson (Legacy) engine for intent matching. Knowledge Base intents don't allow for reuse, as the intent qualifiers themselves are defined within the articles in the knowledge base.

To take advantage of the benefits of performance and flexibility, you are encouraged to convert a knowledge base from Knowledge Base intents to Domain intents as soon as possible, as LivePerson will deprecate the LivePerson (Legacy) engine at the end of July 2021.


When you add an internal knowledge base, you'll specify its language.

When a text-to-text search is performed and a match is found, the knowledge base's language doesn't play a role. Whatever article is matched is simply returned.

When an NLU search is performed, the knowledge base's language works differently based on how you've defined the knowledge base:

  • If the knowledge base uses Domain intents, the domain's language is used instead. In this case, the languages supported depend on the domain's NLU provider.
  • If the knowledge base uses Knowledge Base intents (a legacy feature), the knowledge base's language is used. In this case, only English and Spanish are supported.

Positive and negative learnings

Positive and negative learnings play a role in intent detection regardless of whether you're using domain intents or knowledge base intents.

When using domain intents with the LivePerson engine or a 3rd-party NLU engine, the positive learnings are applied (added) to the training phrases when the model is trained, and the negative learnings are applied during processing of user inputs.

When using knowledge base intents or when using domain intents with LivePerson (Legacy) engine, positive and negative learnings are applied during processing of user inputs.

Active versus inactive articles

An article is either active or inactive. Active articles are returned in knowledge base searches in Knowledge Base integrations while inactive articles aren't returned.

  • An article is active if its Enable Article setting is turned on. If the article has Valid From and/or Valid To dates (optional, specified in UTC), it is only active during the specified time period. If no dates are specified, an enabled article is always active.
  • An article is inactive if its Enable Article setting is turned off. It's also inactive if the setting is turned on, but the current date and time in UTC falls outside the time period specified by Valid From and/or Valid To.

In the Knowledge Base application, you can easily identify an article's current status:

Using Valid From and Valid To dates

You can specify optional Valid From and/or Valid To dates when you add an article.

For example, you might run a promotion over a holiday that has an associated FAQ, and that FAQ should only be used for a finite period of time. Or, you might have an article that you want to become active on a certain date and remain so indefinitely. You can satisfy requirements like these with Valid From and/or Valid To.