Introduction

This document will guide you through the steps to integrate Surfly into your CXOne platform.

It includes the following sections:

Studio Implementation
Step by step, all the changes needed on your current Studio scripts in order to integrate Surfly into your CXOne platform.

Javascript Integration File
How to generate the Javascript file that you need to include in your website in order to use Surfly with CXOne.

 

Integration Testing
All the steps necessary to test and troubleshoot your integration.

 

User Flows
All the available user flows that we offer with this integration, and all the things you can do with Surfly.

 

Studio Flow Description
In depth explanation of the Studio flow, and how it communicates with the Javascript file.

Before You Begin

You will need:

  • Our Studio scripts
    on_call.xml: used for the phone flow
    on_chat.xml: used for the CXOne chat flow
    on_chat_salesforce.xml: used for the CXOne chat flow (Salesforce app)
    IB_Video_WI.xml: used for the videochat flow
    Surfly_Signaler.xml: used to trigger the OnSignal branch of the chat script
    generic_script: used for displaying the Surfly launch bar

  • Your Scaledrone Channel ID and Authentication token

  • Your Surfly’s widget key
    - Log in into https://app.surfly.com
    - Go to Settings → Integration → Widget Key

  • Your Business Unit (BU) number

  • Access to Studio and the CXOne platform

CXOne Chat Flow Integration

Flow Description

This flow allows an Agent to send a co-browsing invite to a customer using the CXOne chat.

The Agent will be chatting with the customer through the CXOne chat. The customer may be stuck on the website, or may need help to fill in a form or complete a purchase.

The agent will click on the “Send Co-browse” indicate:

After the user consents, he/she will start a cobrowsing session and the agent will join in.

Script

Import the on_chat.xml file into Studio. You can save the file if you don’t have any chat scripts in your environment yet. Otherwise, you will have to integrate the script’s flow into your current one, as described below.

The file should look like this:

Begin Branch

Add the uniquePageId to the list of parameters. If you already have any parameters on your list, make sure that you add uniquePageId as the last one.

Append the ReqAgent Skill NiC Chat and Assign Script Variable actions to the end of your existing Begin branch.

Enter your ScaledroneID and Scaledrone Authentication Token values on the Assign Script Variables action’s data field.

The uniquePageId value is a unique value generated by the Javascript file (see Javascript Implementation File) on the customer’s browser. It’s passed to Studio and used to identify each customer that initiates a CXOne chat session, and to identify the recipient of the Scaledrone message that will start the co-browsing session triggered by the Agent (see Chat Flow)

The Scaledrone variables configured in the Assign Script Variables action will be later used in the OnSignal Co-Browsing branch to call your Scaledrone channel.

OnAnswer Branch

Append all the actions after the OnAnswer action to your existing OnAnswer branch, as shown below:

On the Set Security User action, select a user that has Admin privileges.

This branch will attempt to check if the current CXOne Agent is registered in Surfly’s database. The GetPage Agent Token action will make a call to Surfly to check if the Agent exists. If it doesn’t, the account will be created using the Agent’s first and last name and email (see Assign Agent Variables action).

Then the Agent token will be returned, and the “Send Cobrowse Invite” and “Send Videochat Invite” indicators will be displayed in the Agent’s MAX option’s bar.

OnRelease Branch

Add the OnRelease Chat Ended branch to your setup, or append all the actions after OnRelease Chat Ended action to your existing branch.

This branch is to make sure that the  “Send Cobrowse Invite” and “Send Videochat Invite” indicators are no longer displayed once the chat session has ended.

OnSignal Branch

Add the OnSignal branch to your setup, or append all the actions after OnSignal Co-browsing Chat Ended action, to your existing branch.

NOTE: If you already have an OnSignal Branch with your own routing, follow this additional steps: 👇

In order to distinguish that the request made to Onsignal comes from your original flow, you can append a new value (for example “client“) to the existing ActionValues of the client’s indicators:

Then add this value at the end of the parameter list of the OnSignal Action. Please note that In the previous image, the first passed value {ContactId} is NOT considered parameter[0]. This first value is ignored and “NA“ would be the parameter[0].

Finally, add an IF action after the OnSignal Co-browsing action to check if the indicator sent the “client“ value as the 5th parameter. If it is, go through the new flow that we created for Surfly. Otherwise, continue with your branch's original implementation.

CXOne Videochat Flow Integration

Flow Description

In this case, the customer can request a video chat session with an agent by clicking the “Start Video chat” button.

The agent will see the request on the CXOne agent like this:

