Merge pull request #42 from flashcatcloud/docs/fix-bot-at-mention-support

docs: fix bot @ mention support to match frontend

Author: ysyneu

en/on-call/configuration/notifications.mdx

@@ -292,7 +292,7 @@ All bot types support the following advanced options, accessible by expanding **
 | **Alias** | All | Set an alias for the bot to help remember and distinguish different notification channels |
 | **Severity filter** | All | Select which alert severity levels trigger notifications. Incidents with unselected severity levels will not be pushed |
 | **Notification event types** | Feishu/Lark, Dingtalk, WeCom, Slack, Zoom | Select which event types trigger notification pushes (e.g., triggered, acknowledged, closed). All selected by default |
-| **@ Mentions** | Dingtalk, Zoom | When enabled, @ mentions corresponding responders via user mapping. Dingtalk matches by phone number by default; Zoom requires a user mapping table |
+| **@ Mentions** | Feishu/Lark, Dingtalk, WeCom, Slack, Zoom | When enabled, @ mentions corresponding responders. Feishu/Lark and Zoom require a user mapping table; WeCom optionally supports one; Dingtalk matches by phone number by default. Dingtalk also supports @ all |
 
 <Tip>
 The user mapping table defines the correspondence between Flashduty users and IM platform users. You can create and maintain mapping tables on the **Platform Management** → **Mapping Table Management** page.
@@ -328,8 +328,10 @@ After adding the Incoming Webhook app in Zoom, use the `/inc connect flashduty`
 <Accordion title="Bot @ mentions are not working?">
 Verify the following:
 - The **@ mentions** toggle is enabled
-- A **user mapping table** is correctly selected (Zoom) or member phone numbers are correct (Dingtalk)
-- The user mappings in the table are correct and complete
+- Feishu/Lark, Zoom: a **user mapping table** is correctly selected with complete mappings
+- WeCom: if using a mapping table, verify the mappings are correct
+- Dingtalk: verify member phone numbers are correct
+- Slack: verify member account associations are correct
 </Accordion>
 </AccordionGroup>
 

zh/on-call/configuration/notifications.mdx

@@ -293,7 +293,7 @@ Flashduty App 是 On-call 工程师最高效的移动办公工具。无论您身
 | **别名** | 全部 | 为机器人设置别名，方便记忆和区分不同的通知渠道 |
 | **严重程度过滤** | 全部 | 选择需要推送通知的告警严重程度，未选中的严重程度对应的故障将不会推送 |
 | **触发通知事件类型** | 飞书、钉钉、企微、Slack、Zoom | 选择哪些事件类型触发通知推送（如触发、认领、关闭等），默认全选 |
-| **@ 提醒** | 钉钉、Zoom | 开启后通过用户信息映射 @ 提醒对应的处理人员。钉钉默认使用手机号匹配，Zoom 需配置用户信息映射表 |
+| **@ 提醒** | 飞书、钉钉、企微、Slack、Zoom | 开启后 @ 提醒对应的处理人员。飞书和 Zoom 需配置用户信息映射表，企微可选配置映射表，钉钉默认使用手机号匹配。钉钉还支持 @ 所有人 |
 
 <Tip>
 用户信息映射表定义了 Flashduty 用户与 IM 平台用户之间的对应关系。您可以在 **平台管理** → **映射表管理** 页面创建和维护映射表。
@@ -329,8 +329,10 @@ Flashduty App 是 On-call 工程师最高效的移动办公工具。无论您身
 <Accordion title="机器人的 @ 提醒不生效怎么办？">
 请确认以下事项：
 - 已开启 **@ 提醒** 开关
-- 已正确选择 **用户信息映射表**（Zoom）或确认成员手机号正确（钉钉）
-- 映射表中的用户映射关系正确且完整
+- 飞书、Zoom：已正确选择 **用户信息映射表**，映射关系正确且完整
+- 企微：如使用映射表，确认映射关系正确
+- 钉钉：确认成员手机号正确
+- Slack：确认成员账户关联正确
 </Accordion>
 </AccordionGroup>