Knowledge Articles

Why does the article title differ from the autocomplete suggestion?

As the user is entering a question in the search in the Support Center or in the widget, the autocomplete continuously checks for and returns the most likely responses that are identified based on our Natural Language Processing (NLP) algorithm and popularity.

The autocomplete can present any phrasing associated with articles. Knowledge base managers can control whether an article phrasing is returned in autocomplete with the Autocomplete checkbox next to the phrasing.

Once the user selects an autocomplete suggestion, the article associated with the selected phrase is presented. The title of this article may differ from the phrase the user selected.



Figure 1. What Autocomplete displays


Figure 2. What selected article looks like

Can you support multiple websites from one knowledge-base?

Yes, Bold360 AI supports multiple websites from a single knowledge-base, but you must set up a separate widget for all your websites.

However, it is recommended to separate the knowledge-bases in case of completely different content.

For more information, see How do I add another knowledge base? and What widgets do you provide and how can I add them to my website?

How do I add another knowledge base?

Learn what to consider before adding a new knowledge base.

When you use a single Knowledge Base for multiple websites

Bold360 AI can support multiple websites from a single knowledge base.

If you have similar content with some modifications based on different categories or websites, you shouldn't create another knowledge base but rather use just one knowledge base with contextual answers. Web visitors can ask the same question, and get different answers based on any differentiating information you have on a customer such as the product or page they're currently looking at. See What are Bold360 AI contextual answers? to learn more.

When you have multiple Knowledge Bases

It is recommended to have separate knowledge bases for completely different content, for example, for internal and external use, completely different websites, a dedicated knowledge base per language and so on.

If you'd like to have an additional knowledge base, contact your Customer Success Manger.

How can I handle various languages on the same topic?

There are two recommended ways to support your customers in various languages:

  • Use one knowledge-base for your local language and provide on-the-fly automatic translations. Read more here.
  • Create several knowledge-bases; one for each language. This option will ensure more accurate translations. Read more here

How to use the knowledge base launchpad

Use the knowledge base launchpad to create a knowledge base quickly and easily.

Note: The knowledge base launchpad is not available by default, it must be enabled for the knowledge base on account level. For more information contact your Customer Success Manager.
  1. In the AI Console, go to Knowledge > Launchpad.
  2. Select one of the predefined packages depending on your business needs.

    Result: Once you select a package, a list of articles appears.

  3. Review and modify the articles as required.

    You have the following options for each article:

    Table 1. Options for knowledge base launchpad articles
    Option Description
    Live This option controls whether the article is imported to the knowledge base in online or offline state. All articles are set offline by default. If you set an article live, it will be immediately available on touchpoints once you launch the article.
    Article Title Displays the article title and the number of phrasings available for the article. Select the number to see the phrasings.
    Content The body of the article. You can add the content you want to present as a response to the question that is in the Article Title.
    (Delete) This option enables you to delete specific articles from the list.
    (Launch) With this option you can launch a specific article.
  4. Optional: Add new articles as you see fit.
  5. Launch all articles using the button at the bottom or launch articles one by one.
    Note: Once you launch a package in a knowledge base, it can't be launched to the same knowledge base again.
The articles you launched are available in your knowledge base under Knowledge > Articles.

How do I define conversational flows?

There are multiple ways to enhance the conversational bot with call-to-action activities that enhance the user experience and help guide the flow and suggest options to the user. These can be added to the regular answers using the Conversation tab in Bold360 AI.

  1. In the AI Console, go to Knowledge > Articles and create a new article.
  2. On the Conversational tab, click the Conversation Enabled toggle to enable the conversational editor in the Article Editor.
  3. Select Add Flow.
  4. Add the main answer in the Content field that appears.
    Tip: If you want to display the content in multiple bubbles, enter the <page_separator/> tag in the text where you want to separate the content.
  5. Optional: Add rotating content.

    You can add variations for the content to create a more human-like user experience.

  6. Select +Child to create the options.
    Note: It is recommended to use between 5-7 quick buttons to avoid scrolling on the page.
  7. In the Title field that appears, enter the text you want to display on the button.

    The text on the button can be up to 20 characters long.

    Tip: Use synonyms to cover different user inputs. For example, if the buttons show Yes and No, you can create a synonym group that includes yes, yeah, ya and so on. This way, if the user types yeah instead of choosing the Yes button, they still receive the relevant answer.
  8. Select the type of button you want to use.

    You can either use quick buttons or persistent buttons. Quick buttons appear under the content as separate buttons and once the user selects an option, the rest of the options disappear. Persistent buttons appear as a list under the content and all of them remain visible to the user after they select one. Use the quick button if only one of the options is relevant to the user. Use the persistent buttons if multiple options could be relevant to the user.

  9. Add the content that is to be presented upon clicking the button.

    You have the following options:

    • Content: Enter the content that is to be presented to the user when they click on the button.
    • Variation ID: You can specify the article variation that is to be presented to the user.
    • Article: Use this option to direct the user to an answer in the knowledge base. You can search for articles by title.
    • Statement: Use this option if the answer has more variations associated with different contexts and you want the bot to display the relevant variation based on context. Enter the title of the article with multiple variations.
    • URL: You can create a link to a webpage with this option.
    • Phone Number: You can use this option to add a phone number and call the number defined when clicked.
      Note: Using this option affects the channeling score for phone on the Dashboard. For more information about the channeling score see What do I see on the Dashboard?.
    • External: Use this option to transfer parameters to an external interface. This is useful for handshaking with a customer app that uses certain parameters from the conversational bot.
  10. Optional: Besides plain text, you can also insert HTML elements in the conversation tree to enhance the conversation's look and feel, as well as its functionality. For example, you can enter a link in the conversational statement by adding an HTML tag in the Article Editor's text field.

How do I upload content into the knowledge base?

Content can be extracted from your current content management system and uploaded into Bold360 AI using the attached Excel template.

The fields to be captured per article:

Column 1- article title

Column 2 - article body. The article body is preferably to be provided with HTML formatting.

Column 3 - article labels. For general information about labels click here.

Column 4 and on - article contexts and context values. Each column should represent a single context type. Within this column for each article capture the relevant context values. For general information on Context see What are Bold360 AI contextual answers?

In order to upload the content please contact your Success Manager or send the file to support.

Synonyms and conversational flows

Synonyms are used to enhance your Knowledge Base (KB) and improve search results. There are two types of synonyms in Bold360 AI:

  • Local synonyms: The synonym repository in the KB which is created and maintained by your content management team. Local synonyms typically include words that are related to your business and serve as an extension to the list of global synonyms.
  • Global synonyms: Language-specific global synonyms that Bold360 AI uses which are relevant across all verticals.

