Installing chat for multi-broker & enterprise web sites

Enterprise Installation

For greater control over how chat conversations are assigned, follow the steps below. For hands on help with enterprise installations, schedule an installation consultation by emailing support@dotsignal.com.

 

Required Parameters. DO NOT CHANGE THESE VALUES.

_dschat.rootURL = location.host;

_dschat.pageURL = document.baseURI;

_dschat.pageTitle = document.title;

 

Forcing Conversations to Specific Teams

zipCodes, optional

teamID, optional

There are two ways to force a conversation.

  •  zipCodes – will identify all teams that service the defined zip code and randomly assign the conversation to one of the teams.  zipCodes will be ignored if teamID or mainTeam/backupTeam are defined.
  • teamID – will immediately assign the conversation to the specified team.

 

 _dschat.zipCodes = [84094,84121,...];

 _dschat.teamID = 7;

 

Forcing Conversations to a Specific Agent User

userID, optional.

Defining the userID will assign the conversation immediately to the userID defined. If the user does not claim the conversation, the ‘zipCodes’ parameter will be used to identify a team, unless ‘teamID’ has explicit been defined.

 _dschat.clientID = 63321

 

Target Code

targetID, optional

targetID is a unique identifier that  can be set as a way of correlating conversations back to objects within 3rd party systems.  For example: you could set the targetID as the MLS # of a property to be able to report on the number of conversations that originated while on the property detail page of a given property.

_dschat.targetID = 'p123456';

 

Dynamic Conversation Assignments

For enterprise web sites that prefer to control conversation routing dynamically, please reference the documentation below.  The following documentation will provide instructions on how to bypass preconfigured teams and dynamically control how conversations right within your code base.

Defining the Main Team

If teamID (above) is defined, mainTeam will be ignored.

 _dschat.mainTeam = {

userIDs : [1,2,3,4,5,...],

Comma separated list of userIDs to notify and potentially claim the conversation    

batchSize : 2,

number of users to notify in each attempt   

timeout : 10,

The number of seconds to claim a conversation before attempting another batch of users from the defined userIDs.

reassignTimeout : 30,

how long the assigned user has without activity before prompting the consumer if they would like to chat with a new user.

attempts : 2,

how many times to notify agents from this pool

 

 };

Defining the Backup Team

If teamID (above) is defined, mainTeam and backupTeam will be ignored.

_dschat.backupTeam = {

userIDs : [1,2,3,4,5,...], 

Comma separated list of userIDs to notify and potentially claim the conversation    

batchSize : 2,

number of users to notify in each attempt   

timeout : 10,

The number of seconds to claim a conversation before attempting another batch of users from the defined userIDs.

reassignTimeout : 30,

how long the assigned user has without activity before prompting the consumer if they would like to chat with a new user.

attempts : 2,

how many times to notify agents from this pool

};

 

Calling the Chat function

(function(){   

var dschat = document.createElement('script'); dschat.type = 'text/javascript'; dschat.async = true; dschat.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'chat.dotsignal.com/js/injectChat.js';    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(dschat, s);

})();

 

 

 

 

Have more questions? Submit a request