Sensever: what it is and where to start
Sensever is a messenger and a set of business tools under one account. You chat with people, groups and channels, answer customers from your website and messengers in one queue, add an advanced chat widget with a built-in AI assistant to your site, publish articles, keep your files in one Storage, plan work in Flow and connect your own code through bots and the API.
This page is a map. Each section says in a few sentences what the product does and who it is for, and links to the detailed guides in this channel.
Chats, groups, channels and topics
Direct chats, groups and channels work like in a familiar messenger: text, replies, reactions, photos, files, voice messages and calls. A group is a shared conversation; a big group can be split into topics, so each subject has its own thread. A channel is for publishing: its owners post, readers subscribe, and a channel can hold articles sorted into sections, like this one.
Read more: Chats, contacts and messaging in Sensever and Articles and channels.
Requests: customer support in one queue
Requests is where a company answers its customers. Messages from the website widget, the contact page and connected messengers (WhatsApp, Telegram, MAX and Instagram) arrive as requests of one project, and your team answers them from Sensever. Requests can be assigned automatically, split by departments and handed over between agents. It is for any business that talks to customers and wants one inbox instead of five apps.
A project doesn't need a website. If you sell on a marketplace or talk to customers only on WhatsApp, create a project with the website field left empty, connect your messengers and turn on the AI assistant: it answers there.
Read more: Customer support: requests, team and routing and Project messaging channels. Connection guides: WhatsApp, Telegram, MAX, Instagram.
Website chat widget with an AI assistant
Sensever gives your website an advanced chat widget with a built-in AI assistant. Visitors write in the widget, the assistant answers from your articles, documents and price tables, and an agent can join the same conversation at any moment. To set it up, create a project, add your site, paste the widget code into the site and turn on the assistant in the project's Assistant section. You can also connect your own bot instead of our model.
Read more: AI chat for your website, Website widgets: support, comments and private access and, for developers, the widget installation guide.
Comments on your website
A comments block can sit under an article, a product or a task on your own site. Comments can be public, with guests and Sensever accounts, or private for a CRM or a closed site, where your server decides who may read and write. Moderation happens in Sensever.
Read more: Website comments: public and private and Library and comments API.
Studio: articles, videos and publishing to channels
Studio is where you create materials: articles with headings and a table of contents, videos, photo galleries, recipes and reels. Several authors can work on one draft. A material is published into a channel, where it gets its own address and a card in the channel feed. Documentation, a knowledge base for the AI assistant or a company blog are all made this way.
Read more: Articles and channels: creating, publishing and access.
Storage: your files in one place
Storage keeps the files you upload in Sensever: photos and files from chats, Studio media, files for the AI assistant. When you attach a file, the Storage window lets you upload from your device or pick a file you already have, so it is reused instead of uploaded again. Removing a file from a chat or from the assistant's knowledge doesn't delete it from Storage. Space is counted for the owner of the place where the file is used: the owner of the group, channel, project or Flow workspace.
Flow: tasks, deals and workspaces
Flow is for team work: tasks, deals, projects and any objects with your own fields and statuses. Work is organized in workspaces, shown as a table, a board, a calendar or a timeline, with automations, processes with approvals, reports and time tracking. Notifications come to Sensever chat and by email.
Read more: Flow: introduction, Flow: workspaces and templates and All workspaces mode. For developers: Flow API basics.
Bots and the Bot API
A bot is an account that belongs to a person and is driven by code. Bots answer in direct chats, work in groups and channels, show buttons and Mini Apps, and can answer website visitors as a project's assistant. Sensever has its own Bot API and also accepts Telegram Bot API requests, so many existing Telegram bots run after changing the address and the token.
Read more: What Sensever bots can do, Your first bot step by step and Moving a bot from Telegram.
API and API keys
The API lets your server read chats and send messages, publish Studio content into a channel, read a channel's knowledge base and work with Flow tasks. Access goes through API keys that you issue in your profile, each with its own permissions, channels and workspaces. There is also a JavaScript SDK for chat in browsers and Node.
Read more: Sensever API: authorization, content, chats and Flow tasks, Library and comments API and JavaScript SDK.
Apps for computer and phone
Sensever works in the browser at sensever.com. Apps for Windows and macOS with native notifications are on the download page. On iPhone, iPad and Android you can install Sensever as a web app with notifications and its own icon; App Store and Google Play apps are on their way. One account works on every device.
Where to start
An AI chat on your website: AI chat for your website.
Answer WhatsApp, Telegram, MAX or Instagram customers in one place: Project messaging channels.
Organize your team's support: Customer support: requests, team and routing.
Publish documentation or a blog: Articles and channels.
Plan tasks and deals: Flow: introduction.
Build a bot or an integration: What Sensever bots can do and Sensever API.
If something is unclear, write to Sensever support at sensever.com/help: the virtual assistant answers first, and our team is in the same conversation.
Reacties