For your conversational flows, synonyms are especially important as you will have to anticipate the different ways customers are looking for your goods or services.

The following is an example of global and local synonyms as seen in the Article Editor:

When you look at the synonyms of create, you see that "add" and "make" are defined locally. At the same time, "build" and "open" are defined as global synonyms that are also applied when a customer enters an intent.

How to add synonyms

The synonyms you add are applied to all articles in the knowledge base.

Create groups of synonyms broaden your terminology base and deliver the information your customers are looking for.

There's no need to update each question separately. Once a group of synonyms is created, it takes effect across the entire knowledge base.

Create and edit synonyms from the Synonyms page

  1. Go to Admin Center > KB Setup.

    The Knowledge base: Synonyms page is displayed.

  2. On the Knowledge base: Synonyms page, click Add new synonyms group.

    The Synonym group editor is displayed.

  3. Enter words which you want to treat as synonyms.

    Once you've entered the first word, the editor will recommend other relevant synonyms to choose from. You may either choose from the recommended words by clicking on them or enter your desired words in the New synonym box.

  4. Click Save.

    The Synonym words editor opens.

  5. Select the synonyms that should be associated with the words that you have.

    In the example above, the synonym "ms" was defined as synonym for "microsoft". The NLP engine considers "ms" as the plural form of "m" and, unless you clear the checkbox for that word, the engine adds that word as a synonym to "ms".

    If you define multiple words as synonyms then all those words are listed on this page.

  6. Click Apply to save your synonym group on the Synonyms page.
Note: To delete an existing synonym, click the trash icon next to the synonym group.

Create and edit synonyms in the phrasings editor of an article

  1. Go to Knowledge > Articles and open an existing article or create a new one.
  2. In the article editor, open the Phrasings section and click Synonyms.
  3. Click +Add to create a group of synonyms.

You may notice how the same question repeats itself in different phrasings with similar words. Once we create groups of synonyms, all four questions can be minimized into one. If there's already an existing group of synonyms for a word, you may edit the group by clicking on the synonyms. When editing a group, the synonym group editor opens.

What are quick action events?

When using Quick Action buttons, a special event can be created.

An event can be setting a new context or changing an entity value. Events can help you gather more information about your users and their specific preferences so that the bot can present the most relevant content for them.

For example, let?s say we have a context called User Type, and its value are Basic and Advanced. Suppose we have an article providing a general overview of our product. We can add a quick button like Learn more with an event that changes the User Type context to Advanced. Therefore, when the bot displays the Learn more article, it presents the variation of the article that has Advanced context.

Important: For a context value to be successfully set using an event, the context category must have Detect from user search enabled.

How else can you use context-based quick action buttons?

Let's say, you want to offer different shipping information for website visitors who are currently looking at an item and visitors who have actually purchased that item. In this case, you can create a shipping-related article with two variations: one where the context called purchased is set to true and one without any context defined. Then in your main article, you create the quick action button and define an event to open the shipping-related article when the visitor clicks that button. In this case, visitors who are just looking for an item may find general shipping information, while customers who have purchased that item may see the date when they are supposed to receive their products.

Tip: You can use synonyms to cover different user inputs. For example, if the buttons show Yes and No, you can create a synonym group that includes yes, yeah, ya and so on. This way, if the user types yeah instead of choosing the Yes button, they still receive the relevant answer.

What property options are available for custom entities?

Property options in Bold360 AI enable you to customize entities.

Table 1. Property options for custom entities
Option name Description
Life cycle The Life Cycle field above the properties table sets the life cycle for the entire entity. You can also set a life cycle for each property. Properties can have a life cycle that is shorter than the life cycle of the entity as a whole. For more information about life cycles, see How do life cycle options work?.
Name The expression used to identify the property and add to articles. The property name can contain letters, numbers and underscores. Spaces are not allowed.
Detect Specifies the type of input expected from the user, like text, date or number. Validation is completed based on the selection here. For example, if email is selected, the user is expected to enter an email address, otherwise they receive an error. If you choose Date, customers can use a calendar to select the date:
Bot Query The question the bot asks to receive the input from the user.
Error Message The error message displayed to the user when they provide an input that is not valid. You can also set the number of times the error message is to be displayed, that is, the number of chances you give the user to provide the correct format. After that the user receives the fallback message. For example, you have a property where Detect is set to Email, the bot query is What's your email address? and the error message is Please provide an email address. which is set to be displayed 3 times. When the user fails to provide an email address for the fourth time, the fallback message or article is displayed if it is set up.
Note: Validation is not possible for text-type properties, so you can't enable error messages for such properties.
Life cycle The Life Cycle field of the property sets the life cycle for the specific property. You can also set a life cycle for the entity. Properties can have a life cycle that is shorter than the life cycle of the entity as a whole. For more information about life cycles, see How do life cycle options work?.

What are the property options for data source entities?

Property options in Bold360 AI enable you to customize entities.

The options listed here are available in the Properties table of data source entites. Some of them you can find under (More options).

Table 1. Property options for data source entities
Option name Description
Life cycle The Life Cycle field above the properties table sets the life cycle for the entire entity. You can also set a life cycle for each property. Properties can have a life cycle that is shorter than the life cycle of the entity as a whole. For more information about life cycles, see How do life cycle options work?.
Expose? Sets the visibility of this property in a conversation.
Key Displays the header names as they are in the data source.
Name The expression used to identify the property and add to articles. The property name can contain letters, numbers and underscores. Spaces are not allowed.
Detect Controls whether the property is visible in a conversation.
Query The question the bot asks to receive the input from the user.
Life cycle The Life Cycle field of the property sets the life cycle for the specific property. You can also set a life cycle for the entity. Properties can have a life cycle that is shorter than the life cycle of the entity as a whole. For more information about life cycles, see How do life cycle options work?.
Split by A syntax value such as a comma or a vertical bar that is used to separate multiple values in a CSV cell or in the value associated with a JSON key.
Auto Spelling When selected, the customer's answer doesn't have to be an exact match to a value in a CSV cell or a value associated with a JSON key.
Is Shared You can share the selected property with another entity. For example, if you define color in your phone and tablet entities, then you can share the color values across entities. In this case, when the customer selects a phone color that doesn't exist in the phone entity but exists in the tablet entity which is shared, then the bot will know it is a color and present the message defined in the entity for no results.
Autocomplete When selected, customers are offered autocomplete, or type-ahead options as they enter the entity value.
Use Quick Option The customer can choose from the values that a specific CSV column or JSON key contains. For example, if the CSV contains Apple, Samsung, and Google in the Brand column for a list of mobile phones, these options are displayed as buttons to the customer. See How to use quick options in a conversational article to learn more.
Parent property You can set up a dependency between two properties of the same entity. For example, the parent property of Cities can be Country. When the customer is asked about these two properties, the following happens:
  • The bot asks the question for the parent property first. For example, What country are you located in? and then Which city do you reside in?.
  • If the Country property is either asked again or deleted, the City property is also deleted, that is, the child property behaves in the same way as the parent property.

