Kbot is designed to leverage your Snow environment configuration. It improve the ServiceNow customer experience and is not aimed at duplicating information that is already defined in Snow. This page describes how you can get the best experience by configuring to configure your environment.

Info

This content is targeted to the administrators who are familiar with the ServiceNow concepts. In particular, we will cover OAuth2 authentication, portal links, and sys_class_name.

...

Configure the Snow OAuth2 authentication, so the users are authenticated by same principle as in the Snow platformcan authorize easily. To make Kbot propose the Snow authentication to users, you must register it:

...

2. Navigate to the System Oauth section in the menu on the left side of the window (or use the search field) and click Application Registry to create a provider.

...

Once you have finished the provider configuration, collect the you can obtain Client ID and Client secret.

...

To enable the live chat, define the Queue you plan to use. This can be done with a the setup of the following kind:

...

Once it is done, you need to define a few triggers. The Konverso team will send you the code. Please send a request to contact@konverso.ai, so the Konverso team will send you the code.

Portal widget

We recommend adding Kbot as a widget inside the Snow portal. To do so:

  1. Create an application inside Kbot for your new view. Call it ServiceNow (for as an example) and enable only Snow OAuth2 there.

  2. Create a widget inside Kbot and configure the display parameters to fit your needs.

  3. Copy the widget code inside the portal.

Users are prompted for the authentication once; then their to authorize once; after it is done, they do not need to log in. The authentication token is refreshed automatically.

...

.