CloudFly Helpdesk
Channels

Supported channels

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.

View .mdOpen llms.txt

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.

Which channel to connect

ChannelWhat you need firstGuide
Facebook PageAn account that administers the PageConnect a Facebook Page
Zalo OAAn app on developers.zalo.me and OA admin rightsConnect a Zalo Official Account
TelegramA bot issued by @BotFatherConnect a Telegram bot
IMAP/SMTP mailboxA mail address and an app passwordConnect an IMAP/SMTP mailbox
Website widgetA domain to embed the snippet onCreate your first channel

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

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.

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.

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 shows where the console says so and how to re-check each kind of channel.

On this page