---
url: 'https://docs.mychatbot.app/channels.md'
description: >-
  Choose a channel based on who the assistant talks to. Customer conversations
  belong to the Sales Platform; the Agents Platform has a separate Telegram
  connection for an agent…
---

# Channels

Choose a channel based on **who the assistant talks to**. Customer conversations belong
to the Sales Platform; the Agents Platform has a separate Telegram connection for an
agent that works with you or your team. These paths use different bots and create
different kinds of conversations.

## Choose the right platform

| You want to… | Platform | Connection | Conversations appear in | Start here |
|---|---|---|---|---|
| Answer customers on your website, WhatsApp, Instagram, Facebook, Viber, email, SMS, marketplaces, or phone | **Sales Platform** | Connect a channel to the customer-facing sales assistant | Sales chats and client records | [Sales channels](#sales-platform-channels) |
| Talk to an autonomous agent from Telegram so it can research, operate tools, or run tasks for you | **Agents Platform** | Connect a dedicated Telegram bot to one agent | That agent's conversations | [Connect Telegram to an agent](/agents/telegram) |

::: warning The two Telegram connections are separate
The [Sales Platform Telegram channel](/channels/telegram) talks to your customers. The
[Agents Platform Telegram bot](/agents/telegram) talks to you or your team. Use a separate
BotFather token for each connection and do not expect conversations to move between the
two platforms.
:::

## Sales Platform channels

Most Sales Platform channels are self-serve under **Sales Platform → Channels**. Select
the sales assistant that should answer, connect the provider account or token, review its
behavior settings, and turn the channel on only after a test.

| Channel | Typical use | Direction | What you need |
|---|---|---|---|
| [Website Widget](/channels/website-widget) | Customer chat embedded on your site | Inbound chat; the assistant replies | A website where you can paste the embed |
| [WhatsApp](/channels/whatsapp) | Official WhatsApp Business or a linked personal number | Two-way messaging | A WhatsApp Business account or linked phone |
| [Telegram bot](/channels/telegram) | A dedicated customer-facing bot | Two-way messaging | A BotFather token |
| [Telegram Account](/channels/telegram-account) | Answer from an existing Telegram account | Two-way messaging, with polling delay | A Telegram account and linked-device authorization |
| [Instagram](/channels/instagram) | DMs, comments, story reactions, and product replies | Inbound events and replies | An eligible Instagram account |
| [Facebook Messenger](/channels/facebook) | Page messages and comment-to-DM flows | Inbound events and replies | A Facebook Page |
| [TikTok](/channels/tiktok) | Direct messages and comment replies | Inbound events and replies | A TikTok account with messaging permissions |
| [Viber bot](/channels/viber) | A dedicated Viber customer bot | Two-way messaging | A Viber bot token |
| [E-Chat Viber](/channels/e-chat-viber) | A Viber number through E-Chat.tech | Two-way messaging | An E-Chat.tech account, API token, and number |
| [E-Chat Telegram](/channels/echat-telegram) | A Telegram phone number through E-Chat.tech | Two-way messaging | An E-Chat.tech account, API token, number, and webhook |
| [Gmail](/channels/email) | A shared customer email inbox | Receive and reply, including attachments | A Google account for the assistant |
| [SMS](/channels/sms) | Text conversations on a business phone number | Two-way SMS | Twilio or Quo (OpenPhone) with an SMS-capable number |
| [OLX](/channels/olx) | Buyer chats on supported OLX marketplaces | Inbound buyer messages and replies | An OLX seller account in Ukraine, Poland, or Romania |
| [Calls](/channels/calls) | AI voice on phone or in the browser | Inbound and outbound AI calls | SIP, Twilio, or the Web SDK |
| [Calls Ringostat](/channels/ringostat) | Put human-manager calls and transcripts into client chats | Inbound and outbound human calls | A Ringostat account and webhook |
| [UniTalk](/channels/unitalk) | Put human-manager calls and transcripts into client chats | Inbound and outbound human calls | Preview access configured with MyChatBot support |
| [Webhooks API](/channels/webhooks) | Connect a custom messaging system | Your system sends inbound messages and receives replies | An HTTPS reply endpoint and generated token |

## Before going live

1. Configure and test the assistant in a private chat first.
2. Connect one channel and leave its **Connect agent to this channel** switch off while
   you review credentials and behavior settings.
3. Turn it on, send a real test message or call, and confirm the reply lands in the
   expected Sales chat or Agents conversation.
4. Test pause and disconnect behavior. Confirm any provider-side webhook, permission,
   template, or carrier requirement in the channel-specific guide.

## See also

* [Sales Platform](/sales/) — configure the customer-facing assistant and client records
* [Agents Platform](/agents/) — configure autonomous agents that work for your team
* [Connect Telegram to an agent](/agents/telegram) — the direct Agents Platform channel
* [CRM and integrations](/integrations/overview) — connect downstream business systems
* [Channels cheat sheet](/cheat-sheets#channels-integrations) — quick links to related setup references