Your customers already chat where the answers live
Your customers write on WhatsApp, Telegram, Discord and Slack: from today those same channels answer with what your documents say, citation included. Request a demo and watch your knowledge answer where your customers already are.

Your customers already write there: now the answers write back
Your customers and colleagues talk on WhatsApp, Telegram, Discord and Slack every day. From today those same channels answer with what YOUR documents say - cited, and with the data on your servers.
One knowledge base, one per-channel door
Every channel you connect gets one door into the same document knowledge: staff and customers ask in the chat they use daily, and the answer - with the source cited - arrives in that same conversation. Everything you don't connect stays unreachable: the door opens only where you open it, and the IT office decides who reads what, permission by permission.
Limits you decide
You set how much traffic each channel can consume: per minute and per day, with zero meaning "no ceiling". An unexpected wave of messages consumes what you allow - nothing more. Turn a door off without deleting a thing, re-tune it after an incident: today's update makes that a single edit, not a rebuild. (This is the part for large organizations: the channel doors are a feature of the Enterprise edition.)
The answer you can check
When the documents don't contain the answer, the channel reads the reply you wrote for that case - never a confident guess with nothing behind it. When they do, the citation travels with the answer: the reader can ask "says who?" and get the document. You can verify it: open the cited document and check the wording yourself.
See it live
Richiedi una dimostrazione — bring one channel and a folder of documents, and watch the knowledge answer where your customers already are:
- Request a demo
- The full operator walkthrough(/en/docs/connectors)
- The engineering deep dive(/en/blog/connectors-adapter-contract)
Facts in this post - FACT-CENSUS rows F-CONN-1, F-CONN-2 (cited in the plan). Provenance: the product's docs at v0.28.1.


