docs: add Zoom webhook troubleshooting FAQ and service account warning

Zoom incoming webhook connections are tied to the creator's account. When
that user leaves the org, all their webhooks silently break with a vague
HTTP 400 "Failed to send bot message" error. Add a Warning block in
prerequisites recommending shared service accounts, and a new FAQ entry
explaining the failure and how to recover.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ysyneu

en/on-call/integration/instant-messaging/zoom.mdx

@@ -13,6 +13,10 @@ Before configuring, you need to create a Chatbot application in the [Zoom Market
 1. **Webhook URL or Token**: The Webhook URL or Token of the Zoom Chatbot.
 2. **Verify Token**: The Verify Token used to authenticate request origins.
 
+<Warning>
+Zoom Incoming Webhook connections are tied to the Zoom account that created them. When that user leaves the organization or their account is deactivated, all Webhook connections they created are automatically invalidated. **We strongly recommend using a shared team service account** (rather than a personal account) to create Webhook connections, preventing notification disruptions due to personnel changes.
+</Warning>
+
 ## Configuration steps
 
 Add a Zoom bot notification channel in a channel's escalation rule:
@@ -81,4 +85,12 @@ You can find the Verify Token on your Chatbot application's configuration page i
 <Accordion title="How do I create a user mapping table?">
 Go to Platform Management → Mapping Table Management to create a Zoom-type user mapping table. You can also click the **Quick Create Mapping Table** link when configuring the Zoom bot to navigate directly to the creation page.
 </Accordion>
+
+<Accordion title="Notification fails with 'Failed to send bot message'?">
+This error typically indicates the Webhook connection has become invalid. Zoom Incoming Webhook connections are tied to the Zoom account of the user who created them. When that user leaves the organization or their account is deactivated/deleted, all Webhook connections they created are automatically invalidated, causing notifications to return HTTP 400 errors.
+
+**Solution:**
+- Have a current active Zoom user create a new Incoming Webhook connection, then update the Webhook URL and Token in Flashduty
+- We recommend using a shared service account (rather than a personal account) to create Webhook connections to prevent notification disruptions due to personnel changes
+</Accordion>
 </AccordionGroup>

zh/on-call/integration/instant-messaging/zoom.mdx

@@ -13,6 +13,10 @@ Zoom 机器人是一种群聊通知渠道，您可以在协作空间的分派策
 1. **Webhook 地址或 Token**：Zoom Chatbot 的 Webhook URL 或 Token。
 2. **Verify Token**：用于验证请求来源的 Verify Token。
 
+<Warning>
+Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定。当创建者离职或账号被停用时，其创建的所有 Webhook 连接将自动失效。**强烈建议使用团队共享的服务账号**（而非个人账号）来创建 Webhook 连接，避免因人员变动导致通知中断。
+</Warning>
+
 ## 配置步骤
 
 在协作空间的分派策略中添加 Zoom 机器人通知渠道：
@@ -81,4 +85,12 @@ Zoom 机器人是一种群聊通知渠道，您可以在协作空间的分派策
 <Accordion title="如何创建用户信息映射表？">
 前往 平台管理 → 映射表管理，创建 Zoom 类型的用户信息映射表。您也可以在配置 Zoom 机器人时，点击 **快速创建映射表** 链接直接跳转创建。
 </Accordion>
+
+<Accordion title="通知发送失败，提示 Failed to send bot message？">
+该错误通常表示 Webhook 连接已失效。Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定，当创建者离职或账号被停用/删除时，其创建的所有 Webhook 连接将自动失效，导致通知发送返回 HTTP 400 错误。
+
+**解决方法：**
+- 由当前在职的 Zoom 用户重新创建 Incoming Webhook 连接，并更新 Flashduty 中配置的 Webhook 地址和 Token
+- 建议使用共享服务账号（而非个人账号）创建 Webhook 连接，避免因人员变动导致通知中断
+</Accordion>
 </AccordionGroup>