Skip to main content
The administrator setup goal for Xpert Tag is to connect enterprise IM platforms to Xpert, then configure groups, digital experts, knowledge, tools, access, and budget in one product area.
Today, setup is done by combining system integrations, plugin triggers, and digital expert workflows. A dedicated Tag admin console is Planned.

​
Setup Flow

  1. Install the communication plugin at tenant level.
  2. Create a Lark, DingTalk, or WeCom system integration.
  3. Add the matching Trigger to the target digital expert workflow.
  4. Select the integration and configure session timeout, message aggregation, group scope, or DM scope.
  5. Connect downstream Agent, knowledge, toolset, skill, and business-process nodes.
  6. Publish the digital expert.
  7. Invite the bot into the target group or test a direct message.
The future Tag admin console should compress steps 2 through 6 into “create Tag app -> choose IM -> choose group -> bind expert -> bind capability package -> test and launch”.

​
Platform Preparation

​
Bind Digital Experts

Current triggers use an explicit binding model:
  • Lark, DingTalk, and WeCom triggers bind one integrationId to one xpertId.
  • A single IM integration usually binds to one digital expert at a time, preventing one bot message from triggering multiple experts.
  • Conversation bindings take priority over trigger bindings, so an active conversation continues with the same expert until timeout.
  • Users can end or reset conversations through supported card actions or /new-style commands, depending on the plugin.
After Tag productization, administrators should be able to configure the default digital expert at group/channel level, and route to different experts through mentions, commands, or skills.

​
Future Tag Admin Console

These capabilities are Planned:

​
Launch Checklist

Before enabling a group, administrators should confirm:
  • The IM app is published, bot capability is enabled, and webhook/long connection works.
  • The bot has joined the target group and the group trigger strategy matches expectations.
  • The trigger is published and points to the correct integration.
  • The digital expert has the required knowledge bases, toolsets, and skills.
  • Write tools require confirmation or approval by default.
  • Sensitive data, files, and images comply with company policy.
  • Pilot users know which features are live and which are Planned.