Channels
Access: Admin.
URL: /staff/channels
Channels are the entry points where customers interact with Stenbee. Each channel represents a platform (website embed, Facebook, Instagram, Telegram, WhatsApp, TikTok) and has its own configuration, session list, and optional widget overrides.
Page layout
Section titled “Page layout”Channel list with expandable cards
Section titled “Channel list with expandable cards”Channels are displayed as a vertical list of cards. Each card shows:
| Element | Description |
|---|---|
| Platform icon | Visual indicator of channel type |
| Channel name | The name you gave the channel |
| Session count | Number of conversations on this channel |
| Active/inactive toggle | Switch to enable or disable the channel |
Click a card to expand it, revealing the full configuration panel.
Channel types
Section titled “Channel types”When creating a channel, you select from these platform types:
| Type | Use case |
|---|---|
| HTML Embed | Embed the Stenbee chat widget on your website |
| Connect a Facebook Page for Messenger conversations | |
| Connect an Instagram Business account for DM conversations | |
| Telegram | Connect a Telegram bot for messaging |
| Connect a WhatsApp Business account | |
| TikTok | Connect a TikTok Business account |
Core interactions
Section titled “Core interactions”Creating a channel
Section titled “Creating a channel”- Click Create Channel at the top of the page
- Enter a channel name
- Select the platform type from the dropdown
- Platform-specific fields appear — fill them in and save
Configuring by platform type
Section titled “Configuring by platform type”HTML Embed
Section titled “HTML Embed”| Setting | Description |
|---|---|
| Allowed Domains | Comma-separated list of domains where the widget can load (e.g., example.com, store.example.com). Prevents unauthorized embedding. |
| Embed Code | Generated script snippet to paste into your website |
Facebook / Instagram (Meta)
Section titled “Facebook / Instagram (Meta)”| Setting | Description |
|---|---|
| OAuth connection | Click Connect to open a Meta OAuth popup. Log in to the Facebook/Instagram account and grant permissions. |
| Webhook URL | Auto-generated URL. Copy this into your Meta App’s webhook settings. |
| Verify Token | Auto-generated token. Use this in your Meta App’s webhook verification. |
Meta OAuth flow:
- Click Connect (or Reconnect if previously connected)
- A popup opens to Facebook’s OAuth consent screen
- Log in and grant messaging permissions
- The popup closes and the panel updates to show “Connected”
Telegram
Section titled “Telegram”| Setting | Description |
|---|---|
| Bot Token | Your Telegram bot token from @BotFather |
| Webhook URL | Auto-generated URL for receiving Telegram updates |
| Set Webhook | Click this button to register the webhook URL with Telegram |
Telegram setup workflow:
- Create a bot via @BotFather on Telegram
- Copy the bot token
- Paste it into the channel config
- Click Set Webhook — this registers your panel’s webhook URL with Telegram
- The channel is ready — messages sent to your bot appear as sessions in the panel
Expanded channel panel
Section titled “Expanded channel panel”When a channel card is expanded, you see these actions:
| Action | Description |
|---|---|
| Channel ID | The unique identifier for this channel — copyable for reference |
| Meta Webhook URL | (Meta channels) The webhook URL to paste into Meta’s developer console — copyable |
| Meta Verify Token | (Meta channels) The verify token for webhook setup — copyable |
| Telegram Webhook URL | (Telegram channels) The webhook URL — copyable |
| Telegram Set Webhook | (Telegram channels) Button to register the webhook with Telegram |
| Get Code | (HTML Embed) Generates the embed script snippet |
| Connect / Reconnect | (Meta channels) Opens OAuth flow |
| Widget Settings | Per-channel widget overrides (see below) |
| Toggle Active | Enable or disable the channel |
| Delete | Removes the channel permanently |
Embed code generation (HTML Embed)
Section titled “Embed code generation (HTML Embed)”Click Get Code to generate an embed snippet. The modal displays a script tag you can copy and paste into any page within your allowed domains to embed the chat widget. A Copy button copies the snippet to your clipboard.
Widget settings (per-channel overrides)
Section titled “Widget settings (per-channel overrides)”Each channel can override workspace-level settings from the Settings page:
| Override | Description |
|---|---|
| Widget Title | Custom heading for this channel’s widget |
| Agent Name | Custom sender name for AI messages on this channel |
| Color | Custom accent color for this channel’s widget |
| Avatar URL | Custom agent avatar for this channel |
| System Prompt | Custom AI instructions for conversations on this channel |
If a channel has an override set, it supersedes the workspace-level setting. Leave the override empty to fall back to the workspace default.
Channel count limit
Section titled “Channel count limit”The Dashboard shows your plan’s channel limit. When reached:
- The Create Channel button is disabled
- A message appears: “Channel limit reached. Delete existing channels to create more.”
States
Section titled “States”| State | What you see |
|---|---|
| Loading | Channel cards show skeleton placeholders |
| Empty | ”No channels yet — create your first channel” |
| Limit reached | Create button disabled with limit message |
| OAuth in progress | Popup window open; panel waits for callback |
| Webhook set | Green toast: “Webhook registered successfully” |
| Delete | Confirmation modal before permanent deletion |
- Create separate channels for different sections of your site (e.g., “Homepage”, “Pricing Page”, “Checkout”) with tailored system prompts
- Use allowed domains to prevent unauthorized widget embedding on other sites
- Test Meta OAuth in an incognito window to ensure you’re logged into the correct Facebook account
- Telegram’s Set Webhook must be clicked after pasting the bot token — it’s a separate setup step
- Channel-level system prompts are powerful — you can have a “sales-focused” agent on one channel and a “support-focused” agent on another