How to create API-based entities

Entities in Bold360 AI enable you to turn your data into smart chatbot conversations.

Note: The steps described in this article require web developer knowledge.

To set up an API-based entity you need a custom entity to collect data from the customer for the API, a data source entity with the API as its data source that uses the custom entity and an article you use these entities in. In this example, we have an API for data about concert tickets and we want to create a bot that the customer can ask about the tickets that they already booked.

  1. Create a custom entity.

    You create this entity to collect the data required for the API. In this example, we're asking for the customer's email address to display their booked concert tickets.

    Example:

    Entity name: TicketDeails

    Entity description: Collect the customer's email address

    Table 1. Property table of TicketDetails
    Name Detect Bot Query ErrorMessage Life Cycle
    Email Email What's your email address? Please enter a valid email address. Persistent
  2. Create a data source entity with the API as its data source.
    1. Choose (Create Entity).
    2. Select custom entity for entity type.
    3. Provide a name and optionally a description for your entity.

      The entity name can contain letters, numbers and underscores. Spaces are not allowed.

      You can use the description to give your entity a more meaningful name or description that helps you identify it later.

      Example:

      Entity Name: TicketsByName

      Entity Description: Get a list of tickets by email address

    4. In the Data Source URL field, enter the URL of the API and add the property of the custom entity you created in Step 1.

      Example: https://api.example.com/v1/tickets/[[TicketDetails.Email]]

      Result: The custom entity is listed as a dependent entity under the Properties Table. See What are dependent entities? to learn more.

    5. Change Response Type to JSON.
    6. Choose LOAD.
    7. On the set parameters samples dialog enter a sample email address and choose LOAD.

      This way the system knows what a valid response looks like.

      Result: The Properties table is automatically filled with the keys that come from the API.

    8. Define display settings.

      Display settings are available for arrays. See What are the display settings for API-based entites? or more information.

    9. Save the entity.
  3. Create an article that uses these entities.
    1. Go to Knowledge > Articles.
    2. Create a new article or open an existing one and add the entity in the article's body.

      Example: Intent: What tickets do I have reserved?

      Body: ?You have the following tickets reserved: [[TicketsByEmail.TicketsByEmail_ARRAY]]

    3. Publish the article.

What are dependent entities?

Dependent entities are entities used in other entities.

When you have an entity with an API as data source, you need to set up a custom entity that collects the information from the user and and include this custom entity in the API-based data source entity to pass it on to the API. Dependent entities provide a better understanding of what properties compose the entity.

To add dependent entities, do the following:

  1. In the AI Console, go to Knowledge > Entities.
  2. Select an existing entity or create a new one.
  3. Choose click URL inputs next to Data Source URL.
  4. Add the entity you want to use.

    You can add an entity on the Parameters,Headers or Bodytab, depending on where it's needed. The entity should be added in [[Entity_Name.Property.Name]].

The dependent entities are listed under the Properties Table.

How to create data source entities

Use data source entities in Bold360 AI to turn your data into smart conversations.

Make sure your widget is set to conversational. Learn more here.
In this example, we have a list of mobile phones and we want to create a bot that recommends users the best mobile devices based on their needs. We are going to set up a data source entity based on this list of mobile phones and then create an article that uses this entity.
  1. Create the list of mobile phones in a CSV file.

    A sample CSV file is attached at the end of this article. Learn more about the different data source options and requirements in this article.

  2. In the AI Console, go to Knowledge > Entities.
  3. Choose (Create Entity).
  4. Select data source entity for entity type.
  5. Provide a name and optionally a description for the entity.

    The entity name can contain letters, numbers and underscores. Spaces are not allowed.

    You can use the description to give the entity a more meaningful name or description that helps you identify it later.

    Example: Name your entity MOBILE_PHONES.

  6. Fill out the Data Source URL field.

    You can select the CSV file from your local computer and upload it to Bold360 AI' secure server or you can upload the file to a file hosting service like OneDrive and enter its URL here.

    Note: If you provide a link to the file's location, make sure it's publicly accessible.
    See What are the data source URL options? for more options.
  7. Set the response type to CSV.
  8. Choose LOAD.

    Result: The properties table is now loaded. Properties are the columns that are available in the data source file.

  9. Fill out the Properties table.

    See What are the property options for data source entities? and How do life cycle options work? to learn more about the options.

    Example:

    You should decide what questions the bot should ask the end users to offer the best possible recommendation about phones. In this example, the bot asks questions about brand, price range, and camera quality.

  10. Optional: Define fallback messages.

    See What are fallback messages? to learn more.

    Example: For this example, we enter Unfortunately, there's no mobile device that matches your preferences. for no results and set up a carousel to be displayed with the image, the brand and model, and the price if there are multiple results based on the customer's responses.

  11. Save your changes.
  12. Now go to Knowledge > Articles.
  13. Create a new article or open an existing one and add the entity in the article's body.

    In the article's body, create the final response of the bot: this is what the bot responds when there is a single mobile device to recommend. The response should use the entity to present the details of the selected mobile device. To insert an entity, you can either choose or enter [[ in the text editor and have a drop-down of all entities displayed. Once you add an entity to the response, the entity is automatically added to the article. You can expand the entity to see the questions that the bot may ask the user and adjust them to fit the article if needed.

    Note: You can drag-and-drop entities in the Article Editor to control the order of the questions in the conversation.

    Example: Intent: I want to buy a mobile phone

    Body: ?

  14. Publish the article.

You can now see the conversation in action in your widget ? just enter I want to buy a mobile phone.

Important: The bot doesn't always ask all the questions we set in the entity. It can automatically identify when there is no need to ask a question, for example, when there is only one possible result left. In addition, the order of the questions might differ as the bot automatically chooses the order based on what it estimates as the fastest way to get to a possible answer.

How do life cycle options work?

The life cycle of an entity in Digital DX defines the period during which the bot remembers the user's answer.

You can define a life cycle for the entity as well as for each property of the entity. Properties can have a life cycle that is shorter than the life cycle of the entity as a whole.

