> ## Documentation Index
> Fetch the complete documentation index at: https://boundbot.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels overview

> Understand how BoundBot connects bots to customer-facing surfaces.

export const BrowserWrapper = ({src, alt, title, description, height = '280px', caption, imgStyle = {}, children, imagePadding = '0px'}) => {
  const legacyDocsImagePrefix = '/images/';
  const productionDocsImagePrefix = '/docs/images';
  const rawSrc = typeof src === 'string' ? src : src && (src.src || src.default) || '';
  const imageSrc = rawSrc.startsWith(legacyDocsImagePrefix) ? `${productionDocsImagePrefix}/${rawSrc.slice(legacyDocsImagePrefix.length)}` : rawSrc;
  return <Frame caption={caption || alt || title} width="100%">
      <div style={{
    border: '1px solid #e2e8f0',
    borderRadius: '12px',
    overflow: 'hidden',
    boxShadow: '0 10px 15px -3px rgba(0, 0, 0, 0.1), 0 4px 6px -2px rgba(0, 0, 0, 0.05)',
    width: '100%'
  }}>
        <div style={{
    backgroundColor: '#f8fafc',
    padding: '10px 15px',
    borderBottom: '1px solid #e2e8f0',
    display: 'flex',
    gap: '6px'
  }}>
          <div style={{
    width: '10px',
    height: '10px',
    borderRadius: '50%',
    backgroundColor: '#ff5f56'
  }} />
          <div style={{
    width: '10px',
    height: '10px',
    borderRadius: '50%',
    backgroundColor: '#ffbd2e'
  }} />
          <div style={{
    width: '10px',
    height: '10px',
    borderRadius: '50%',
    backgroundColor: '#27c93f'
  }} />
        </div>
        <div style={{
    overflow: 'hidden',
    background: '#ffffff',
    width: '100%',
    padding: imagePadding
  }}>
          {src ? <img src={imageSrc} alt={alt || ''} data-docs-screenshot style={{
    ...imgStyle,
    width: '100%',
    minWidth: '100%',
    height: 'auto',
    display: 'block',
    borderRadius: '0px'
  }} /> : children ? children : null}
        </div>
      </div>
    </Frame>;
};

A channel is the connection between BoundBot and a customer-facing platform. Every channel points to a bot, and every conversation that enters through that channel is handled by that bot unless you add other automation on top.

<BrowserWrapper src="../images/webchat-connect.png" alt="Channel management dashboard." caption="The channel management dashboard showing various channel types, public keys, and status toggles." />

## Available channels

BoundBot currently exposes these channel types in the <a href="https://www.boundbot.com/dashboard/channels/webchat" target="_blank" rel="noopener noreferrer">dashboard</a>:

* **WebChat**
* **WhatsApp**
* **Messenger (Beta)**
* **Telegram**
* **Slack**
* **Discord**

## Plan availability

* WebChat: available on all plans
* WhatsApp, Messenger, Telegram: available on Starter and above
* Slack, Discord: available on Pro and above

## Match the channel to the job

<Tabs sync={false}>
  <Tab title="Website" icon="globe">
    **WebChat** is the best fit when you want real-time lead generation and support directly on your site—especially on landing pages and marketing pages where every visitor is a potential conversation.

    **Best for**

    * Capturing leads and answering pre-sales questions while the visitor is still on the page
    * Support and triage without forcing users to leave your domain or open another app
    * A consistent, on-brand experience because you control where and how the widget appears

    **Key benefit**

    * Full **UI customization** (theme, position, colors, copy) so the widget matches your brand identity
    * Public key + optional origin controls let you align embeds with production, staging, or testing safely
    * Fastest path to a live bot on your own properties—see <a href="/channels/webchat">WebChat</a> for setup and embed
  </Tab>

  <Tab title="Social" icon="message-circle">
    **WhatsApp**, **Messenger**, and **Telegram** put the bot where your customers already message, which lowers friction for sales and routine queries and keeps conversations in apps they use daily.

    **Best for**

    * Re-engagement and follow-ups in channels customers check often
    * Sales and support threads that do not need a browser session on your site
    * Regions and audiences that prefer chat apps over email or phone

    **Key benefit**

    * **Asynchronous, long-term support**—threads persist and users can reply when it suits them
    * Less friction than asking users to switch context; you meet them on their preferred platform
    * Strong fit for ongoing conversations rather than one-off page visits—see <a href="/channels/whatsapp">WhatsApp</a>, <a href="/channels/messenger">Messenger</a>, and <a href="/channels/telegram">Telegram</a>
  </Tab>

  <Tab title="Community" icon="users">
    **Slack** and **Discord** are the go-to when the bot supports **internal team productivity**, **developer or partner support**, or **large community groups** where many people share a space.

    **Best for**

    * Internal teams (ops, support, sales) who already collaborate in Slack
    * Developer communities, open-source projects, or technical audiences on Discord
    * Member-heavy communities that need moderation-aware, thread-based help at scale

    **Key benefit**

    * Operators and members stay in a single workspace; the bot answers where work already happens
    * Better suited to **structured channels** and roles than one-off web chats alone
    * Pro and above—see <a href="/channels/slack-discord">Slack and Discord</a> for OAuth, activation, and permissions
  </Tab>
</Tabs>

## Before you connect a channel

Make sure you already have:

1. a bot to attach to the channel
2. the right provider account or bot token
3. the permissions, business assets, or bot credentials required by that provider

## Channel status

Each channel can appear as:

* **Active**: healthy and ready to receive messages
* **Disconnected**: configured but not currently usable
* **Error**: connected with a credential, webhook, or provider issue

## Choose the right channel

Use **WebChat** when you want the fastest path to a live bot on your own site.

Use **WhatsApp** or **Messenger** when you want customer support or sales inside Meta-owned messaging apps.

Use **Telegram**, **Slack**, or **Discord** when your audience already lives inside those environments.

## Channel-specific setup guides

<CardGroup cols={2}>
  <Card title="WebChat" icon="messages-square" href="/channels/webchat">
    Create a website chat widget, customize it, and embed it on your site.
  </Card>

  <Card title="WhatsApp" icon="message-circle" href="/channels/whatsapp">
    Connect a WhatsApp Business setup with Embedded Signup or redirect OAuth.
  </Card>

  <Card title="Messenger" icon="messages-square" href="/channels/messenger">
    Link a Facebook page and route Messenger threads into BoundBot.
  </Card>

  <Card title="Telegram" icon="send" href="/channels/telegram">
    Connect with a bot token from BotFather.
  </Card>

  <Card title="Slack and Discord" icon="plug" href="/channels/slack-discord">
    Connect internal or community chat environments on Pro and above.
  </Card>
</CardGroup>
