Channels: how people reach agents
Channels bring conversations to agents. Each channel has its own access control, independent of the agent's.
Chat, email, phone and business apps, without asking anyone to learn a new tool.
Each entry point says who can come in: everyone, members or a group.
Channels at a glance
| Channel | What it does | Access control |
|---|---|---|
| Web app | A page or application of your own, with an assistant that uses the app's functions | Public, organization or group |
| Telegram bot | Every message to the bot becomes a conversation | Who gets an answer: anyone or only members linked with /link |
| Mailbox | Incoming mail becomes a conversation, one per thread | Can accept only authenticated mail from members or from a group |
| Voice | Gives an agent a voice on the phone. See Telephony and voice | Call routing |
| Scheduler | Starts conversations or runs tools at the set time | Uses only organization resources or those of the pinned account |
| MCP server | Lets external assistants use the project's tools or talk to an agent | Whoever has the address can do everything the tools allow |
Web app with an assistant
This is the platform's main use case: an app for organization members with a chat inside. The agent's turn runs inside TeraBrain NX and the page just observes it: reloading mid-answer loses nothing.
- The app is published at an address in the environment, or at a dedicated domain name.
- The visitor's identity always comes from the platform, in headers the browser cannot forge.
- A restricted app sends the anonymous visitor to login. The session is single for the whole platform.
- The app's tools (its functions) are the assistant's tools.
Telegram and mailbox
- Telegram. The bot is created with BotFather and the token is set as a secret. It can be limited to members, who link their own account from their profile. A /reset command opens a new conversation.
- Hosted mailbox. An address managed by TeraBrain NX, active at build.
- Gmail, Microsoft 365, IMAP. They connect with a connection or with credentials; Microsoft 365 also supports shared mailboxes.
- Controlled sending. The
allowfield limits the recipients an agent can write to.
Scheduler
It is the project's clock. Tasks are written in the Scheduled tasks section, or an agent schedules them on its own within limits on frequency, number and duration. Every run is recorded.
MCP server
It is the door for external assistants (Claude, ChatGPT, Claude Code, Cursor), which use it as a connector. It offers the project's tools, an agent to assign tasks to, or both.
Related pages
How to create a new agent
Step by step: project, agent node, instructions, model, tools, channel, testing and publishing.
Telephony and voice
A small SIP switchboard in the project: lines, extensions, opening hours, menus and agents that talk on the phone.
Security
Roles, groups, credentials, enterprise sign-in and least privilege: how to protect an agent system.
Building with external assistants
Using Claude, Codex or other assistants to build and develop TeraBrain NX projects, with the person's own rights.
Have an agent to take to production?Let’s talk.
We show you TeraBrain NX on your case: systems to connect, access and controls.