Table 1. Entity life cycle options
Life cycle option Description
Persistent The bot remembers the user's answers for the duration of the session, that is, until the user closes the browser.
Topic The bot remembers the user's answers as long as the articles returned to the user's questions contain the entity. So as soon as the user asks the bot for an article that does not use the entity, the bot deletes the user's answer from its memory.
Intent The bot remembers the user's answer as long as the user is in the same intent. So as soon as the user asks the bot something else, the bot deletes the user's answer from its memory even if the answer to the user's next question contains the same entity.
Statement The bot remembers the user's answer until another question is asked from the user. For example, if the bot asks two questions, like What is your first name? and What is your email address?, the bot forgets the user's first name before the second question is asked.

What are the data source URL options?

Use these options when providing a link to a file or an API link in the Data Source URL field of a data source entity in Bold360 AI.

When creating a data source entity, you can either upload a CSV or a JSON file from your local drive or add a URL to such a file or provide the URL of an API as data source.

Entities support two types of HTTP methods to integrate an external URL: POST and GET. You can select a method from the drop-down next to the Data Source URL field.
The following options are also available for data source URLs:

  • URL inputs which enable you to add header and body content
  • Interval settings where you can set the refresh interval for how often the cached version of the file is to be refreshed
  • Download file to get a local copy of the file

URL Inputs

To integrate an external data source, you may need to use specific parameters, headers or include specific data in the body of the request when you send it to the server that stores the data files.

When you select (URL Inputs), you have the option to add parameters, headers and a body in case of POST requests. It is possible to include another entity as a parameter, in the header and in the body in which case this entity is listed as a dependent entity under the Properties table. See How to create API-based entities to learn more.

Headers

In several cases, POST requests require specific headers to be sent to the server. When testing a POST request, the tool you're using might automatically add certain default headers without even showing them to you. Make sure you add all headers in the entity configuration.

Body

In the body you can add content. The body of an HTTP request supports different formats for sending content. The format you should use depends on what the receiving server expects. In the AI Console, POST requests in entities support raw format only.

How can I use entities in user search?

What are the display settings for API-based entites?

Display settings are available for arrays in API-based data source entities.

Choose for an array in the Properties table of your API-based data source entity to set up the following options:

  • Display results in a carousel
  • Display results as quick buttons
  • Display a message when there are no results

What are system entities?

You can use built-in, or system entities even without defining your own ones. These Entities let you define the following:

  • NUM - Stores the numeric value that the user enters.
  • EMAIL - The answer displays the email address that the user entered as part of the intent.
  • DATE - User can either select a date from a date picker or type a date in MM/DD/YYYY format. The answer displays that value in MM/DD/YY format.
  • DATE_TODAY -
  • DATE_TODAY_DISPLAY -
  • DURATION - Converts weeks, days, hours, and minutes into number of days.
  • DATE_RANGE -
  • DATE_RANGE_PAST -
  • DATE_RANGE_FUTURE -
  • LOCATION - Returns the user's geolocation (latitude and longitude coordinates).

What are entities?

Entities in Bold360 AI enable you to turn your data into smart chatbot conversations.

Tip: Check out this video to see entity configuration in action.

Entities serve as a database for the information that the conversational bot needs to answer your customers' questions. You set up an entity with a data source and provide different questions the conversational bot will ask the customer about the same set of data. For example, you have a data source for mobile phones and you want to create a conversational bot that recommends your customers the best mobile devices based on their needs. Your data source contains information about the brand, the model, the price, the screen size and so on of the mobile phones available. In the entity, you can set up questions about these bits of information, like Any specific brand you're looking for? and What is the price range?. The customer answers these questions and the conversational bot provides the best fit or fits based on their answers.

With entities, you can provide a smart conversational experience to your customers:

  • If the customer provides an answer to a question that the conversational bot hasn't asked yet, it won't ask that question. For example, if someone is looking for an iPhone with 64GB memory, the bot will skip the question about memory type and potentially the one about phone type as well.
  • The conversational bot presents the questions in the most effective way to ensure the customer has to provide the least number of answers to find the result. So regardless of the order of the questions in the entity, the conversational bot rearranges the questions in the most logical way.
  • When a question has one answer only, the bot simply skips that question and does not present it to the customer. For example, if there is only one Samsung phone with a 7" screen, the bot doesn't ask the customer about either the camera or the memory of the phone, but displays the result immediately.

Bold360 AI supports the following types of entities:

  • Data source entities where the data comes from
    • a CSV or a JSON file or
    • an external data source through an API
  • Custom entities that you can use
    • to collect information from your customers in an interactive way
    • an auxiliary for API-based data source entities as they help collect the information required for the API and then trigger the API itself

Conversation entity verification

As a content manager, you can create conversations that verify answers that end-users provided and to prevent any typos or other human errors. To do that, create a new step in the process of API-based entities that will do the following:

  • Summarize the data the user has provided
  • Present the data to the user in the widget
  • Enable the user to change the data if needed or to confirm.

How do data source entities work?

Use data source entities in Bold360 AI to turn your data into smart conversations.

Data source entities can be based on a CSV or a JSON file or can retrieve data from an external data source through an API. In terms of the data source, you have the following options:

  • Upload the file from your local drive
  • Upload the file to a file hosting service like OneDrive and add its URL to the entity
  • Specify the URL of an API
See What are the data source URL options? to learn more.

Makes sure the CSV or JSON file you use with entities meet the following requirements:

  • The file is valid, for example, the CSV file contains no unescaped commas. Use a validator tool to check.
  • If you provide a link to the file's location, make sure it's publicly accessible.
  • The file is structured in a way that
    • Each bot query corresponds to a column
    • Each response corresponds to a row or a part of it
    • Columns are divided into two parts: bot queries and answers.
See this article to learn how to set up an entity with a CSV data source.

How to limit a content manager's access to knowledge bases

Create user groups that provide access to selected knowledge bases and assign them to users.

When you have multiple knowledge bases (KBs) and content managers, you may want to restrict users to have access to those KBs that are relevant for their daily work. For example, your organization may support multiple languages or products, where a each language or product has its own KB and is curated by a specific content manager. In this case, you can create a user group and assign a KB to that group. Then you can add users to the same group.

  1. In the AI Console, go to Admin Center > Users.
  2. Click the Groups icon.
  3. Click the Create Group link.
  4. Give the group a name, and on the Advanced tab, select the knowledge bases that you want group members to have access to.
  5. Click Save.
  6. Add users to the group:
    1. On the Users page, click on the name of a user.
    2. Click the Groups icon.
    3. Select the groups that you want the user to be a member of.
    4. Click Apply.

Your users are now limited to access the selected knowledge bases only.

How can I assign users to voices?

You can assign users to customer voices in Search Optimizer to create or revisit articles based on customer needs.

To assign users to voices in Search Optimizer, you must have the Enable voice assignment option enabled for your account. Contact your Customer Success Manager for more details.

  1. In the AI Console, go to Voices > Search Optimizer.
  2. Search for the voice that you want to assign.
  3. Choose in the Owner column.
  4. On the Set the owner pane search for a specific user or find one in the list and select Set as new owner.

