Chat and channels
WhatsApp, Telegram, web and voice, and how group modes work.
Suvi listens on several channels and they share one session and one memory. A fact learned on WhatsApp is known on the web dashboard immediately.
The primary surface. Suvi gets its own seat rather than a copy of yours: you pair a second device to a number Suvi answers on. It handles direct messages and, when you add it, groups.
Media works in both directions. Send a voice note, a photo of an invoice or a PDF and Suvi reads it. It replies with documents, images and spoken audio.
Telegram, web and voice
Telegram is a full second channel through the same gatekeeper and session pool. The web dashboard has a chat panel. A voice page lets you hold a spoken conversation in the browser, with transcription and speech both running on the instance rather than a third-party API.
Group modes
Group behaviour is per group, and the mode controls whether Suvi replies, not whether it listens.
| How much should Suvi say in this group? | Mode |
|---|---|
| Reply to everything relevant | active |
| Reply only when named | mention |
| Never reply, but stay aware of the conversation | silent |
| Store everything, process nothing, reply never | mining |
Every message is stored regardless of mode
Silent and mining stop Suvi talking. They do not stop it listening. This is the point of adding it to a group at all, but it is worth telling the group.
mining differs from silent in that it skips processing as well as replying:
messages are kept for later search but do not enter the knowledge graph or
trigger any work. Use it for high-volume groups where the content matters
occasionally but the noise would swamp the graph.