> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Connect an expert to Feishu, DingTalk, or QQ

After a channel is on, you message the expert from the chat app you already use, and the reply comes back in that thread. Each channel belongs to one expert.

Start here:

```text
Personalization → Channels
```

Select the expert at the top of the page, then open the platform.


![Channels](/images/en/ui-channels.png "Channels")

## Connect each platform

When a platform offers a scan, start there. Manual app setup sits at the end of each section, for organizations that require their own app.


**Feishu**

In the channel drawer, generate a Feishu AI bot QR code, scan it with Feishu **Scan**, and confirm on the phone. Octop fills in and saves the credentials. Send the bot a message and confirm a reply comes back. Replies inside a Feishu topic use the topic reply API (`reply_in_thread`).
The same flow is available in the terminal:
```bash
octop channel feishu-setup
```

**When your organization requires its own app**

Create an app in the [Feishu Open Platform](https://open.feishu.cn/) and copy the **App ID** and **App Secret**. Turn on **Feishu** under **Personalization → Channels** and fill in both values. Paste the callback URL Octop shows into **Event subscription** on the Feishu app, then save the Feishu settings.


**WeCom**

In the channel drawer, click **Generate WeCom scan code** and scan it with the WeCom mobile app. Or run `octop channel bind` and scan from the phone.

**When you need a self-built app**

Create a WeCom app and collect the **Corp ID**, **Agent ID**, and **Secret**. Turn on **WeCom**, fill in those three values, and add the callback URL Octop shows to the WeCom app.


**DingTalk**

1. Open **Personalization → Channels** and select **DingTalk**.
2. Stay on **Quick setup (scan)** and click **Generate DingTalk QR Code**.
3. Scan with the DingTalk app while signed in to the same organization, and confirm application creation.
4. After authorization, Octop creates and enables the channel.

**When you fill it in manually**

Switch to **Fill in manually**. Enter the **Client ID** and **Client Secret** from a bot you created in the [DingTalk Open Platform](https://open.dingtalk.com/). Copy the callback URL Octop shows into the app’s **Message receive mode**.


**QQ**

In the channel drawer, click **Generate QQ QR Code** and confirm with mobile QQ. Or run:
```bash
octop channel bind qq --agent main
```
For groups, you can set visibility (`auto`, `all`, `mention_recent`, or `mention_only`). When visibility is `all`, reply timing can be `mention` or `always`.
QQ direct chat defaults to official `stream_messages`. Saving the channel writes `c2c_streaming: true`. Set `c2c_streaming: false` only when you want a single static reply. The old keys `streaming` and `response_mode` do nothing for direct chat. Group, channel, and channel-DM chats have no stream API and stay static. Tool-progress bubbles use extra passive-reply quota, about four per inbound message.

**When you paste an App ID instead**

Turn on **QQ**, fill in the **App ID** and **Client Secret** from the open platform, and save.


**Telegram**

Create a bot with [@BotFather](https://t.me/BotFather) and copy the **Bot Token**. Open **Personalization → Channels → More channels**.

![Telegram channel](/images/en/ui-channel-telegram.png "Telegram")

1. Select **Telegram**.
2. Paste the **Bot Token**.
3. Optionally fill **Allowed Telegram user IDs** (comma or newline separated). Leave it empty to allow anyone the bot can see.
4. Turn on **Enable channel** and save.

> **WARNING**
> 
> Keep the Bot Token private. If it leaks, revoke it in BotFather and update the channel in Octop.
> 



**Discord**

Create a bot in the [Discord Developer Portal](https://discord.com/developers/applications), copy the **Bot Token**, and invite the bot to your server with message permissions.

![Discord channel](/images/en/ui-channel-discord.png "Discord")

1. Under **Personalization → Channels → More channels**, select **Discord**.
2. Paste the Bot Token. You do not need a public key or client secret.
3. By default the bot can use every text channel it can access. Turn off **Allow all accessible channels** and list channel IDs for a tighter scope. For DMs, fill allowed Discord user IDs. Empty means no DMs.
4. Turn the channel on and save.


**Others**

**WeChat** and **Yuanbao** can also bind from a QR code in the drawer. For **Xiaoyi** and **MQTT**, turn the channel on and fill in the credentials that platform asks for.


## How replies show up in a group

Open the channel settings drawer and use **Message display → Response mode**:

- **Final only** sends one completed reply after the expert finishes. Progress narration before tool calls stays out of IM. Generated media arrives with the final text. Use this in a group.
- **Live progress** keeps staged updates. Use it when people need to follow the work.

External IM channels created in the web UI start on **Live progress**. **Show Thinking** and **Show tool hints** stay separate. QQ private chat ignores this switch and uses `c2c_streaming` instead.


> **WARNING**
> 
> A credential is control of the bot. Keep it on this Octop. Do not paste it into a chat log.
> 



> **TIP**
> 
> Terminal commands `list`, `test`, `delete`, `feishu-setup`, and `bind` are in [Channel and cron commands](/en/cli/channel-cron-commands.md#octop-channel).
> 