Users can find all voices assigned to them under Voices > Assigned to Me.

How can I export voices?

You can export voices from the Unanswered, Answered and Muted categories in Search Optimizer.

  1. In the AI Console, go to Voices > Search Optimizer.
  2. Optional: Apply filters and change the time frame.

    These changes will be reflected in the exported file.

  3. Expand for the selected category.
  4. Select one of the export options.

    To export the content of the table to a comma-separated values (CSV) file or an Excel file, use the respective option under Export Voices.

    To export the details of the voices to a comma-separated values (CSV) file or an Excel file, use the respective option under Export Events Log.

How to add negative phrasings in the Article Editor

You can set a phrasing as negative in the Article Editor so that the bot knows what customer voices the article should not answer.

Note: To add negative phrasings, you must have the Enable negative examples feature enabled for your account. Contact your Customer Success Manager for more information.
  1. In the AI Console, go to Knowledge > Articles.
  2. Open the article in the Article Editor and view its Phrasings.
  3. Enter a new phrasing and click Add.
  4. Click Set as negative next to the phrasing.

  5. Publish the article.

How to manage localization in the Digital DX  AI platform?

One of the most efficient ways to manage translations/localization is to use GeoFluent, which works in search and conversational widgets alike. However, if you do not have a GeoFluent account, you can still use Digital DX AI's built-in translation management feature: as a Knowledge Manager, you can control the localization of individual articles, directly from the Article Editor.

Important:
  • This solution is limited to search widgets.
  • You must have at least two knowledge bases set up on your account that are part of the same translation group. Contact your Customer Success Manager to set up additional knowledge bases.

Even though this solution is available in search widgets only, it works in conjunction with auto-translation:

  • If there is an article in the user's language, then that is presented
  • If there is no relevant article, then the English KB is searched and the response is translated on-the-fly with Google Translate

To create a localized version of an article, do the following:

  1. In the AI Console, go to Knowledge > Articles.
  2. Open an article that you want to localize.
  3. On the Localization tab of the Article Editor, click Add localization.
  4. From the Choose KB drop-down list, select the knowledge base where you want to create the localized version of the selected article.
  5. Define the appropriate translation for the selected article:
    • On the Choose an existing answer tab, you can search for an article in the target knowledge base that contains the translation of your article (if you know there is such an article)
    • Otherwise, on the Write Answer tab, you can verify that the translation provided by Google Translate is correct
  6. On the Write Answer tab, add the necessary phrasings to the localized articles and make sure the article is Set Live.
  7. Save your changes.

    The Localization tab, now lists all localized versions of the article. The list includes the name of the user who last edited the localized article, the knowledge base that contains the localized article and the title of the article. Click View next to a localization to open the translated version of the article.

  8. Publish the original article to make the localized versions available.

The number of localized versions of an article is displayed on the Articles page:

How to delete an article variation

When you have multiple answers for a question and you no longer want to display different answers to this question based on context, you can remove the article variation.

Remember: If you delete articles, you lose all insight into how these articles performed in the past. To ensure reporting insights remain intact, set the articles offline instead.
  1. In the AI Console, go to Knowledge > Articles and open the article you have already created.
  2. Under Context Variations, choose next to the variation you want to delete.

    Result: The Duplicate and Delete options appear.

  3. Select Delete variation.
  4. Choose OK on the confirmation that is displayed.
  5. Publish the article for your changes to take effect.

How can I assign users to articles?

You can assign users to an article to signal that the article needs revision as part of the approval process.

To assign users to articles, you must have the Enable approval workflow option enabled for your account. Contact your Customer Success Manager to enable it for you. See How to define a content management workflow for more information.

Important: A user must have modify permission for Knowledge-Base to be included in the workflow.
  1. In the Bold360 AI, go to Knowledge > Articles.
  2. Create an article or open an existing one that you want to assign to a user.

    Result: The Article Editor is displayed.

  3. At the top of the Content tab, click New Assignee.
  4. Select a user from the list.

  5. Click Publish & Close.

Users can find all articles assigned to them under Knowledge > Assigned to Me.

You can also set up email alerts when the assignee changes. See How to receive email alerts about changes in an article to learn more.

How do I add an additional phrasing to an existing article?

To add an additional phrasing to an existing question/answer, do the following:

  1. Go to Knowledge > All Articles in the Bold360 ai navigation menu.
  2. Search your question in your online Knowledge Base.
  3. Select your question (article) and click Phrasings.
  4. Enter a new phrasing and click Add.
  5. Click Publish to save the new phrasing.

How to create good phrasings for your article?

  1. Add synonyms. (For example: I want to buy tea: buy|porches|sell|stock|get etc.)
  2. Do not add more than 5-10 phrasings per article. That will make precision less accurate.
  3. Add keywords in your phrasings (from the previous example: tea).

For more information about phrasings, see these articles:

How do Synonyms work?

What is the best practice for phrasings and synonyms

How do I review overlapping phrasings?

While editing an article, you notice that it has overlapping phrasing.

Bold360 AI enables knowledge managers to easily optimize phrasings by providing a list of articles that use the same or similar phrasing.

  1. In the Article Editor, select Overlapping phrases above the intent.

    This button is only available for an article that contains overlapping phrasings with other articles.

  2. On the Overlapping phrases dialog, select an article from the list to open it for editing on a new tab.
  3. Edit the phrasing of the article you just opened or go back to the original article and edit the relevant phrasing there.

    Unique phrasings ensure visitors get the most relevant results during search.

  4. Publish the articles.

What is letter count?

The letter count shows the number of characters with spaces in the given article.

Letter count is available for articles in the knowledge base as follows:

  • As a column in the article list under Knowledge Base > Articles
  • Above the Content area in the Article Editor

Why do I see N/A in the Letter Count column?

If the Letter Count column in the Article List shows N/A, the article in question uses conversational elements, like quick buttons, entities or has content on the Conversational tab. Therefore, the N/A value provides insight into which articles in the knowledge base contain such elements.

How do I add a link to a Bold360 AI answer?

To help your customers find related information, you can add links to other articles in your knowledge base.

  1. In the Article Editor, click on the (link) icon in the answer toolbar to open the Link dialog.
  2. On the Link Info tab, enter the text that you want to display as a link.
  3. Select Article from the Link Type drop-down.
  4. Optional: Select the Link to specific variation checkbox.

    When you create a link to an article with multiple variations, by default, Bold360 AI chooses the correct variation based on the context. This option enables you to create a link to a specific article variation yourself.

  5. In the Select an answer field, start typing the title of the article that you want to display once the link is clicked.

    Result: A list of matches is displayed.

  6. Select an article.

    If you selected the Link to specific variation checkbox, you can find and select a specific variation of an article.

