service-itsm-channels-coordinate

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Employee Service (ITSM) Channels Setup Coordinator

员工服务(ITSM)渠道设置协调器

Interactive coordinator that presents a menu of ITSM channel setup options and delegates to the appropriate child skill based on user selection.
交互式协调器,用于展示ITSM渠道设置选项菜单,并根据用户选择委派至对应的子skill。

Scope

适用范围

  • In scope: Presenting the channel setup menu to the user. Delegating to child skills based on selection (Teams, Swarming, Portal). Validating prerequisites before delegation. Providing clear descriptions of each channel capability. Notifications is the one exception — no dedicated notifications child skill exists yet, so this coordinator enables the notification-channel org preferences inline for that choice (see Choice 4); those are the only setup-API writes it performs itself.
  • Out of scope: Directly calling setup APIs for any channel that has a dedicated child skill (Teams, Swarming, Portal — always delegate). Channel-specific configuration details beyond the initial enablement. User permission assignment. Post-setup testing.

  • 纳入范围:向用户展示渠道设置菜单;根据选择委派至子skill(Teams、Swarming、Portal);委派前验证前提条件;提供各渠道功能的清晰说明。Notifications是唯一例外——目前尚无专用的通知子skill,因此本协调器会在用户选择该选项时直接启用通知渠道的组织偏好设置(见选项4);这是它自行执行的唯一设置API写入操作。
  • 排除范围:直接调用任何已有专用子skill的渠道的设置API(Teams、Swarming、Portal——始终委派);初始启用之外的渠道特定配置细节;用户权限分配;设置后的测试。

Available Channel Setup Skills

可用渠道设置Skill

This coordinator can invoke five distinct channel setup skills:
本协调器可调用五种不同的渠道设置skill:

1. Microsoft Teams Setup

1. Microsoft Teams 设置

Skill:
service-itsm-teams-configure
What it does:
  • Enables the
    service-cloud-itsm-teams-integration
    Salesforce Go feature via headless-360's feature-enablement Connect API — the only verified path that flips
    ITSMTeamsEnabled
    (direct PATCH of the org preference is blocked with 401)
  • Optionally enables the sibling
    OrgHasITSMFulfillerTeams
    /
    OrgHasEmployeeServiceTeams
    preferences
  • Verifies
    ITSMTeamsEnabled
    afterward and reports the remaining manual (Microsoft-side) steps
Prerequisites:
  • Teams ITSM add-on licenses
  • Setup admin permissions
Use when: User wants Microsoft Teams integration for IT Service Desk or Employee Service apps.
Teams sub-skills
service-itsm-teams-configure
delegates to (surface these if the user asks for a specific half):
service-itsm-teams-itdesk-configure
(fulfiller/IT Desk checklist),
service-itsm-teams-itservice-configure
(employee/IT Service checklist),
service-itsm-teams-employee-agent-configure
(embedded "Ask AI Agent"), and
service-itsm-teams-debug
(diagnose a failing Teams setup — login, tab loading, agent, swarming, SSO).

Skill:
service-itsm-teams-configure
功能:
  • 通过headless-360的功能启用Connect API启用
    service-cloud-itsm-teams-integration
    Salesforce Go功能——这是切换
    ITSMTeamsEnabled
    状态的唯一验证路径(直接PATCH组织偏好会被401拦截)
  • 可选启用关联的
    OrgHasITSMFulfillerTeams
    /
    OrgHasEmployeeServiceTeams
    偏好
  • 之后验证
    ITSMTeamsEnabled
    状态,并报告剩余的手动(Microsoft端)步骤
前提条件:
  • Teams ITSM附加许可证
  • 设置管理员权限
适用场景: 用户希望为IT服务台或员工服务应用集成Microsoft Teams。
service-itsm-teams-configure
委派的Teams子skill
(若用户询问具体分支可展示):
service-itsm-teams-itdesk-configure
(服务台/IT Desk checklist)、
service-itsm-teams-itservice-configure
(员工/IT Service checklist)、
service-itsm-teams-employee-agent-configure
(嵌入式“Ask AI Agent”)、
service-itsm-teams-debug
(诊断失败的Teams设置——登录、标签加载、agent、swarming、SSO)。

