1. Home
  2. Concepts
  3. Deploying your Search Assistant
  4. Deploying your Search Assistant

Deploying your Search Assistant

SearchAssist grants access to the folder required for the Web SDK and a test application to run the Search Assistant on your machine as a local host server for testing purposes.

Once the end user experience offered by the Search Assistant meets your expectations you can launch it in your desired channel. 

  1. To get the SearchAssist Web SDK, write to <emailSA>@kore.ai
  2. Extract all files to your local folder
  3. From the SearchAssist Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu, copy the following: (These values needs to updated in the ‘findly-config.js’ file)
    • App Name 
    • App ID
    • Client ID 
    • Client secret ID
    • Search ID
  4. Open the extracted folder, locate and navigate to /web-kore-sdk-private/findly/demo/ folder
  5. Open ‘findly-config.js’  file in any of the editors(Ex:- Notepad++, Visual studio)

Update the botOptions parameters botInfo, clientId and clientSecret, and your emailID as userIdentity. modify the host URLs as per your instance

botOptionsFindly.koreAPIUrl = “Host URL”; (Ex: ‘https://searchassist.kore.ai/’)

botOptionsFindly.baseAPIServer = “”;   (Ex: ‘https://searchassist.kore.ai/’)

botOptionsFindly.botInfo = { chatBot: “”, “taskBotId”: “”};

botOptionsFindly.clientId = “”;

botOptionsFindly.clientSecret = “”;

botOptionsFindly.searchIndexID = “”;

botOptionsFindly.reWriteSocketURL = {

        protocol: ‘wss’,

        hostname: ”  (Ex: ‘qa.kore.ai’)


  1. Save the changes done in the ‘Findly-config.js’ file
  2. Locate and navigate to /web-kore-sdk-private/demo/ folder
  3. Right-click “index.html” file and open with any one of the browsers
  4. End User SDK will be opened with the changes done in the configured Search Assistant
  5. Start the searches in the SDK and relevant results are displayed.
  6. Data searched in the End User SDK (“searches”,”Users”,”Clicks” and “Appearance of Sources data”) are displayed in the Business user portal.

When you host the Search Assistant on a local system, it’s deployed on a given demo website template to demonstrate functionality and lets  you evaluate how it  performs on  your content. 

The UIs customized in the SearchAssist platform as a Business user can be viewed once the Search Assistant is hosted with the SDK or in the Test mode prior to launching. 

Note: If the Search Assistant is running in a local box, to validate it the following steps are mandatory

  • We need to run SDK in chrome browser in security disability mode to allow the Cross-Origin Resource Sharing (CORS)  
  • For that open windows run command and paste chrome.exe –disable-web-security –user-data-dir=c:\my-chrome-data\data
  • Hit enter chrome will be opened in disabled security disabled mode paste the index.html path here to run the sdk

Passing data via webSDK

Pass additional information of the user accessing the channel by adding the custom data at botInfo inside the SearchAssist-config.js file.
botOptionsFindly.botInfo = { chatBot: “<App Name>”,
    “taskBotId”: “<App ID>”,
} };
botOptionsFindly.botInfo = {chatBot: “<App Name>”, 

                            “taskBotId”: “<App ID>”,


Commonly Encountered Errors

  • A wrong URL is given in index.html, users see a 404 error. Double-check the URL. URL changes depending on whether you are hosting the bot on your own web SDK or on SearchAssist’s web SDK.
  • Not found: User sees this error when either wrong clientID or no clientID is given. Check the correct ClientID from Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu
    botOptions.clientId = “{clientID}”; provide secure client-id

error verifying the jwt: the Wrong clientSecret is given in index.html: Check the correct clientSecret you get from Business Portal -> Manage -> Web/Mobile Client Channel page on the Channels menu
“clientSecret”: “{clientSecret}”; provide clientSecret here