Skip to main content
Xpert Tag brings Xpert digital experts into enterprise IM group chats and direct messages. Team members can mention a bot in Lark, DingTalk, or WeCom, hand work to a digital expert, and receive progress and results back in the same conversation.
Xpert already has the IM integration, trigger, conversation, aggregation, card/notification, and partial context-reading foundations. Features marked Planned are Xpert Tag product goals, not current production behavior.

Product Positioning

Xpert Tag is not a simple IM webhook bot, and it does not mean rewriting Lark, DingTalk, and WeCom into one plugin. It is a governed group-agent product experience built on the existing communication plugins and Xpert platform capabilities:
  • Groups become workspaces: project, support, alert, sales, and requirement groups can each have their own expert.
  • Access follows the group: administrators decide which knowledge bases, tools, plugins, and business systems a group can use.
  • Work is visible to the team: progress, key tool calls, results, and traceability return to the original chat or thread.
  • Results are more than chat: outputs can be summaries, docs, tickets, charts, metric analysis, code recommendations, or pull request links.
  • Team behavior can accumulate: rules, output formats, routines, and repeated workflows can become memory, routines, and skills.

Relationship To Existing IM Plugins

PlatformCurrent foundationXpert Tag product direction
Lark / FeishuLong connection or webhook, group mentions, DMs, conversation binding, group scopes, message aggregation, cards/updates, message history/resource reading, document-source support.Configure experts, knowledge, tools, memory, routines, and audit at the group/channel level.
DingTalkStream or HTTP, group mentions, DMs, conversation binding, aggregation, text/Markdown/interactive cards, card callbacks, update/recall.Use a unified Tag session, progress card, and group-level access model for long-running tasks.
WeComShort or long connection, DMs/groups, conversation binding, aggregation, template cards, streaming/thinking hints, image input, /new reset.Provide Tag behavior according to platform capabilities and clearly degrade unsupported group experiences.

Reused Xpert Capabilities

Xpert capabilityRole in Xpert TagStatus
Digital expertsThe task executor users mention in chats.Available foundation
WorkflowsGoverned business flows, routing, approval, extraction, and tool calls.Available foundation
Knowledge BaseGrounded answers, policy lookup, project materials, and document review.Available foundation
ToolsetsExternal APIs, data analysis, notifications, files, code, browser, and virtual environments.Available foundation
SkillsReusable team processes, output templates, and task rules.Available foundation
Schedule TriggerDaily reports, checks, syncs, and scheduled jobs.Available foundation
Coding ExpertGitHub, GitLab, Gitee, and Yunxiao issue, PR, and code tasks.Partially available
Group-level Access BundleReusable packages of knowledge, tools, credentials, model policy, budget, and write policy.Planned
Group memoryGroup rules, project facts, decisions, and output formats.Planned
Tag admin consoleA dedicated place for group, expert, access, memory, routine, audit, and usage management.Planned

Typical Experience

A project-group member sends:
@Xpert summarize this requirement discussion, draft a PRD, and list open questions.
The target Xpert Tag experience is:
  1. Create a Tag session bound to the group or thread.
  2. Read the current message, reply chain, authorized group context, attachments, knowledge, and tool configuration.
  3. Acknowledge the task and show a progress list or card.
  4. Call knowledge, data, ticketing, document, or code tools.
  5. Return the PRD draft, source summary, open questions, and next-action buttons in the group.
  6. Record the task, tool calls, results, and cost in audit and usage views.
Steps 1, 2, and 4 can already be composed from current IM triggers and digital expert capabilities. Unified Tag sessions, group access, live checklist, group memory, routines, and usage audit are productization goals.