2. Slack Setup

2. Slack 设置

Skill: the installed Slack ITSM setup skill — resolve it from the skills catalog at delegation time by name pattern (see Choice 2 in the workflow); do not hardcode a single skill name.
What it does:
  • Enables Slack integration for ITSM (Employee Service / IT Service on Slack)
  • Configures the Slack workspace connection and required org preferences/permission sets
Prerequisites:
  • Slack workspace with admin access
  • Org has Slack integration enabled
Use when: User wants Slack integration for ITSM.

Skill: 已安装的Slack ITSM设置skill——委派时通过技能目录按名称模式解析(见工作流中的选项2);请勿硬编码单个skill名称。
功能:
  • 为ITSM启用Slack集成(Slack上的员工服务/IT服务)
  • 配置Slack工作区连接及所需的组织偏好/权限集
前提条件:
  • 拥有管理员权限的Slack工作区
  • 组织已启用Slack集成
适用场景: 用户希望为ITSM集成Slack。

3. Swarming Setup

3. Swarming 设置

Skill:
service-itsm-swarming-configure
What it does:
  • Enables the
    service-cloud-swarming
    Salesforce Go feature via headless-360's feature-enablement Connect API
  • Sets the "Select a Collaboration Tool" picklist to
    Teams
    via
    PATCH /services/data/v67.0/setup/org/values/SWARM_COLLABORATION_TOOL
    — fully automated, no manual click required
Prerequisites:
  • Microsoft Teams integration (Swarming requires Teams — run
    service-itsm-teams-configure
    first)
Use when: User wants collaborative problem-solving for ITSM.

Skill:
service-itsm-swarming-configure
功能:
  • 通过headless-360的功能启用Connect API启用
    service-cloud-swarming
    Salesforce Go功能
  • 通过
    PATCH /services/data/v67.0/setup/org/values/SWARM_COLLABORATION_TOOL
    将“选择协作工具”选择列表设置为
    Teams
    ——完全自动化,无需手动点击
