Listen to this event emitter to override the default remote control acceptance prompt.
When you have gained confirmation from the user, you should call Session.setRemoteControl
and pass either RemoteControlState.on or RemoteControlState.rejected to approve or reject
the remote control request.
Listen to this event emitter to override the default session acceptance prompt. The session
passed to this method will be in the SessionState.authorizing state, when you have gained
confirmation from the user, you should call either Session.activate or Session.end
to approve or reject the session.
Listen to this event emitter to override the default session indicator. This method may be
called several times as the session progresses through its lifecycle, so you may need
to adjust your UI accordingly. See the available sesssion methods to inspect session state.
Note you should also listen to CobrowseIO.hideSessionControls if you are implementing
this feature.
Creates a new screenshare session. Sessions will start in a 'pending' state. To activate a
session an agent must have joined and all required consent given by the user. Pending sessions
contain a six digit code that can be displayed for the user to give to a support agent.
Gets the current screenshare session. This may be a session waiting to start, the currently
active session, or may be null if no session has been created.
Fetches a session by its ID or by a 6 digit code. When loaded the callback will be invoked
with the session object, or an error if the session could not be fetched.
Sets the available capabilities for a session. Different annotation tools and events will
be available during a session depending on the capabilities you set here. By default all
capabilities supported by the device are enabled.
Sets metadata attached to this device that will be displayed and filterable in the web
dashboard. This allows you to find and identify your users devices quickly. We recommend
adding information such as your logged in users email addresses or user IDs here.
By default, when the SDK starts it will register the device to your account and share its
connectivity state. This provides the dashboard with a list of devices which are online
and ready to connect.
Call start() when you have configured Cobrowse and would like to start accepting incoming
session requests. Calling start will register the device into your cobrowse dashboard and
open a socket to accept incoming connection requests from your support agents.
Stops Cobrowse, de-registering the device from the server and closing any open connections.
After this method has been called you can no longer start sessions either via the dashboard,
or via a 6 digit code, until Cobrowse has been started again.