Tenant
One organisation’s installation — its assistants, its people, its data. On a self-hosted installation there is exactly one, and it is mostly invisible: it shows up as the tenant-wide Settings that every assistant shares.Assistant
One bot. It has its own channels, flows, contacts and conversations, and shares nothing with other assistants. See Assistants.Channel
The assistant’s presence on a messaging platform — the Telegram or WhatsApp bot people actually write to. An assistant without a channel cannot hear anyone. See Channels.Contact
A person the assistant has talked to, on one channel. Contacts are not entered by hand: one appears the first time someone writes. See Contacts.A contact belongs to a channel, not to a person. The same human writing on two
platforms is two contacts, because the assistant has no way to know they are
the same and guessing wrong would merge two strangers.
Flow
A conversation, drawn rather than coded. A flow is a sequence of nodes — send a message, wait for a reply, branch on a condition, call another system — and the connections between them. See Flows.Node and handle
A node does one thing and reports an outcome: a branch reportsyes or no,
a call reports whether it worked. That outcome is called a handle, and the flow
decides where each handle leads.
The node does not choose what comes next. That separation is why a flow can be
rearranged without rewriting its parts, and why an unexpected path is either a
wrong outcome or a wrongly connected one — a distinction
Flow logs makes visible.
Session
One contact making one pass through one flow. A session starts when a flow is triggered and ends when the flow finishes or is abandoned. See Sessions.A conversation is the whole history with a contact on a channel. A
session is one journey through one flow inside it. A conversation may
contain many sessions, or none.
Publishing
Editing a flow does not change what contacts see. Work happens in a draft, and contacts keep receiving the published version until someone publishes the new one. See Publishing a flow. A session also holds the version it started with, so publishing never changes a conversation already under way.Trigger
What causes a flow to start — a keyword the contact sends, an event raised elsewhere, or being the assistant’s default flow. A flow with no trigger is started by another flow, or not at all.Everything else in this guide is a screen for managing one of these.