前提条件:
  • Microsoft Teams集成(Swarming需要Teams——先运行
    service-itsm-teams-configure
适用场景: 用户希望为ITSM启用协作式问题解决功能。

4. Notifications Setup

4. Notifications 设置

Skill: none yet — handled inline by this coordinator (see Choice 4)
What it does:
  • Enables the master Notifications feature
  • Configures notification channels: Email, In-App, Slack, Teams
Prerequisites:
  • Multi-channel Notifications feature enabled
  • View Setup + Customize Application permissions
Use when: User wants to enable multi-channel notifications for ITSM events.
Note: For demo, execute inline until dedicated skill is created.

Skill: 暂无——由本协调器直接处理(见选项4)
功能:
  • 启用主通知功能
  • 配置通知渠道:邮件、应用内、Slack、Teams
前提条件:
  • 已启用多渠道通知功能
  • 拥有查看设置+自定义应用权限
适用场景: 用户希望为ITSM事件启用多渠道通知。
注意: 演示阶段,在专用skill创建前直接执行此流程。

5. Portal Setup

5. Portal 设置

Skill:
experience-portal-create
What it does:
  • Creates a Digital Experience portal for employee self-service
  • Supports Employee Service, Partner, and Customer portals
Prerequisites:
  • Vary by portal type
Use when: User wants to create a portal for employee self-service.

Skill:
experience-portal-create
功能:
  • 创建用于员工自助服务的Digital Experience门户
  • 支持员工服务、合作伙伴和客户门户
前提条件:
  • 因门户类型而异
适用场景: 用户希望创建员工自助服务门户。

Workflow

工作流

Step 1: Present Menu to User

步骤1:向用户展示菜单

Always present the menu before proceeding:
text
I can help you set up ITSM channels. Which channel would you like to configure?

**Choose one:**

1. **Microsoft Teams Setup**
   - Enable Teams integration master toggle
   - Provision authentication infrastructure
   - Prerequisites: Teams ITSM licenses required

2. **Slack Setup**
   - Enable Slack integration for ITSM
   - Configure Slack workspace connection
   - Prerequisites: Slack workspace with admin access

3. **Swarming Setup**
   - Enable Swarming for collaborative problem-solving
   - Configure Swarming channels (requires Teams)
   - Prerequisites: Teams integration + Swarming feature

4. **Notifications Setup**
   - Enable multi-channel notifications (Email, In-App, Slack, Teams)
   - Configure notification delivery channels
   - Prerequisites: Multi-channel Notifications feature

5. **Portal Setup**
   - Create Digital Experience portal for employee self-service
   - Choose portal type during setup
   - Prerequisites: Vary by portal type

Please respond with the number (1, 2, 3, 4, or 5) of your choice.
Do NOT proceed until the user provides a choice.

始终先展示菜单再继续:
text
我可以帮您设置ITSM渠道。您想要配置哪个渠道?

**请选择一项:**

1. **Microsoft Teams 设置**
   - 启用Teams集成主开关
   - 部署身份验证基础架构
   - 前提条件:需要Teams ITSM许可证

2. **Slack 设置**
   - 为ITSM启用Slack集成
   - 配置Slack工作区连接
   - 前提条件:拥有管理员权限的Slack工作区

3. **Swarming 设置**
   - 启用Swarming协作式问题解决功能
   - 配置Swarming渠道(需要Teams)
   - 前提条件:Teams集成 + Swarming功能

4. **Notifications 设置**
   - 启用多渠道通知(邮件、应用内、Slack、Teams)
   - 配置通知交付渠道
   - 前提条件:多渠道通知功能

5. **Portal 设置**
   - 创建用于员工自助服务的Digital Experience门户
   - 设置期间选择门户类型
   - 前提条件:因门户类型而异

请回复您选择的编号(1、2、3、4或5)。
用户未做出选择前请勿继续

Step 2: Validate Prerequisites

步骤2:验证前提条件

Based on user's choice, check prerequisites before delegating to child skills:
根据用户选择,在委派至子skill前检查前提条件:

For Choice 1 or 3 (Teams Integration):

选项1或3(Teams集成):

  1. Check if Teams master toggle API is accessible
  2. Attempt to query current toggle state
  3. If prerequisites fail, inform user about missing Teams ITSM licenses
  1. 检查Teams主开关API是否可访问
  2. 尝试查询当前开关状态
  3. 若前提条件不满足,告知用户缺少Teams ITSM许可证

For Choice 2 or 4 (Notifications):

选项2或4(Notifications):

  1. Check if Notifications preference APIs are accessible
  2. Verify Multi-channel Notifications feature is available
If prerequisites fail:
  • Explain what's missing (licenses, features, permissions)
  • Offer alternative choices (e.g., suggest #4 if Teams licenses missing)
  • Do NOT attempt to execute the chosen configuration

  1. 检查通知偏好API是否可访问
  2. 验证多渠道通知功能是否可用
若前提条件不满足:
  • 说明缺失的内容(许可证、功能、权限)
  • 提供替代选项(例如,若缺少Teams许可证,建议选择选项4)
  • 请勿尝试执行所选配置

Step 3: Delegate to Child Skill

步骤3:委派至子Skill

Choice 1: Microsoft Teams Setup

选项1:Microsoft Teams 设置

Delegation:
text
Invoke the service-itsm-teams-configure skill.
On success: "Success: Microsoft Teams integration master toggle is enabled. Background provisioning in progress (2-5 minutes).
Next steps:
  • Configure Azure AD application
  • Set up Salesforce IT Desk and/or IT Service apps"
On failure: "Failed: Teams integration failed: [error details]
Resolution:
  • Verify org has Teams ITSM licenses
  • Try option #4 (Notifications) instead"

委派指令:
text
调用service-itsm-teams-configure skill。
成功时: "成功:Microsoft Teams集成主开关已启用。后台部署进行中(2-5分钟)。
下一步:
  • 配置Azure AD应用
  • 设置Salesforce IT Desk和/或IT Service应用"
失败时: "失败:Teams集成失败:[错误详情]
解决方案:
  • 验证组织是否拥有Teams ITSM许可证
  • 尝试改用选项4(Notifications)"

Choice 2: Slack Setup

选项2:Slack 设置

Resolve the delegation target deterministically from the skills catalog, then invoke the result. Do not decide by prose guesswork — look the skill up:
text
1. Query the installed skills catalog for a Slack ITSM setup skill, in priority order:
     a. any skill whose name matches ^service-itsm-slack-.*-configure$   (preferred)
     b. any skill whose name matches ^(setup|service)-.*slack.*(configure|enable)$
2. If the lookup returns a skill → invoke that exact skill and stop.
3. If the lookup returns nothing → fall through to the manual instructions below.
Manual instructions (only if the catalog lookup returned no Slack skill): "No Slack ITSM setup skill is installed in this environment. To configure Slack manually:
  1. Navigate to: Setup → Integrations → Slack
  2. Connect your Slack workspace
  3. Configure Slack apps for ITSM"

从技能目录中确定性地解析委派目标,然后调用结果。 请勿通过文本猜测判断——需查询技能目录:
text
1. 按优先级查询已安装的技能目录,查找Slack ITSM设置skill:
     a. 名称匹配^service-itsm-slack-.*-configure$的skill(优先选择)
     b. 名称匹配^(setup|service)-.*slack.*(configure|enable)$的skill
2. 若查询到skill → 调用该skill并停止流程。
3. 若未查询到skill → 执行下方的手动操作说明。
手动操作说明(仅当目录未查询到Slack skill时): "当前环境未安装Slack ITSM设置skill。手动配置Slack步骤:
  1. 导航至:设置 → 集成 → Slack
  2. 连接您的Slack工作区
  3. 为ITSM配置Slack应用"

Choice 3: Swarming Setup

选项3:Swarming 设置

Delegation:
text
Invoke the service-itsm-swarming-configure skill.
On success: "Success: Swarming feature enabled, and the Collaboration Tool is now set to Teams — 'Set Teams as Collaboration Tool for Swarming' is fully complete, no manual click needed."
On failure: "Failed: Swarming setup failed: [error details]
Resolution:
  • Ensure Microsoft Teams integration is enabled first (use option #1)
  • Verify org has the Swarming feature entitlement"

委派指令:
text
调用service-itsm-swarming-configure skill。
成功时: "成功:Swarming功能已启用,协作工具已设置为Teams——'将Teams设为Swarming协作工具'已完全完成,无需手动点击。"
失败时: "失败:Swarming设置失败:[错误详情]
解决方案:
  • 确保已先启用Microsoft Teams集成(使用选项1)
  • 验证组织拥有Swarming功能权限"

Choice 4: Notifications Setup

选项4:Notifications 设置

Inline enablement (in-scope exception — no dedicated notifications child skill exists yet). Unlike the other choices, this branch enables the notification-channel org preferences itself. Issue the writes with
mcp__headless-360__dispatch
(
PATCH
, full
/services/data/vXX.0/...
path). When a dedicated
setup-itsm-notifications-*
child skill lands, delegate to it and drop this inline block.
Step 4.1: Enable Master Notifications Preference
text
PATCH /services/data/v66.0/setup/org/preferences/Notifications
Body: {"desiredState": true}
Step 4.2: Enable Individual Channels
text
PATCH /services/data/v66.0/setup/org/preferences/EmailNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/InAppNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/SlackNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/TeamsNotifications
Body: {"desiredState": true}
On success: "Success: All notification channels enabled:
  • Email Notifications
  • In-App Notifications
  • Slack Notifications
  • Teams Notifications
Next steps:
  • Create notification definitions at: Setup → Service → Notifications
  • Configure ITSM event triggers
  • Customize message templates"
On failure: "Failed: Notification channels setup failed: [error details]
Resolution:
  • Verify org has Multi-channel Notifications feature
  • Confirm you have Customize Application permission"

直接启用(纳入范围的例外——目前尚无专用通知子skill)。 与其他选项不同,此分支由协调器直接启用通知渠道的组织偏好设置。通过
mcp__headless-360__dispatch
发出写入请求(
PATCH
方法,完整
/services/data/vXX.0/...
路径)。当专用的
setup-itsm-notifications-*
子skill上线后,将委派至该skill并移除本直接执行模块。
步骤4.1:启用主通知偏好
text
PATCH /services/data/v66.0/setup/org/preferences/Notifications
Body: {"desiredState": true}
步骤4.2:启用各渠道
text
PATCH /services/data/v66.0/setup/org/preferences/EmailNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/InAppNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/SlackNotifications
Body: {"desiredState": true}

PATCH /services/data/v66.0/setup/org/preferences/TeamsNotifications
Body: {"desiredState": true}
成功时: "成功:所有通知渠道已启用:
  • 邮件通知
  • 应用内通知
  • Slack通知
  • Teams通知
下一步:
  • 在设置 → 服务 → 通知中创建通知定义
  • 配置ITSM事件触发器
  • 自定义消息模板"
失败时: "失败:通知渠道设置失败:[错误详情]
解决方案:
  • 验证组织已启用多渠道通知功能
  • 确认您拥有自定义应用权限"

Choice 5: Portal Setup

选项5:Portal 设置

Delegation:
text
Invoke the experience-portal-create skill.
The portal creation skill will handle all clarifying questions (portal type, name, URL prefix, etc.).
After delegation: "Success: Portal setup delegated to experience-portal-create skill. Follow the prompts to complete portal creation."

委派指令:
text
调用experience-portal-create skill。
门户创建skill将处理所有澄清问题(门户类型、名称、URL前缀等)。
委派后: "成功:门户设置已委派至experience-portal-create skill。请按照提示完成门户创建。"

Decision Tree

决策树

text
User requests ITSM channel setup
Present menu (5 options)
User selects option (1-5)
Validate prerequisites (optional)
  ├─ Choice 1: Invoke service-itsm-teams-configure
  ├─ Choice 2: Resolve the Slack skill from the catalog, then invoke it (or manual instructions)
  ├─ Choice 3: Invoke service-itsm-swarming-configure
  ├─ Choice 4: Execute notifications setup inline (demo mode)
  └─ Choice 5: Invoke experience-portal-create
Report outcome to user
Suggest next steps

text
用户请求ITSM渠道设置
展示菜单(5个选项)
用户选择选项(1-5)
验证前提条件(可选)
  ├─ 选项1:调用service-itsm-teams-configure
  ├─ 选项2:从目录中解析Slack skill,然后调用(或执行手动说明)
  ├─ 选项3:调用service-itsm-swarming-configure
  ├─ 选项4:直接执行通知设置(演示模式)
  └─ 选项5:调用experience-portal-create
向用户报告结果
建议下一步操作

Rules / Constraints

规则/约束

ConstraintRationale
Always present options before proceedingUser may not know what's possible or what their org supports
Validate prerequisites before delegatingCatch licensing/feature gaps early before invoking child skills
Choice 4 uses manual API calls, not a child skillNo existing skill for "notifications without specific channels"
Do not retry failed delegationsChild skills handle their own retries; surfacing error to user for decision
Partial success is acceptableIf Teams succeeds but Notifications fails, user can retry Notifications separately

约束理由
始终先展示选项再继续用户可能不清楚可用选项或组织支持的功能
委派前验证前提条件在调用子skill前尽早发现许可证/功能缺口
选项4使用手动API调用,而非子skill目前尚无“无特定渠道的通知”相关skill
不重试失败的委派子skill自行处理重试;向用户展示错误以便决策
允许部分成功若Teams设置成功但Notifications失败,用户可单独重试Notifications

Prerequisites by Choice

各选项的前提条件

Choice 1: Teams Setup

选项1:Teams 设置

  • Teams ITSM licenses
  • Setup admin permissions
  • Teams ITSM许可证
  • 设置管理员权限

Choice 2: Slack Setup

选项2:Slack 设置

  • Slack workspace with admin access
  • Org has Slack integration enabled
  • 拥有管理员权限的Slack工作区
  • 组织已启用Slack集成

Choice 3: Swarming Setup

选项3:Swarming 设置

  • Microsoft Teams integration (required for Swarming — run Choice 1 first)
  • Microsoft Teams集成(Swarming必需——先执行选项1)

Choice 4: Notifications Setup

选项4:Notifications 设置

  • Multi-channel Notifications feature enabled
  • View Setup + Customize Application permissions
  • 已启用多渠道通知功能
  • 拥有查看设置+自定义应用权限

Choice 5: Portal Setup

选项5:Portal 设置

  • Vary by portal type (see experience-portal-create skill)

  • 因门户类型而异(详见experience-portal-create skill)

Error Handling

错误处理

If user provides invalid choice:

若用户提供无效选择:

"Please choose a valid option: 1, 2, 3, 4, or 5."
"请选择有效选项:1、2、3、4或5。"

If prerequisites check fails:

若前提条件检查失败:

"I've detected that your org is missing [specific requirement].
I recommend choosing [alternative option] instead, which works with your current org configuration."
"我检测到您的组织缺少[具体要求]。
我建议您选择[替代选项],该选项适用于当前组织配置。"

If delegation fails:

若委派失败:

"The [child skill name] encountered an error: [error message]
[Provide specific resolution steps based on error]"
"[子skill名称]遇到错误:[错误消息]
[根据错误提供具体解决方案]"

If user is unsure which to choose:

若用户不确定选择哪个选项:

"Let me help you decide:
  • Do you want to enable communication channels?
    • Microsoft Teams → Choose #1
    • Slack → Choose #2
    • Both → Run #1, then #2
  • Do you want collaborative problem-solving?
    • Swarming (requires Teams) → Choose #1 first, then #3
  • Do you want notifications for ITSM events?
    • Multi-channel notifications → Choose #4
  • Do you want a portal for employee self-service?
    • Digital Experience portal → Choose #5"

"我来帮您决定:
  • 您是否想启用沟通渠道?
    • Microsoft Teams → 选择#1
    • Slack → 选择#2
    • 两者都要 → 先执行#1,再执行#2
  • 您是否需要协作式问题解决功能?
    • Swarming(需要Teams)→ 先选择#1,再选择#3
  • 您是否想接收ITSM事件通知?
    • 多渠道通知 → 选择#4
  • 您是否需要员工自助服务门户?
    • Digital Experience门户 → 选择#5"

Related Operations

相关操作

After completing channel setup via this coordinator:
  • Configure channel-specific settings — customize each channel's behavior
  • Create notification definitions — configure ITSM event triggers (if Notifications selected)
  • Set up Azure AD — required for Teams (if Teams selected)
  • Test channels — verify each channel is working
To modify later:
  • Enable additional channels — rerun this coordinator with different option
  • Disable channels — use corresponding disable skills
  • Update channel settings — navigate to Setup → [Channel] → Settings

通过本协调器完成渠道设置后:
  • 配置渠道特定设置——自定义各渠道的行为
  • 创建通知定义——配置ITSM事件触发器(若选择了Notifications)
  • 设置Azure AD——Teams必需(若选择了Teams)
  • 测试渠道——验证各渠道正常运行
后续修改操作:
  • 启用额外渠道——重新运行本协调器并选择不同选项
  • 禁用渠道——使用对应的禁用skill
  • 更新渠道设置——导航至设置 → [渠道] → 设置

Embedded Agentforce Agent in Microsoft Teams

Microsoft Teams中的嵌入式Agentforce Agent

Making the embedded Agentforce agent actually reply inside the Teams custom client ("Salesforce Employee Assist" / "Ask AI Agent") is the hardest, most under-documented part of Teams ITSM. It is now a dedicated skill:
service-itsm-teams-employee-agent-configure
The verified architecture is a Web Enhanced-messaging channel with User Verification OFF (auth mode false) — the Teams client uses the scrt2 unauthenticated token endpoint — the
Teams_AgentForce
custom-client Embedded Service Deployment, an Omni-Flow routing flow targeting a real, Active Agentforce Employee Agent, and an Agent Access permission set enabling that agent for the portal user. That skill also covers the key diagnostic: "agent joins then leaves without replying" has two fixable causes — auth mode left ON (→
/eventrouter/v1/sse
401) and the portal user missing Agent Access — not an unfixable agent-runtime failure.

让嵌入式Agentforce agent在Teams自定义客户端(“Salesforce Employee Assist”/“Ask AI Agent”)中真正回复消息是Teams ITSM中最复杂、文档最不完善的部分。现在已有专用skill:
service-itsm-teams-employee-agent-configure
经验证的架构是Web增强消息渠道,且用户验证关闭(auth mode false)——Teams客户端使用scrt2 未认证令牌端点——
Teams_AgentForce
自定义客户端嵌入式服务部署,针对真实、活跃
的Agentforce员工agent的Omni-Flow路由流,以及为门户用户启用该agent的Agent Access权限集。该skill还涵盖关键诊断:“agent加入后立即离开且未回复”有两个可修复原因——auth mode仍为开启状态(→
/eventrouter/v1/sse
401错误)和门户用户缺少Agent Access权限——并非无法修复的agent运行时故障。

API Type Classification

API类型分类

This coordinator:
  • Does NOT call APIs directly (except for Choice 4 demo mode) — it delegates to child skills
  • Uses interactive menu for user selection
  • Child skills handle all API calls
Child skills used:
  • service-itsm-teams-configure
    — headless-360 (Salesforce Go feature-enablement Connect API)
  • Slack ITSM setup skill (resolved from catalog by name pattern) — child skill handles its own API calls
  • service-itsm-swarming-configure
    — headless-360 (Salesforce Go feature-enablement Connect API)
  • Notifications — no dedicated child skill yet; handled inline via Connect API (see Choice 4)
  • experience-portal-create
    — Connect API

本协调器:
  • 不直接调用API(选项4演示模式除外)——它仅委派至子skill
  • 使用交互式菜单供用户选择
  • 所有API调用由子skill处理
使用的子skill:
  • service-itsm-teams-configure
    ——headless-360(Salesforce Go功能启用Connect API)
  • Slack ITSM设置skill(通过名称模式从目录解析)——子skill自行处理API调用
  • service-itsm-swarming-configure
    ——headless-360(Salesforce Go功能启用Connect API)
  • Notifications——尚无专用子skill;通过Connect API直接处理(见选项4)
  • experience-portal-create
    ——Connect API

Important Notes

重要说明

  1. This is an interactive coordinator — it MUST present the menu and wait for user choice before executing anything.
  2. Always delegate to child skills — this coordinator doesn't implement channel-specific logic; it only routes to the appropriate skill.
  3. Some skills may not exist yet — if a skill is not found, provide manual setup instructions so the user isn't blocked.
  4. Choice 4 (Notifications) executes inline — no dedicated notifications child skill exists yet, so this coordinator enables the notification-channel preferences directly (see Choice 4). When such a skill lands, delegate to it and drop the inline block.
  5. Prerequisites vary by channel — each channel has different licensing and feature requirements.
  6. No retry logic — this coordinator doesn't retry failed operations. Surface the error and let user decide next steps.
  7. Educational role — help users understand what each channel does and which prerequisites they need.
  1. 这是交互式协调器——必须先展示菜单并等待用户选择,才能执行任何操作。
  2. 始终委派至子skill——本协调器不实现渠道特定逻辑;仅负责路由至合适的skill。
  3. 部分skill可能尚未存在——若未找到skill,需提供手动设置说明,避免用户受阻。
  4. 选项4(Notifications)直接执行——目前尚无专用通知子skill,因此本协调器直接启用通知渠道偏好设置(见选项4)。当此类skill上线后,将委派至该skill并移除本直接执行模块。
  5. 各渠道前提条件不同——每个渠道有不同的许可证和功能要求。
  6. 无重试逻辑——本协调器不重试失败操作。展示错误并让用户决定下一步操作。
  7. 教育引导作用——帮助用户了解各渠道功能及所需前提条件。