Example:
 

For an example, we have created this link. Clicking it will direct you to the linked Bold360 AI answer.

How can I add an attachment to an article?

Learn what types of attachments Bold360 AI supports and how to add them to an article.

To add a file to an answer, simply click on the attachment icon in the answer's toolbar.

A browser window will open for choosing your file.

These are the type of files which are supported as attachments in Bold360 AI (Knowledge base, Ticketing):

  • jpg
  • jpeg
  • png
  • gif
  • bmp
  • bml
  • tif
  • pdf
  • doc
  • docx
  • xls
  • xlm
  • xlsx
  • ppt
  • pptx
  • zip
  • rar
  • txt
  • xml
  • eml
  • pps
  • ppsx
  • rtf
  • csv
  • tar
  • gz
  • set
  • html
  • mobileconfig
  • apn
  • cs
  • aspx
  • mht
  • ged
  • uzed
  • zed
  • mp4
  • wav
  • mov
  • avi

In case you need to support additional attachment types, please contact our support team.

Please note, that the attachments are not supported in Bold360 AI conversational widgets.

How to create a button as a link in an article

In order to present a link as a button, copy the CSS below into the source of the article. In the snippet you will need to update:

  • The target link
  • The styling of the button
  • The text presented on the button

In order to generate the button's style you can also use widely available CSS Button generators.

<p><a href="https://www.Nanorep.com" 
style="background-color:#44c767; -moz-border-radius:28px; -webkit-border-radius:28px; border-radius:28px; 
border:1px solid #18ab29; display:inline-block; cursor:pointer; color:#ffffff; font-family:Arial; 
font-size:17px; padding:16px 31px; text-decoration:none; text-shadow:0px 1px 0px #2f6627 ;">green</a>
</p>

How do I remove a label from an article?

Remove labels from articles to remove the article from a group.

  1. Go to Knowledge > All Articles.
  2. You can remove labels from articles in the All Articles list or in the Article Editor.
    • To remove all labels from an article in the All Articles list, select the checkbox for the article, choose and select Clear labels. Confirm that you want to remove all labels from the article.
    • To remove labels one by one from an article in the Article Editor, open the article for editing and in the New Label field remove the labels using the x next to the label. Publish the article.

How to rearrange Quick Action buttons

You can drag-and-drop Quick Action and Persistent List buttons at the bottom of the Article Editor to change the order of the quick option buttons. By reorganizing buttons, you can easily drive customers' attention to the action that you prefer most.

How do I add a link to an answer?

You can add a URL to the body of an answer and present it as a URL or as clickable text.

  1. Select the desired text and then click on the "Link" icon in the toolbar. You may also click on the link icon without selecting any text. In that case, you'd be adding a direct URL address.
  2. In the link dialog, enter the target URL.
  3. Click OK to add the link.

Knowledge Base Labels

Knowledge base labels are categories you can use to organize content in the knowledge base or in the support center.

Knowledge Base Labels are categories that you assigned to articles to make organization of your Support Center easier and more efficient. You can arrange labels in a hierarchy to define how your Support Center is displayed. Labels also make it easier for you to search for specific topics and related answers.

Tip: Looking for information regarding Ticket Labels? See How do I assign a label to a Ticket?

Creating a Label

  1. Go to Knowledge > All Articles and click the Label icon.
  2. Click Create Label.
  3. The Content Labels window is displayed, where you can add, remove, edit and sort labels.
  4. Under Label Name, give your Knowledge Base Label an appropriate name and then select a color for your label.
  5. Save your changes. The label is displayed in the list of Knowledge Base Labels, and is displayed next to any article to which it is assigned.

Categorizing Knowledge Base Answers Using Labels

Categorizing Knowledge Base answers mean that you can easily organize your support page into groups of related topics for easy browsing of your customers.

  1. Go to Knowledge > All Articles, and select the article(s) to be categorized.
  2. Click the Label icon.
  3. Choose the relevant label to assign it to the article.

Categorizing Multiple Labels at Once

  1. On the Knowledge > Articles page, select the check box of an article (or articles).
  2. Click the Label icon () in the toolbar.
  3. Click Select multiple....
  4. Select labels and click Apply.

How can I add labels to articles?

Add labels to articles to group related articles together.

Once you have created labels, you can assign them to articles.

  1. Go to Knowledge > All Articles.
  2. You can add labels to articles in the All Articles list or in the Article Editor.
    • To add a label to an article in the All Articles list, select the checkbox for the article and then choose and select the label you want to assign. To assign multiple labels at once, choose Select multiple... in the label menu, select the labels to assign and choose Apply.
      Tip: You can assign labels to multiple articles with this option.
    • To add labels to an article in the Article Editor, open the article for editing and select the labels you want to assign in the New Label field. Publish the article.

How to create labels

Create labels to organize content in your knowledge base and group articles in the support center.

  1. Go to Knowledge > All Articles, and choose (Label).

    Result: In the drop down list displayed, you can see existing labels, and three links, including the Create Label link.

  2. Select the Create Label link.

    Result: The Label Editor is displayed.

  3. In the Label Editor, enter a name for the label and customize the look of the label.
  4. Choose Save to create the label.
The label is now be displayed in the list labels and when assigned to an article, it is displayed next to the article in the All Articles list.
You can now assign this label to articles and use it in the support center as well.

What is the knowledge base launchpad?

The knowledge base launchpad in Bold360 AI enables content managers to jumpstart a knowledge base.

Note: The knowledge base launchpad is not available by default, it must be enabled for the knowledge base on account level. For more information contact your Customer Success Manager.

The knowledge base launchpad offers several packages content managers can choose from depending on the nature of the knowledge base they want to set up. The packages contain a set of intents with phrasings which serve as examples and guidance for content creation and can be changed. To access the knowledge base launchpad, go to Knowledge > Launchpad.

With the knowledge base launchpad, content managers can:

  1. Select from a list of predefined content packages
  2. Review the content of the package
  3. Edit the content of the package such as edit the intent, the phrasings and the content of the article
  4. Delete articles from the list that are not needed and add new ones
  5. Set articles live
  6. Launch the entire package or specific articles of the package to the knowledge base

See How to use the knowledge base launchpad to learn more about how to use the launchpad.

How do I start creating my Knowledge Base ?

You can import an existing FAQ from a website, create articles manually or upload articles in a batch to fill your knowledge base with content.

You can populate the knowledge base software in 3 different ways.

Importing FAQ from a Website

