---
title: "Supported channels"
description: "The four channels you can connect from the CloudFly Helpdesk console — a Facebook Page, a Zalo OA, a Telegram bot, an IMAP/SMTP mailbox — and who sets up what."
updated: "2026-08-28"
audience: [administrator]
source: "https://helpdesk-docs.svr1.feedapp.click/en/kenh"
---

This section connects each source of customer messages to your workspace, then
shows how to notice when one of them has stopped working. For what an inbox is
and what a channel is, read [Shared inboxes and channels](/en/khai-niem/inbox-va-kenh).

## Which channel to connect [#which-channel-to-connect]

| Channel           | What you need first                              | Guide                                                      |
| ----------------- | ------------------------------------------------ | ---------------------------------------------------------- |
| Facebook Page     | An account that administers the Page             | [Connect a Facebook Page](/en/kenh/ket-noi-facebook)       |
| Zalo OA           | An app on developers.zalo.me and OA admin rights | [Connect a Zalo Official Account](/en/kenh/ket-noi-zalo)   |
| Telegram          | A bot issued by @BotFather                       | [Connect a Telegram bot](/en/kenh/ket-noi-telegram)        |
| IMAP/SMTP mailbox | A mail address and an app password               | [Connect an IMAP/SMTP mailbox](/en/kenh/ket-noi-email)     |
| Website widget    | A domain to embed the snippet on                 | [Create your first channel](/en/bat-dau/tao-kenh-dau-tien) |

The **WhatsApp** and **API Hook** tiles still appear in the channel wizard, but
neither has a creation form yet: picking one answers **This channel cannot be
set up here yet.**

## Two roles, kept apart [#two-roles-kept-apart]

The three social channels run through **one** registration that belongs to the
whole installation, not one per person. Whoever deploys the system declares the
app and the webhook address once, in environment variables and on the third
party's own dashboard. Console users then connect each Page, each OA and each
bot by clicking.

Every page in this section names which role owns which step. Steps that belong
to the deployer point at the installation's `README.md` rather than repeating a
runbook here.

> **Note:** Connecting a channel is a write on channels, so an administrator can always
> do it and anybody else needs a permission group that allows it. See
> [Roles and per-feature permissions](/en/khai-niem/vai-tro-va-quyen).

## When a channel goes quiet [#when-a-channel-goes-quiet]

A broken channel makes no noise. A revoked token and a misdirected webhook both
leave the same single symptom: an empty queue.
[Spot and fix a disconnected channel](/en/kenh/suc-khoe-ket-noi) shows where the
console says so and how to re-check each kind of channel.