This content has been archived.

Table of Contents

Handling the user identity in a Web Chatbot interaction

Pega Customer Service ships a sample identity as a test account to test end-user authentication in Web Chatbot. When the authentication is validated, the chat case is escalated to the customer service representative and the customer is recognized.

The following steps suggest how you can use the sample identity with the cookie for end-user authentication. You can choose to use your own logic for this mechanism.

  1. Log in to the Web Chatbot configuration portal.
  2. Configure and download the Web Chatbot .zip archive files.
  3. Extract the files into your system. The .zip archive includes the following files:
    • PegaHelper.js – A JavaScript file with functions that help to perform Web Chatbot functionality.
    • PegaHelperExtension.js – A JavaScript file focused on identity management, allowing customers to read identity (contact and account numbers for example) from a local cookie. This cookie is configured before the chatbot is initiated (on DOM load).
    • PegaStyle.css – A style sheet with all defined styles.
    • Index.html – The HTML file that displays on the deployed Web Chatbot portal.
    • ReadMe.txt – A README file.
  4. Replace the functionality in the PegaHelperExtension.js file to read a cookie or inject an identity from the calling page that maps to how your business manages and persists authenticated users across your website and how it associates them with Pega Contact and Account records.
The sample identity within the cookie created by the PegaHelperExtension.js file assumes that the sample data is used.
Suggest Edit

0% found this useful

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.