List of current available callbacks

Building the mind for your business

List of current available callbacks

All of the following callbacks are called with a required first parameter and may have additional parameters. The required first parameter that we pass to all callbacks when calling them has this structure:

   conversationId: string,
   createdAt: Date

Any additional parameters will be listed in their own callback


Executed when the widget is finished initializing


Executed when the widget is minimized


Executed when the user escalates (either via escalation or via handover). This callback receives an additional second parameter containing the message of the escalation/handover. The structure of the parameter is the following:

	actions: array 
	aspect: string,
	text: string

The different aspects can be:

In the event of a titlebar escalation, actions & text won’t exist.


Executed when the widget opens (normally when the user clicks on the FAB)


Executed just before we try to connect to the websocket. This connection is not established if the user does not open the widget.


Custom callbacks must be added after our widget has loaded.

Notice how we add our callbacks after the event load of our script is called.

  <script id="dialpad-widget">
      window.GLR = {
        appId: '190931b6-d139-4c2b-a3ff-144ad89bc38a'
      (function(w, d, s){
        var j = document.createElement(s); j.async = 1; j.type = 'text/javascript'; j.src = '';
        w.GLR = w.GLR || {};

        j.addEventListener('load', () => {
          kare.onLoad(function(callbackEvent) {
            console.log('my custom onLoad callback');
          kare.onClose(function(callbackEvent) {
            console.log('my custom onClose callback');
          kare.onEscalate(function(callbackEvent, messageBody) {
            console.log('my custom onEscalate callback');
          kare.onOpen(function(callbackEvent) {
            console.log('my custom onOpen callback');
          kare.onBeforeSocketOpen(function(callbackEvent) {
            console.log('my custom onBeforeSocketOpen callback');
      })(window, document, 'script');

Keep in mind the browser compatibility you want to provide your users when using this method to trigger your own callback.

We don’t manipulate the code inside the callback in any way.