Chats, contacts and messaging in Sensever
Sensever brings direct conversations, groups, channels and content discussions together in one interface. This guide helps you choose the right kind of conversation, find a person, send your first message and set up a comfortable way of working with your conversations. Start with the scenario you need in the table of contents; instructions on serving customers are in a separate support guide.
What kinds of chats Sensever has
There are five main scenarios for users: a direct chat, a group, a channel, a support request and a discussion under a content item. Choose by task: talking to a person, team communication, publishing content, helping a customer or commenting on a specific object.
A topic isn't another separate kind of chat: it splits the messages inside a conversation by subject. Public, private and link-only describe access, not what a conversation is for.
Direct chat: message one person
A direct chat is for a conversation between two people. Find the person by name or @username in chat search and choose them from the global results. You can also open a conversation from your contacts. You don't need to create a group or project first.
Direct chats have no topics. Contact circles help you organize your list of people, but they don't turn a direct chat into a shared chat and don't change what the other person can access.
Group: talk together
A group suits a team, friends and joint discussions. Unlike a channel, it's meant for shared conversation among members. Whether you can send messages, invite people and manage the group depends on your role and the group settings.
For a busy conversation you can use topics: separate subjects within the shared conversation. Membership and access settings still belong to the group. A group doesn't replace a support project if you need agents, request routing and a customer queue.
Channel: publish content for an audience
A channel is for the team to publish and for followers to read. A content item can be an article, a video, a gallery or another supported content type. Content authorship and the publishing channel are different properties: in a channel, content is posted on behalf of the channel, and the authors are listed separately. Content from Studio is published only to a channel — it has a single address of the form sensever.com/<channel>/<content>.
A channel has a page with a description and its content. Content is split by type, and the owner can organize it into categories. The article structure helps readers navigate documentation; you don't need to create a separate copy of articles in a special "knowledge base".
A regular follower doesn't become a channel editor. To discuss a specific content item, use its comments; for free-form shared conversation, a group is a better choice.
Request: a customer's conversation with a project team
A request appears in the support scenario through a website widget. The customer talks to the project, and employees work with that conversation in the "Requests" section. This lets you reply on behalf of the organization, assign an agent and pass the question between employees.
Request statuses are "New", "In progress", "Closed" and "Spam". Viewing doesn't mean taking the request. An enabled AI can reply until an agent joins; an explicit assignment or a human reply stops the automatic answers.
Internal notes are for the team and aren't shown to the customer. They don't replace a regular reply to the visitor. Agents get access through the project, not by adding each customer to their personal contacts.
Discussion: comments on an article, task or page
A discussion ties a conversation to a specific content item or object: for example, an article, a Flow task or a website page with a comments widget. The comments in the widget and the accessible conversation in the "Discussions" section are the same conversation.
From the discussion info you can go to the source page if it has an address. The title and link help you understand the context, but they don't replace the object identifier or access checks.
Viewing a page with comments shouldn't by itself add a separate discussion to the reader's list. For closed objects and a private site, access depends on the corresponding permissions; placing the widget on a hidden page doesn't make a public chat private.
Topics vs. content categories
Topics organize the messages of a conversation. When you open a group with topics, its topics appear in the left column: choose a topic to read and write in it; "All messages" shows the shared feed. Unread messages are counted per topic, so reading one topic doesn't mark the others as read. The group's owner and admins create topics in the group settings, and each member can set a topic's sound from the row's context menu. Details: Topics in groups: the topics column, creating topics and topic sound.
Categories organize a channel's content, such as documentation articles. This is a navigation tree nested up to four levels deep. H2 headings inside an article divide the article itself into sections. A chat topic, an article category and an article heading serve different purposes.
Public and private
A public channel is for content open to the audience; private access requires permission. Having a link doesn't by itself lift restrictions. Whether a specific content item is visible depends on the access rules applied to it.
The history visibility setting for new members controls access to messages sent before they joined. A new member not seeing old messages doesn't necessarily mean they were deleted. In a closed widget discussion, the right to enter must be confirmed by the site's integration.
Which scenario to choose
To message someone you know — a direct chat. To discuss work with several people — a group. To publish articles and instructions — a channel. To take questions from your website — a project with a support widget and requests. To collect responses under a specific article or task — a discussion through comments.
Sensever uses its own channel for official documentation. The virtual assistant reads the permitted published articles of this channel by structure and section; this doesn't give it access to all personal chats and customer projects.
How to find a person in Sensever
Open "Chats" and type the person's name in the search bar above the conversation list. Start with at least two characters. Search first shows matching conversations, and below them the global search results. In global search you can find a user you haven't talked to yet. Click their row to open a direct chat.
If you know the username, search by @username. A query with @ searches usernames only, while plain text also matches display names. Check the spelling or type more characters if there are many matches. Don't confuse a person with a channel or group of the same name: they have a different result type.
How to add a contact and message someone first
Open "Chats, contacts and messaging in Sensever" in your profile, click "Add contact" and enter a name or @username in the "Find user" field. Choose the right person from the results. Once added, you can open your direct chat with them.
Adding someone to your contacts isn't required to start a conversation: you can open a chat straight from global search in chats. Contacts let you keep people in your list and sort them into circles.
Why you can't find someone
Make sure you've typed at least two characters, and check the name and @username with the person. They must have opened Chat with their Sensever account at least once. Guest website visitors don't appear as regular users in global search.
Search doesn't show your own account and may hide a user who has blocked you. An empty result doesn't by itself prove you've been blocked. Searching by name or @username isn't a search of your phone book, phone numbers or email addresses. Don't give the assistant other people's personal data in the hope of finding an account.
How to organize contacts into circles
Create circles, for example "Colleagues" and "Friends". On a contact, open "Circles" and check the lists you want: one person can belong to several circles. Choosing a circle helps filter your list of direct chats. You can also add the other person through the conversation info.
Circles are visible only to you. The other person isn't notified when you add them. Deleting a circle keeps the contacts, and deleting a contact keeps the conversation. A circle doesn't by itself grant access to private articles, channels or tasks.
Feed settings: what to show on home
Open the filter next to the "Create" button, choose "Feed settings", set the toggles you need and click "Save". The settings are personal: they're saved for your account on all devices and don't change your colleagues' feeds.
This chooses what goes into the main feed; it isn't sorting. Conversations are still ordered by latest activity. You can choose conversation types, contact circles, individual website widgets, messenger connections, and Sensever groups and channels. Conversations hidden from home stay in their tabs; access, membership and read status don't change.
On home and Quiet: independent settings
"On home" controls whether a conversation appears in the main feed. "Quiet" mutes message notifications: no sound, no pop-up notifications and no push. Unread messages and their counters are kept. You can keep a source on home and make it quiet, or hide it and keep its notifications. Hiding alone doesn't turn off notifications.
Quiet mode applies only to you and covers new conversations from the selected source. It doesn't turn off messages to visitors or your colleagues' notifications. Call settings aren't included here. Quiet mode for a category, circle, source or the conversation itself adds up: if at least one of them is on, messages arrive without notifications.
Circles, groups and channels in the main feed
To see direct chats only from selected circles, turn off "All direct conversations" and turn on "On home" for the circles you want. Multiple circles are combined. If you leave "All direct conversations" on, choosing a circle won't limit your other direct chats. There's a separate toggle for requests from new contacts.
Individual groups, channels and request sources have their own visibility toggle: an explicit setting on a source overrides the general setting of its category. For example, you can turn off "All Sensever channels" but keep one selected channel. New sources inherit the category setting.
"Default" on a source resets its own visibility and quiet mode settings. The general rules apply again; if the category is already quiet, resetting an individual source won't turn its notifications on.
Website widget and Telegram: separate request sources
A website widget and a Telegram bot connected to a project are different sources. For example, "Sensever" may stand for the website widget and "Sensever Telegram" for the Telegram connection of the same project. You can set "On home" and "Quiet" separately for each. Turning off one source doesn't turn off the other.
A Telegram connection in the requests section isn't a Sensever channel for publishing articles. Sensever channels are set up separately. Go by the source's section and the project name shown under it.
Message requests and new direct requests
"Requests" is a separate tab for new direct requests: the person isn't in your contacts, wrote to you first, and you haven't replied yet. These are personal messages, not requests from widget visitors or a project's Telegram customers.
The "Show new direct requests" toggle controls whether they appear on home. It's off by default, but message requests are always available in their own tab — the last icon in the row. Turning off visibility doesn't block the sender and doesn't by itself turn off notifications: to do that, turn on "Quiet" in the requests row.
Once you reply, the conversation is no longer a message request and follows the settings for regular direct chats. So if direct chats are turned off, it won't necessarily appear on home after you reply.
Example: one widget on home, all requests without notifications
Say you're an administrator of four widgets but only want one on home: turn off "On home" for "All project requests", then turn it on for the widget you need. The other requests stay in the "Requests" tab.
To make all project requests arrive quietly, turn on "Quiet" for "All project requests". If only certain widgets or messenger connections should be quiet, turn on "Quiet" for those sources. Click "Save": new messages keep increasing the unread counters without sound or notifications.
Finding a person, a message and a mention are different actions
To find someone to talk to, use search in the chat list or contacts. To find text from an old conversation, type words from the message in chat search and choose a result among the messages. Search covers the conversations you have access to and doesn't open other people's conversations.
The list that appears when you type @ in a message is for mentioning a participant. It isn't a global user directory: in a regular conversation it covers participants, and in requests it covers project colleagues.
How to contact Sensever support
If by "find a person" you mean a support agent, open sensever.com/help and write in the support widget. Say that you need help from an agent and describe your question. The message stays in the request and is available to the team; the assistant can't promise that an agent will join immediately or give a reply time.
Text, replies, reactions and photos
The smiley button under the input field opens emoji. The selected emoji is inserted where the cursor is. Emoji and reactions use the same set.
Formatting and finding colleagues
Select text and click B, I or S under the field: bold, italic and strikethrough. The result is visible right away and is kept after sending. Keyboard shortcuts: Ctrl+B, Ctrl+I and Ctrl+Shift+X; on a Mac, use ⌘.
Press Alt on its own or start typing @ to find a person. In requests, search shows colleagues from the selected project; in direct chats and groups, the conversation's participants. The arrow keys choose a result, Enter inserts the name and Esc closes the list. Alt+Shift still switches the keyboard layout. Widget visitors aren't shown the list of colleagues.
Reply to a specific message
Right-click a message and choose "Reply". On a phone, press and hold the message. The author and the text or a photo thumbnail appear above the input field. Write your reply and send it.
The cross next to the preview cancels the reply. The sent message keeps the quote: click it to jump to the original.
Add or remove a reaction
Open the same menu and choose one of 25 emoji. The reaction appears under the message. Click your reaction again to remove it. The number next to it shows how many participants chose that emoji.
Attach and open a photo or file
Click the paperclip under the input field. You can also drag a file into the field or paste an image from the clipboard. You can attach up to 10 files, each up to 50 MB.
Click a photo in the conversation: it opens on top of the chat. The arrow keys switch between photos, clicking zooms the image and Esc closes the viewer. The "Original" button lets you download the source file.
For viewing supported images, a lightweight WebP copy up to 1280 pixels on the long side is created. The original is kept. This speeds up viewing; together, the two versions take up more space than the original alone.
What the check marks and "typing…" mean
One gray check mark — the server has received the message.
Two gray check marks — the message has been delivered to the other side.
Two blue check marks — the other side has opened the conversation and reached the new messages.
In a group, two check marks mean confirmation from all current members with read access. Statuses update automatically. A closed widget doesn't mark messages as read.
"typing…" appears while the other person is writing a reply. You don't see the text of their draft.
Direct chats, editing and sending from the keyboard
Click "New chat", choose a direct chat and find the person by name. Search shows people who have opened Chat at least once.
In a regular chat, Enter sends the message and Shift + Enter adds a line break. Your own messages have "Edit" and "Delete". Deleting applies for all participants of the conversation.
What's in the left menu
In "Requests", the selected project, conversation, status, department and search are kept in the address bar. Copy the address to open this screen later or share the link with a colleague who has access to the project. Refreshing the page and the Back/Forward buttons restore the screen.
The arrow next to the logo collapses the menu to icons. Click it again, or click an empty spot in the collapsed column, to expand it. Your choice is saved in the browser. On a phone, the menu opens with the three-line button at the top.
All messages
"All messages" is your main feed. It can include direct chats, groups, channels, discussions and project requests. You choose what it contains through the filter next to "Create" → "Feed settings". By default all types are on except requests from new contacts.
Groups and channels
Separate lists of your groups and channels. The "Create" button lets you start a new conversation. Turning off visibility on home doesn't remove a conversation from its tab.
Requests
Conversations with customers on behalf of a project. For example, this is where the ULIGHT RU team replies to visitors of ulight.ru.
Projects
Your websites, team and widget settings. A project can be a store, a blog, a service or a CRM.
Settings
Notifications on this device, the compact message list and a link to account management.
Developers
Documentation for specialists who connect Chat to other applications.
You can see direct chats and project requests together on home. If a conversation with a customer is hidden by the feed settings, it stays available in the "Requests" tab. The message requests tab is the last in the row of tabs; on a narrow screen you can scroll the row horizontally.
Notifications and account
In "Settings", click "Turn on notifications" and allow them in your browser. The permission applies to this device. You can also click "Turn on notifications" in the left menu. Once set up, you can close the Chat tab: new messages arrive through the browser. The "Test notification" button helps you check that notifications appear on the device. On an iPhone/iPad, first add Chat to the Home Screen and open it from the icon. If you previously blocked notifications, change the permission in your browser's site settings.
The "Turn off on this device" button turns off notifications here. Receiving them also depends on your browser and operating system settings.
Your name, sign-in methods and signing out everywhere are managed in Accounts with the "Manage account" button. The compact message list is turned on separately in the Chat settings and is saved in this browser.
Комментарии