Channel Capabilities

Mopheus connects Feishu, WeCom, and DingTalk through a shared channel engine. All three channels support chatting with agents through a bot, account binding, and sending ticket status changes and comments back to the originating conversation. Message context and presentation capabilities vary by platform.

Installation Records And Outbound Management

Workspace members can view installed channel records from the integrations list. The list shows only the channel, assigned agent or team, installation display name, and connection status. Credentials, external-user bindings, and message content are not exposed there.

Management capabilities depend on the installation and workspace permissions:

The installer can rename, view details, disconnect, and delete the installation.
Members with channel:bind can configure an installation and rename its display name.
Members with channel:delete can view details, disconnect, and delete the installation.
Members without management permission can still see the installation record, but cannot open its details or perform management actions.

Installation details show bound users, pending users, outbound messages, and inbound audit entries. Inbound audits contain only the channel type, external chat and message identifiers, event type, drop reason, and timestamp; raw message bodies and credentials are not exposed.

Agent replies, ticket status changes, and ticket comments are first recorded as outbound delivery entries and then sent by the service instance that currently maintains the channel connection. Failed entries retain their status and error details; only unexpired failed entries can be retried manually. Binding prompts also expire and are not sent after expiration.

Disconnecting an installation cancels outbound entries that have not been sent. Deleting an installation also removes its outbound records, inbound audits, and binding data. The original external conversation can no longer send through that installation after deletion.

Capability Matrix

Capability	Feishu	WeCom	DingTalk	Notes
Direct and group text messages	Yes	Yes	Yes	Group messages must satisfy the platform's bot-mention rules.
Group bot-mention filtering	Yes	Yes	Yes	WeCom only forwards addressed group messages; DingTalk uses its mention list.
Interactive card replies	Yes	No	No	Feishu uses an interactive card containing Markdown; WeCom and DingTalk send Markdown messages.
Thread replies	Yes	No	No	Feishu preserves topic and thread identifiers.
Quoted and forwarded-message expansion	Yes	No	No	Feishu expands explicitly quoted or forwarded content before processing.
Recent group-context prefetch	Yes, permission required	No	No	Triggered only when a group message mentions the bot; currently up to 10 messages.
Live provider message history	Yes	No	No	Only Feishu currently uses the provider message-list API.
Inbound images and files	Yes	Yes	Yes	Media is downloaded and stored as Mopheus attachments.
Processing indicator	Yes	No	Yes	Provided by the platform adapter.
Message editing	Yes	No	No	Not every channel can update an already-sent message.
Streaming updates to the same card	No	No	No	The final message is sent once after the task completes; cards are not updated continuously.
Account binding and ticket notifications	Yes	Yes	Yes	Uses the shared account-binding and ticket-source flow.

Feishu Recent Group Context

When Feishu receives a group message that mentions the bot, Mopheus attempts to fetch messages immediately before the trigger message from Feishu's message list and provides them to the agent as context. The current production fetch limit is 10 messages; the trigger message and its directly quoted parent are not duplicated in the recent-context block.

This capability requires the following permission in the Feishu app:

im:message.group_msg

Without this permission, the Feishu message is still received and processed, but recent context is skipped. This prefetch is a live provider API request; it does not read the conversation messages already stored by Mopheus.

Quoted replies, merged forwards, and recent group context are separate capabilities. The first two are triggered by an explicit quote or forward on the current message. Recent context is triggered only for a group message that mentions the bot.

See Feishu (Lark) Integration, WeCom Integration, and DingTalk Integration for platform-specific setup.