Skip to main content

Channel Workflows

Channels are the places where people talk to bots. Veoveo keeps channel input connected to workspace context so agent work can be reviewed later.

Supported Channel Patterns​

  • Web dock: direct browser interaction with a selected workspace bot.
  • Telegram: team chat or direct-message interaction with a workspace bot when configured.
  • MCP delegation: compatible clients can delegate work to a workspace bot through the MCP surface.

How A Channel Request Moves​

  1. A user sends a prompt or command through a channel.
  2. Veoveo resolves the workspace, bot, and actor context.
  3. The bot receives the request with the channel's available context.
  4. Tool calls and multi-step work are recorded in an operation.
  5. The channel receives the response or follow-up message.

Channel Design Guidance​

Use the web dock for focused artifact and workspace work. Use Telegram when the team already coordinates in chat and needs bot help inside that flow. Use MCP delegation when another client needs structured access to a workspace bot.

Media To Add​

  • Diagram: the same bot reached from web dock, Telegram, and MCP delegation. It helps teams understand that channels are access paths, not separate bots. Source: workspace bot with multiple configured channels.
  • Video: prompt in the web dock producing an operation timeline and artifact output. It helps users see how channel input becomes reviewable work. Source: sample workspace bot interaction.