Channels Overview
Choose the right chat channel for your Buda Agent and understand how channel connections, sessions, and rollout work.
Channels are how your Agent talks to the outside world. A channel connects one communication surface, such as WhatsApp, Telegram, Discord, Slack, Feishu, or WeCom, to a target Agent in Buda.
What a channel does
- Receives inbound user messages
- Maps each user or group conversation to the right Chat Session
- Sends the Agent's reply back to the same platform
- Keeps the connection alive in the background
How to choose a channel
| Channel | Best for | Notes |
|---|---|---|
| Customer support, sales, lead capture | Best for external users and mobile-first conversations | |
| Telegram | Bots, communities, internal automation | Fast setup with BotFather token |
| Discord | Developer communities and shared channels | Useful for community support and async teamwork |
| Slack | Internal team workflows | Good for operations, support, and internal copilots |
| WeCom | China-based internal company messaging | Fits enterprise workflows in WeCom-heavy organizations |
| Feishu | Team collaboration in Lark/Feishu environments | Common in startups and regional operations teams |
Recommended rollout path
- Start with one Agent and one channel.
- Validate the Agent's tone, response quality, and knowledge base on real conversations.
- Define session rules: who can message, whether groups are allowed, and when to start a fresh session.
- Add more channels only after the first one is stable.
Before you connect a channel
- Make sure the target Agent already exists.
- Upload the key files it should reference in Drive.
- Decide whether the channel is for external customers, internal teammates, or both.
- Prepare a short welcome message and escalation policy for cases the Agent cannot handle.