You can create an instant Knowledge Base by importing an existing FAQ. The Import FAQ tool enables you to import an entire existing FAQ page into the Bold360 AI knowledge base.

  1. Go to Knowledge > Import FAQ.

    Result: The Import FAQ tab is displayed.

  2. In the Enter your FAQ URL field, enter the address (URL) of the FAQ that you want to import.
  3. In the Context section, specify the page type. This can be an internal knowledge base page for your support staff to use, or a public FAQ page.
  4. In the Product ID field, enter the name of the product for this Knowledge Base.You may have more than one product, each of which requires its own Knowledge Base.

Adding new answers manually

There is no need to put a lot of effort in collecting questions for the initial knowledge base, since Bold360 AI will learn new questions from your customer inquiries and new answers from your representatives.

How can I add a new article to my Knowledge Base?

Upload via an Excel sheet

We can upload articles via an Excel file directly into your knowledge base in Bold360 AI.

The Excel file must be Excel 2003-2007 Format.

How to import multiple articles in a batch with the API

For more information regarding uploading the articles via an Excel file, contact your Customer Success Manager, or contact our support.

What are the best practices for managing a knowledge base?

Follow these best practices and guidelines to build a knowledge base that knowledge base managers can work with efficiently and where customers can find answers to their questions with ease.

Bold360 AI offers various options you can use to optimize your content:

  • Links to connect related articles to each other for easier findability
  • Labels to organize content in your knowledge base and group articles in the support center
  • Phrasings to make sure readers find relevant content when they use wordings other than the intent
  • Synonyms to cover similar words thus minimize the number of phrasings
  • Context to keep internal and external content separate, offer different escalation channel options based on customer type and so on
  • Article variations to create alternative answers to the same question for different audiences
  • User groups and permissions to provide access to a specific knowledge base or a subset of one
  • Content management workflow to ensure the quality of the content
  • Search Optimizer to help knowledge base managers follow up on customer voices and improve content and phrasings

What are the best practices for labels?

You can increase productivity using labels because you can save time looking for content. Organizing the content helps to keep the content grouped together per owner which in turn also creates easy accountability when filtering the reporting data by label.

When creating and applying labels to articles, keep in mind the following:

  • It?s best to use labels based on how you group content and assign content-related tasks internally.
  • It?s good practice to use a label for conversational articles and articles that include videos to easily find them.
  • To have control over what articles are presented in the FAQ, use a specific label for FAQ articles.
  • To create channeling policies and reports for certain articles, use the same label for them.

What are the best practices for phrasings?

When creating phrasings, remember the following:

  • Search works best with phrasings that are
    • to the point
    • three to eight words long
    • simple sentences
    • formulated as a question
  • Use phrasings that are unique to a single article to ensure the accuracy of search results.
  • Increase variety in the wording of phrasings? as the search algorithm looks at the combinations of the different terms used across all phrases in the article.?
  • Use negative phrasings when you have articles with almost identical titles and substantially different content.
  • Use synonyms instead of phrasings to cover words that are close in meaning.
  • Add up to 10 phrasings for an article.
  • Use the full term in the title and add acronyms as phrasings.
  • Use entities to turn your data into smart chatbot conversations.
  • When leveraging voices to create new phrasings, clean up the voice, for example, remove typos, redundant words and shorten long sentences to improve the appearance of phrasings in autocomplete.?

What are the best practices for synonyms?

Keeping a large list of synonyms helps improve the Bold360 AI Natural Language Processing (NLP) algorithm.?

When creating synonyms, remember the following:

  • Use narrow synonyms. If a synonym is too broad, it negatively impacts search results and it is difficult to identify the root cause.?
  • There?s no need to capture typos as the NLP algorithm automatically corrects them.
  • Create synonym groups for common abbreviations of a word.
  • Add synonyms that are specific to your business.
  • Use synonyms for acronyms and word combinations of two or more words.

How do I create an HTML link to a Bold360 AI article?

You can create Direct Links to other Bold360 AI articles on your website, in e-mails, or anywhere else.

To add a link to another article:

Option #1

  1. In the Support Center, open the article that you want to link to.
  2. Click open a new tab .
  3. Copy the URL of the article from your browser.
  4. Paste the link to the article where you want to show this link.

Option #2

  1. In the Support Center, open the article that you want to link to.
  2. Click Share this answer .
  3. Click Copy to clipboard.
  4. Paste the link to the article where you want to show this link.

How to use custom entities

Use custom entities in Bold360 AI to gather information from your customers and use it to offer a personalized experience.

Make sure your widget is set to conversational. Learn more here.

You can also use custom entities as an auxiliary for API-based data source entities as they help collect the information required for the API and then trigger the API itself.

Instead of asking your customers to fill in a form, you can create a conversation to gather information about the customer. For example, you can set up a custom entity that asks for the customer's name and then include their name in articles. Here's how to do that:

  1. In the AI Console, go to Knowledge > Entities.
  2. Choose (Create Entity) in the top right to create a new entity.
  3. Select custom entity for entity type.
  4. Provide a name and optionally a description for your entity.

    The entity name can contain letters, numbers and underscores. Spaces are not allowed.

    You can use the description to give your entity a more meaningful name or description that helps you identify it later.

    Example: Name your entity UserDetails.

  5. Set the life cycle of the entity to Persistent.

    This way, the bot does not forget the user?s first name once they enter one.

    You can also a set a life cycle for the individual properties keeping in mind their life cycle can't be longer than the life cycle of the entire entity. See this article to learn more about how the different life cycle options work.

  6. Fill out the entities table.

    Example:

    Table 1. Property asking for customer's name
    Name Detect Bot Query ErrorMessage Life Cycle
    FirstName Text Hi, I'm your virtual assistant. What's your first name? N/A Persistent
    Note: Since it's not possible to validate text-type custom entity properties, you can't enable error messages for such properties.

    To learn more about the property options for custom entities, see this article.

  7. Save your changes.
  8. Now go to Knowledge > Articles.
  9. Create a new article or open an existing one and add the entity in the article's body.

    Example: Intent: I want to go to Greece for a vacation

    Body: ?Here are our current offers for you, [[UserDetails.FirstName]]:?

    <add options to the article>

  10. Publish the article.

When an article that uses the UserDetails entity is returned as a response, first the entity question is presented then the article is presented with the name they provided. If the conversation continues and the another article with this entity is returned as a response, the bot won't ask the question again, because the customer name is retained for the duration of the session, as defined by the persistent life cycle option.

How to use the Article Editor

The Article Editor is your ultimate tool for creating content for your customers.