Once the agent accepts the request, he/she will join the customer in a video chat session.

Studio Script

Implement the chat flow as described in the previous section. You will need the chat script for this flow as well.

Work Item

Create a Videochat skill that has its Media Type set to “Work Item”.

Create a Videochat Point of Contact and set its Media Type to “Work Item”.

Import and save the IB_Video_WI.xml file into Studio. The file look like this:

Begin Branch

Append all the actions after the Begin action to your Begin branch.

Change the skill of the Skill action to your videochat skill.

OnAnswer Branch

Append all the actions after the OnAnswer Accept Chat action to your current OnAnswer Accept Chat action. 

OnRelease Branch

Add the OnRelease branch to your setup, or append all the actions after OnRelease action to your existing branch.

OnSignal Branch

Add the OnSignal branch to your setup, or append all the actions after OnSignal action, to your existing branch.

CXOne Phone Flow Integration

Flow Description

While in a phone conversation with a customer, an agent may want to assist him/her on a part of the website.

The agent will type the address he/she wants the Surfly session to start cobrowsing from, in the Surfly launch bar.

 

Then he/she can send the session invite link to the customer via email (or any other channel) so he/she can join the session.

Phone Script

Import the on_call.xml file into Studio. You can save the file if you don’t have any phone scripts in your environment yet. Otherwise, you will have to integrate the script’s flow into your current one, as described below.

The file looks like this:

Begin Branch

Append the ReqAgent Skill NiC Chat to the end of your existing Begin branch.

OnAnswer Branch

Append to your existing OnAnswer branch, all the actions after the OnAnswer Accept Call action, as shown below:

On the Set Security User action, select a user that has Admin privileges.

OnRelease Branch

Add the OnRelease Call Ended branch to your setup, or append all the actions after OnRelease Chall Ended action, to your existing branch.

OnSignal Cobrowsing Disabled Branch

Add the Onsignal Co-browsing disabled branch to your setup, or append the Messages Co-browsing not available action, to your existing branch.

Surfly Signaler 

If you are implementing either the CXOne Chat or Videochat flows, make sure to import and save the Surfly_Signaler.xml file in the root folder.

 

 

We will call this script  from our Javascript file, and the signaler will call the chat script and continue the required flow to start the session on the Agent’s side.

If you are implementing the Video chat flow, don’t forget to set the appropriate Point of Contact value on the Queue WI action:

Surfly Launch Bar

If you want to include the Surfly launch bar in CXOne, you need to import and save the generic_script.xml file into your Studio environment.

The file will display the appropriate indicate in the “Launch” menu to display the Surfly launch bar.

Go to ACD → Script Schedules → Create, and create a new schedule to execute the script for the first time. 

Select the generic script from the script list and “One time” as the schedule type.

Set the “Starts On” time to 15 minutes from your current time (this is the earliest that CXOne allows), and wait for the script to execute.

Once it does, you should be able to see the indicate on the “Launch” menu to display the Surfly launch bar.

Integration Javascript File

Here we describe how to generate the Javascript file that will launch the CXOne chat on your website, and will allow Surfly to communicate with the Studio implementation done in the previous steps.

You should include this file in any webpage you wish to start the CXOne chat from.

When you include the script in your page, it will generate the Live Chat and Start Videochat button.

The next steps describe how to generate some of the URLs and values needed for the Javascript file to work. 

At the end of this section, you can enter these values and generate your Javascript integration file.

Go to ACD →  Contact Settings → Scripts → Surfly_Signaler → Spawn. 

Select the chat skill that you will be using for this integration. Click “Show Shortcut“ and copy the URL in the “Shortcut to Surfly Signaler“ link. This is the Signaler Spawn URL that you will be using in the Javascript integration file (see JS file generator below).

Repeat the same process if you will be using the videochat flow. But in this case, select the Videochat skill you created in previous steps. 

NiC Chat Point of Contact URL

Go to ACD → Contact Settings → Points of Contact → (your chat point of contact) 

Copy the Point of Contact URL as shown here:

Generate Javascript File

Use this page to generate the Javascript file: https://nic-js-generator.herokuapp.com/

Testing the Javascript File

To test the JS file you just generated, just copy and paste its content in your browser’s console and press Enter to execute the script.

You should see the Live Chat button appearing on screen:

Check for any errors that might show up in the console. 

Open a MAX instance on another browser and take the call of the waiting user. Try launching a co-browsing session by clicking on the “Send Cobrowsing Invite”.

The customer should see this popup modal with the following message: