When adding or editing your Co-Browsing module, the following can be configured:
Choose whether you want to save or not save recordings of your Co-Browsing sessions. Some countries require companies (esp. banks) to have every customer interaction documented for audit reasons.
Allow agents to join sessions
Mask user inputs
All inputs of users are masked. Password fields are masked in any case - regarding that no configuration needed. Masked for Chatvisor means, that all characters are replaced with '*' and therefore unidentifiable for the agent.
Note: Masking with Chatvisor actually means that data is excluded from data transmission. Excluded means, that the potential sensitive data will at no time be captured and transferred from the client side anywhere else. Further it needs to be emphasized on the fact, that the validation whether data is sensitive or not entirely happens on the client side, which again implicates that sensitive data will at no point be transferred.
Mask all digits.
All website content is masked. Every text field, input field - literally any type of content. Use "Mask Content" with Whitelisting to de-mask content where you are sure that it does not contian any PII (Personally Identifiable Information).
Store and show the IP address of visitors
Store and show the IP address of visitors. By default, Chatvisor does not store any IP addresses (recommended). Please note, that the IP is considered as PII.
Using HTML/CSS selectors you can select and mask content without needing to alter any your code.
|Blacklisting||Mask selected content.|
|Whitelisting||De-mask selected content. Best practice when handling lots of personal data and displaying it on your website - use "Mask Content" to mask everything and whitelist where you are sure that no PII is included.|
To mask certain CSS classes, use '.' + "your-css-class", to mask HTML e.g. add a 'p' (without apostrophes) for
Transfer only with XHR
When your infrastrucure, your setup is protected by a firewall that disables all WebSocket connections, you need to enable this option to make sure there's a constant connection between Chatvisor and your website/platform. Typically, WebSockets are our preferred way of connection because they provide a faster connection - using XHR works fine though, too.
Shadow Dom Prefix
Keep session for different domains
In case you have a multi-domain page or use subdomains, we need you to specify those to ensure a continous Co-Browsing experience. If not configured, a Co-Browsing session will be disconnected through the page switch. In order for Chatvisor to understand that a session continues on another domain or subdomain, we need you to specify.
In this section you can configure how active your agents can be during a Co-Browsing session (in the Agent View). There are three complementary, but from each other independent options:
- Allow bidirectional interactions
Allow agents to guide and navigate customers. By activating this toggle-slider, agents will be able to scroll and click on behalf of the customer.
- Disable Drawing
By default, agents can give visual hints to customers with the drawing function. This can be disabled.
- Disable mouse
By default, agents can share their mouse cursor position with customers to guide them, but not click or scroll for them. This can be disabled.
Default Optin UI
The yellow marked configuration will add a widget to your page, that allows users to start a optin and Co-Browsing session.
Default UI when Co-Browsing activated
Recommended! When activated, this setting will add a yellow frame around the shared website session indicating customers exactly, what they shared. Further it will add a small widget on the top right, where customers can end the session and see their Session Id. Through sharing their Session Id, agents are able to start Co-Browsing, read more: Agent View
Using our REST API, you can fully customize your opt-in process and alter it according your corporate design.
Allow customers to share their session on your website with their peers. Provide customers with a Co-Browsing link they can share. For further configuration and implementation, take a look at our REST API Docs.