The Article Editor is your ultimate tool for creating content for your customers. It offers the following features:

  • Content tab - A content editor to create articles that the bot serves to your customers
  • Visibility tab - Visibility settings to manage where your article is displayed, when it automatically expires, and which users can access the article in your knowledge base. You can also view the list of articles linked from the current article.
  • Options tab - Set channel value. See Can I offer a special response to a high-value question?
  • Notes tab - Add notes to your article. See How to add notes to an article.
  • Revisions tab - View and revert to previous revisions of your article. See How to view or revert to previous article revisions.
  • Comments tab - View comments of end-users who use the Advise widget
  • Rejections tab - As part of the content management workflow, add rejection notes to the article. See How to define a content management workflow.
  • Save a draft version, publish or delete the article
  • Toggle the status of the article between online and offline by clicking Set Live

To create a new article, do the following:

  1. In the AI Console, open the Article Editor:
    • In the left navigation menu, click Knowledge > Add Article..
    • In the left navigation menu, click Knowledge > All articles, then click New Answer.
  2. Type a question in the Add title field and type the answer in the text editor.
  3. Save your article:
    • Click Save if you have not finished editing the article and you want to save an offline draft.
    • Click Publish to publish the new article in the Knowledge Base.
    • Click Publish & close to publish the new article and return to the All Articles page.

How to control the visibility of articles

As a content manager, you may want to limit the access to specific content for a variety of purposes:

  • You may want to make the information available only via a support page, where there is enough space to display rich content.
  • The information has business sensitivity, such as closing an account. While offering this article via search for users who explicitly look for this information, you may not want to expose it via navigation and FAQ.
  • There may be content that should be available to agents when replying to tickets but unavailable to external users.

You can set article visibility on the Visibility tab of the Article Editor. By default, an article is visible in all touchpoints. To make it unavailable in a specific touchpoint, deselect that touchpoint. If you want to keep an article in your knowledge base, but not display it at all, turn it offline.

Note: On the right side of the Visibility tab, You can see the articles that link to the currently selected one.
  1. Go to the Knowledge > Articles page in the AI Console and select the article that you want to modify.
  2. On the Visibility tab, select which touchpoints should display the article:
    • Search and Auto-Complete - article is available in search based widget
    • Support Center - article is available in support center
    • FAQ Widget - article is available for use in FAQ
    • Open in widget link -
    • Links from other articles - article is available for use as linked answer
    • Ticketing agent interface - article is available an answer when replying to tickets in the Ticketing > Open tickets menu. The name of the touchpoint where the article is available as an answer is displayed in the top-right corner of the answer as follows:
      • If the answer is available only when you answer an open ticket, a red "Agent Only" label is displayed
      • If the answer is available only in some of the touchpoints, then labels with these tocuhpoints will be presented, offering the agents an insight into why the user has escalated their request
      • If the answer is available in all touchpoints then no special indication is displayed
    • Do not index this article - search engines will not find the article
    • Show article in sitemap.xml - allows search engines to find the article, which is important for SEO purposes. By default, all articles are indexed.
    • Publish on - set a date to automatically publish the article on a future date
    • Expires on - set a date when the article should be unavailable for your customers. The article will be moved to the Knowledge > Expired menu.
    • Permission groups - see How to assign group permissions for articles
    • Lock article - lock the article so that only you can edit or delete it
  3. Publish the article.

How to assign group permissions for articles

You can define permission groups to make an article accessible to only a certain group of users in the AI Console. By doing so, you can essentially assign content managers to specific content types who will not see each other's articles.

Important: This feature is disabled by default. Contact your Customer Success representative for further information

To add a user to a permission group, do the following:

  1. In the AI Console, go to Admin Center > Users and click on the name of a user.
  2. Click the Permission Groups icon at the top of the page:

  3. Click Create group.
  4. Name your group and make sure you select the right Knowledge Base where you want to associate your articles with permission groups.
  5. Click Save.
  6. Click the name of a user to edit it and click Permission Groups at the top of the page.
  7. Make the user the member of a permission group by selecting a group. On the user details page, you see the associated permission groups in the Member of field.
  8. Once you are done, you must also assign articles to permission groups:
    1. Go to Knowledge > Articles and select an article.
    2. On the Options tab, select the Permission Groups that you want to assign to the article.
    3. Publish and close the article.
      Note: You must add articles one-by-one to a permission group.
Once you are done, only users in the proper permission groups will see the article.

How to view or revert to previous article revisions

You can view earlier revisions of an article to check what it previously looked like.
Note: You cannot compare two revisions in the Article Editor.
  1. Go to the Knowledge > Articles page in the AI Console and select an article.
  2. On the Revisions tab, select a version of the article that you want to view.

    The Content tab now displays the selected revision of the article.

  3. To revert to the selected revision, click the Revert to this revision link at the top of the Article Editor.
  4. Publish the article.

How to add notes to an article

You can add notes to an article when you want to provide additional information to other content editors. These notes are related to the article itself and not to the individual revisions.
  1. Go to the Knowledge > Articles page in Bold360 AI and select an article.
  2. On the Notes tab, add your remarks about the article.
  3. Publish the article.

How to style your content

You have the following options to display formatted content to your customers:
  • You can use a full range of fonts to style your article content:
    1. Select the text that you want to customize.
    2. From the Font Name menu, select a font face.
  • You can modify the list style type of bullet and numbered lists:
    1. Right-click the list that you want to modify.
    2. Depending on the list type, click Bulleted List Properties or Numbered List Properties.
    3. You can select the list style from a drop-down list.
  • You can add indentation to any HTML element in an article.

What about that warning about conflicting intents?

If a content manager attempts to add a new title or a new phrase that is similar to a phrase in a different article, a warning is displayed. The user is able to view the article that holds the similar phrase to determine if the two articles need to be consolidated or bypass the warning.

Important: Similar phrases in separate articles may negatively impact the NLP and therefore not recommended.

Featured

Bold360 21.10 Release Notes

Bold360 21.10 release notes

Bold360 version 21.10 contains the following new enhancements:

Enforcing HTTPS and removing HTTP across widget scripts

Going forward, there will no longer be an option to choose (non-secure) HTTP-only connections when generating widget touchpoint scripts. HTTPS will be enforced across all touchpoints going forward and HTTP-only widget configurations will no longer be supported as of December 31, 2021. Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted

Access to the Genesys DX AI management (*.nanorep.co) will only be accessible through HTTPs

In-product announcements will be present to raise awareness of this change

Important: Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted.

In-Product Rebranding

As part of the transformation to Genesys DX, the product interfaces are now rebranded to reflect this change. Logos, product names, and company links are now updated to Genesys branding and is present within each of the product interfaces.

getEstimatedWaitTime API call

Using the "getEstimatedWaitTime" API call will provide the estimated wait time that the visitor would spend waiting before starting a live chat with an agent.

Details on using this API can be located in this article.