Screen broadcast

Viewing the visitor’s screen allows you to help your users more quickly and efficiently. Consultants can get access to the visitor’s screen, see the website exactly as a visitor sees it and pay attention to important details.
The consultant cannot operate the page while watching a visitor’s screen. The consultant cannot scroll the page, type in inputs or copy information from the page. This is done for security reasons for user data.

Screen broadcast FAQ

Question:
Are there any restrictions for screen broadcasting?
Answer:
Yes. Unfortunately, not all browsers provide the required functionality to perform screen broadcasting. If a visitor’s browser does not support the required features, the consultant gets an error message in the dashboard.
Question:
How fast does screen broadcast works?
Answer:
It works as fast as it is possible based on visitor’s and consultant’s Internet connection. We are doing our best to provide the highest connection speed, including data compressing.
Question:
What exactly is transferred while screen broadcasting?
Answer:
First, we transfer the whole page HTML markup, then SDK tracks page changes and transfers small patches only. Also, SDK tracks window size changes, page and block scrolling, cursor movings, keyboard inputs, and mouse clicks.

SDK does not transfer scripts, passwords (input[type="password"]) and hidden blocks (class="ym_disable_keys").
Question:
Why page styles do not load in the consultant side?
Answer:
Due to browser security policies, you are required to configure your web server to provide additional response headers. Otherwise, the browser blocks requests for styles. Read more about that in section Displaying CSS styles.

Hide blocks from consultants

Use class ym-disable-keys
The content of the block with this class will not be transferred to the consultant, he will see a placeholder at this place, telling him that this block is hidden.
<div class="classname1 classname2 ym-disable-keys">
This block will be hidden. There could be sensitive information in this block, e.g. bank card number, security codes, personal information, etc.
</div>

Displaying CSS styles

Allow cross-domain requests
Due to the fact, the consultant is at the Chatix dashboard while watching visitor's screen at app.chatix.io and style file can be located at your web server at mysite.com, a single-source policy violation (same-origin-policy) occurs. Browser security policies do not allow load styles from other domains, unlit it is allowed. You can read more about that in article Cross-Origin Resource Sharing (CORS).
In a nutshell, you have to add these headers to your web server responses. Please, refer to your web server documentation.
Access-Control-Allow-Origin: https://app1.chatix.io
Access-Control-Allow-Methods: GET, OPTIONS
Access-Control-Allow-Headers: Content-Type