docs: add custom webhook bot guidance for non-standard IM platforms

Users without standard IM platforms (Feishu/Dingtalk/WeCom/Telegram) can
select any bot type and provide their own server URL — Flashduty does not
validate webhook domains. Added tip to notifications docs and FAQ entry
in both zh and en.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: ysyneu

en/on-call/configuration/notifications.mdx

@@ -248,6 +248,10 @@ If your team cannot do app integration temporarily, using bots is a simple, quic
   </Tab>
 </Tabs>
 
+<Tip>
+**Don't use any of the above IM platforms? You can still use bot notifications.** Flashduty does not validate the domain of bot webhook URLs, so you can select any bot type (e.g., Dingtalk Bot) and set the webhook URL to your own server endpoint. Simply implement the corresponding IM platform's message push protocol on your server to receive Flashduty alert notifications. This approach is ideal for custom notification systems or integrating with non-standard IM tools. For step-by-step instructions, see the [FAQ](/en/on-call/quickstart/faq#i-dont-use-feishudingtalkwecomtelegram--how-can-i-receive-bot-notifications).
+</Tip>
+
 ---
 
 ## General Configuration

en/on-call/quickstart/faq.mdx

@@ -300,6 +300,16 @@ description: "Learn about the most common questions when using Flashduty On-call
 
   If you still can't find the cause, please contact us.
   </Accordion>
+
+  <Accordion title="I don't use Feishu/Dingtalk/WeCom/Telegram — how can I receive bot notifications?">
+    If you don't use any of the above IM platforms, you can still leverage bot notifications. Flashduty does not validate the domain of bot webhook URLs. You can:
+
+    1. Select any bot type (e.g., Dingtalk Bot) in the escalation rules
+    2. Set the webhook URL to your own server endpoint
+    3. Implement the corresponding IM platform's message push protocol on your server (i.e., parse the request body according to that platform's message format)
+
+    Flashduty will send alert notifications to your server using that IM platform's message format. You can then process and forward them to any notification channel of your choice.
+  </Accordion>
 </AccordionGroup>
 
 ## Features and Integrations

zh/on-call/configuration/notifications.mdx

@@ -249,6 +249,10 @@ Flashduty App 是 On-call 工程师最高效的移动办公工具。无论您身
   </Tab>
 </Tabs>
 
+<Tip>
+**没有上述 IM 平台？您仍然可以使用机器人通知。** Flashduty 不会校验机器人 Webhook 地址的域名，因此您可以选择任意一种机器人类型（如钉钉机器人），将 Webhook 地址填写为您自己的服务端 URL。只需在您的服务端实现对应 IM 平台的消息推送协议，即可接收 Flashduty 的告警通知。这种方式适合自研通知系统或需要对接非标准 IM 工具的场景。详细步骤请参考[常见问题](/zh/on-call/quickstart/faq#我没有飞书钉钉企微telegram如何接收机器人通知)。
+</Tip>
+
 ---
 
 ## 通用配置

zh/on-call/quickstart/faq.mdx

@@ -301,6 +301,16 @@ keywords: ["常见问题", "FAQ", "On-call", "故障排查", "使用帮助"]
 
   如果您仍然没有找到原因，请联系我们。
   </Accordion>
+
+  <Accordion title="我没有飞书/钉钉/企微/Telegram，如何接收机器人通知？">
+    如果您不使用上述任何 IM 平台，仍然可以利用机器人通知能力。Flashduty 不会校验机器人 Webhook 地址的域名，您可以：
+
+    1. 在分派策略中选择任意一种机器人类型（如钉钉机器人）
+    2. 将 Webhook 地址填写为您自己开发的服务端 URL
+    3. 在您的服务端实现对应 IM 平台的消息推送协议（即按照该平台的消息格式解析请求体）
+
+    这样，Flashduty 会将告警通知以该 IM 平台的消息格式推送到您的服务端，您可以自行处理后转发到任意通知渠道。
+  </Accordion>
 </AccordionGroup>
 
 ## 功能与集成