Website widgets: support, comments and private access
A project brings together a website, a team and the settings for communicating with visitors. The support widget accepts a private request, while the comments widget hosts a discussion of a specific article, product or task. This guide covers the whole path from installation to a closed CRM; the exact server requests are in the library and comments API guide.
For developers: the full guide to installing the widget, JavaScript events and Yandex Metrica goals.
Creating a project and installing the widget
In the "Projects" section, enter a name and your site's domain, for example
example.com.Create the project and select it in "My projects".
Click "Copy code" and paste it into your site before
</body>. If your site runs on a website builder, pass the code to your developer or add it through the custom code setting.Open your site, click the chat button and send a test message.
Find it in "Requests" by selecting this project.
Your site must open over HTTPS. Enter the exact domain: example.com and www.example.com are added separately. For additional sites, use "Add site" inside the project and copy the code of the selected site.
What you can configure in the widget
Open the project, select a site and find "Widget settings". After making changes, click "Save settings". They take effect the next time the site loads.
Show widget — show or hide the chat on your site.
Title, greeting and button text — what visitors see before the conversation starts.
Color and position — appearance and which side of the screen it sits on.
Open automatically and delay — show the window after a set number of seconds.
Width and height — the initial window size.
Customers can choose a department — let visitors choose who to address their question to.
reCAPTCHA protection — a check before a new guest conversation is created, if it's set up.
During a conversation, visitors can move the window by dragging its top bar and resize it by dragging a corner. The position and size are remembered in that browser.
Visitors can write without signing up or sign in with Sensever. Guest access is granted for 45 days and is extended with activity; clearing browser data can cause a guest to lose access. The team keeps the history. To continue on another device, sign in with Sensever.
Your personal feed and widget notifications
You configure what appears in your main feed and which notifications you get in chat: the filter next to "Create" → "Feed settings". "On home" shows or hides the selected widget's requests in the main feed. "Quiet" turns off sound and message notifications while keeping unread messages and their counters. After choosing, click "Save".
These settings belong to your account, apply on all your devices and don't change the widget for visitors or your colleagues' notifications. A site widget and a Telegram bot connected to the same project are separate sources: each can be shown and made quiet independently. New conversations inherit the source's settings; hidden ones are available in the "Requests" tab.
More details: Chats, contacts and messaging in Sensever — feed settings
Support widget: sign-in, guests and contact options
The support widget is a floating window for sending a request to a project. If a valid Sensever session is available to the widget, it opens the conversation on behalf of that account right away. A guest sees a choice of the available contact options. Signing in to a third-party site is not, by itself, signing in to Sensever.
Why you're asked to sign in again
On a third-party site, the browser may not pass Sensever cookies to the embedded iframe. In that case, an explicit sign-in with Sensever is available. An expired or revoked session also requires signing in. This is different from the secure server-side authorization of a private comments block.
When a request is created
For a signed-in user, the connection is made when the widget is opened. Loading the page in the background doesn't create a request. When the widget is opened again, the existing conversation is used rather than a new chat.
Chat or comments
The floating widget creates a support request. Comments are a separate block under a product, article or task, tied to the content type and ID. Choose the format your site needs.
Comments on your site and AI
To add Sensever comments, create a project with your site's domain, open its "Comments on your site" section, turn on comments and copy the ready-made installation code to the right place on the page. This is a separate block for discussing content, not the floating support request widget.
In the installation code, data-site identifies the project, data-entity-type the content type and data-entity-id its permanent identifier. Pass different identifiers for different content. The page URL and title serve as a description and can change without creating a new thread. data-lang sets the widget language.
For a closed site or CRM, choose private mode and set up data-session-url: your server verifies the user and their access to the content, then issues a limited comments session through the server-side integration. Never put the secret server key in HTML or browser JavaScript. The public data-site key doesn't replace server-side access checks.
The comments block has no AI replies. The AI assistant answers in the support widget, on the contact page and in connected messengers: set it up in the project's "Assistant" section, as described in AI chat for your website. Ticking knowledge base channels doesn't by itself turn the assistant on: that is the "Virtual assistant" switch.
Private comments for a CRM or closed site
A private comments block gets access from your server: the CRM verifies the visitor and their right to a specific content item, and Sensever issues a short session for that discussion only. Placing a public widget on a closed page isn't enough for this kind of protection.
What data the CRM sends
The server sends the user's permanent ID in its own system, a display name, the content type and ID, the site origin, the permission to write and the session lifetime. The server key is stored only on the server. You don't need to pass the CRM user's password to Sensever.
What Sensever protects
The session is bound to the site, origin, participant and thread. Copying the HTML to another domain doesn't grant access to the private history. Your site decides who can open the content; Sensever checks the limited permission it issued whenever the comments are accessed.
Does privacy mean mandatory sign-up
Privacy means having permission, not necessarily a personal Sensever login. The server-side integration can represent an external CRM user. This doesn't hand the project owner's account over to them.
Reading and joining a discussion
Viewing a page and getting a widget session don't create a discussion and don't subscribe the reader to it. Until the first message is sent, thread_id in the response may be null. Existing comments can be read with a valid session without the discussion appearing in personal chats. Participation starts once a comment is sent. When a file is sent, a technical thread is reserved for the upload, but the reader becomes a participant only after sending a message.
Comments