Deployment Channels
One agent definition. Multiple deployment surfaces. Update once — all channels reflect the change.
A channel is a delivery surface, not a copy of the agent. Changes to your agent’s instructions or tools propagate to all deployed channels automatically.
Supported channels
Web Chat
Bothive hosts a shareable web chat link for every agent. Embed it on your site as a widget or share the URL directly.Setup time: 30 seconds
Session support:
Best for: Customer support, product demos, internal tools
Telegram
Deploy as a real Telegram bot with full BotFather integration. Supports commands, groups, inline mode, and message callbacks.Setup time: ~5 minutes
Session support:
Best for: Communities, customer support, personal assistants
Slack
Deploy to any Slack workspace. The agent responds in DMs, channels, or threads. Supports slash commands.Setup time: ~10 minutes
Session support:
Best for: Internal tools, developer assistants, team bots
REST API
Call your agent programmatically from any backend. Streaming supported. Session management via session ID header.Setup time: ~5 minutes
Session support:
Best for: SaaS product integration, programmatic agents
WhatsApp (Coming Soon)
WhatsApp Business API support is in beta. Contact the team to join early access. Supports message routing, media, and template messages.
Channel comparison
How channel binding works
When you deploy to a channel, Bothive creates a channel binding:bot_abc123. All replies from bot_abc123 are sent back through the Telegram provider.
Deploying to Telegram
1
Create your bot with BotFather
Open Telegram → search
@BotFather → /newbot → choose a name and username → copy the bot token.2
Add token to Bothive
In your bot dashboard → Channels → Telegram → paste the token.
3
Set the webhook
Bothive automatically sets the webhook URL. You’ll see a green when confirmed.
4
Test it
Open Telegram → message your bot → see the response in real time.
Deploying via API
Channel-specific formatting
Agents can detect which channel they’re responding on and adjust formatting:Best practices
Launch one channel first
Launch one channel first
Don’t try to deploy all channels simultaneously. Pick one (usually Web or Telegram), make it production-quality, then expand. Each channel has quirks you need to learn.
Test message formatting per channel
Test message formatting per channel
Markdown renders differently on Web, Telegram, and Slack. Test your agent’s responses on each channel before going live, especially if you use formatting heavily.
Set channel-specific rate limits
Set channel-specific rate limits
The API channel often serves many users at once. Configure per-user rate limits in your bot settings to prevent abuse.
Use session IDs for the API channel
Use session IDs for the API channel
Always pass a stable
X-Session-ID header when calling the API channel. This ensures memory and context work correctly across multiple calls from the same user.