Merge pull request #34 from flashcatcloud/doc-review/2026-03-26-webhook-disambiguation

docs: add webhook disambiguation to escalation rules

Author: ysyneu

en/on-call/channel/escalation-rule.mdx

@@ -71,6 +71,10 @@ Determines how users are reached.
 
     - **IM App Groups**: Supports Feishu/Lark, Dingtalk, WeCom, Slack, and Microsoft Teams groups, requires completing [IM Integration](/en/on-call/integration/instant-messaging/lark) first
     - **Group Bots**: Supports Feishu/Lark, Dingtalk, WeCom, Telegram, Zoom, and other Webhook bots. Telegram requires configuring a Webhook notification address and Chat IDs, Zoom requires configuring a Webhook address and Verify Token, and supports enabling @ mention functionality. See [Notification Channel Configuration](/en/on-call/configuration/notifications)
+
+    <Note>
+    **Don't use any of the above IM platforms?** You can select any bot type and set the webhook URL to your own server endpoint (the system does not validate domains), then implement the corresponding message protocol on your server. See [FAQ](/en/on-call/quickstart/faq#i-dont-use-feishudingtalkwecomtelegram--how-can-i-receive-bot-notifications).
+    </Note>
   </Tab>
 </Tabs>
 
@@ -123,6 +127,14 @@ The minimum escalation timeout is 1 minute.
 
     Go to Channel Details → **Escalation Rules** to check current settings.
   </Accordion>
+  <Accordion title="What's the difference between webhook integrations and group bot webhooks?" icon="circle-question">
+    These are two different features — do not confuse them:
+
+    - **Webhook integrations** ([Alert Webhook](/en/on-call/integration/webhooks/alert-webhook), [Incident Webhook](/en/on-call/integration/webhooks/incident-webhook)): When alerts or incidents change, Flashduty pushes event data to your configured URL for integration with external systems (e.g., ticketing systems, automation platforms)
+    - **Group bot webhooks** (this page, "Notification Methods → Group Chat"): Configure an IM group bot's webhook URL in escalation rules so Flashduty sends incident notification messages to the group chat
+
+    In short: webhook integrations are for **data export**, group bots are for **notification delivery**.
+  </Accordion>
 </AccordionGroup>
 
 ## Related Topics

zh/on-call/channel/escalation-rule.mdx

@@ -72,6 +72,10 @@ src="https://download.flashcat.cloud/flashduty/video/escalate-rule.mp4"
 
     - **IM 应用群**：支持飞书、钉钉、企业微信、Slack、Microsoft Teams 群，需先完成 [IM 集成](/zh/on-call/integration/instant-messaging/lark)
     - **群机器人**：支持飞书、钉钉、企业微信、Telegram、Zoom 等 Webhook 机器人。其中 Telegram 需要配置 Webhook 通知地址和群聊 ID（Chat Ids），Zoom 需要配置 Webhook 地址和 Verify Token，并支持开启 @ 提醒功能。详见 [通知渠道配置](/zh/on-call/configuration/notifications)
+
+    <Note>
+    **不使用上述 IM 平台？** 您可以选择任意一种机器人类型，将 Webhook 地址填写为您自己的服务端 URL（系统不会校验域名），然后在服务端实现对应的消息协议即可。详见[常见问题](/zh/on-call/quickstart/faq#我没有飞书钉钉企微telegram如何接收机器人通知)。
+    </Note>
   </Tab>
 </Tabs>
 
@@ -124,6 +128,14 @@ src="https://download.flashcat.cloud/flashduty/video/escalate-rule.mp4"
 
     前往 协作空间详情 → **分派策略** 查看当前设定。
   </Accordion>
+  <Accordion title="Webhook 集成和群机器人 Webhook 有什么区别？" icon="circle-question">
+    这是两个不同的功能，请勿混淆：
+
+    - **Webhook 集成**（[告警 Webhook](/zh/on-call/integration/webhooks/alert-webhook)、[故障 Webhook](/zh/on-call/integration/webhooks/incident-webhook)）：当告警或故障发生变化时，Flashduty 向您配置的 URL 推送事件数据，用于与外部系统（如工单系统、自动化平台）集成
+    - **群机器人 Webhook**（本页「通知方式 → 群聊」）：在分派策略中配置 IM 群机器人的 Webhook 地址，Flashduty 通过该地址向群聊推送故障通知消息
+
+    简言之：Webhook 集成是**数据出站**，群机器人是**通知触达**。
+  </Accordion>
 </AccordionGroup>
 
 ## 延伸阅读