docs: improve Zoom webhook troubleshooting with diagnostic steps

Reframe the FAQ to not assume resignation as the only cause. Add a
step-by-step troubleshooting flow: create a new webhook, test it, then
confirm whether the old one is invalid before concluding root cause.

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

Author: ysyneu

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

@@ -14,7 +14,7 @@ Before configuring, you need to create a Chatbot application in the [Zoom Market
 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.
+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, and Zoom's error response will not indicate the actual cause. **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
@@ -87,10 +87,15 @@ Go to Platform Management → Mapping Table Management to create a Zoom-type use
 </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.
+This error means Zoom cannot send messages through the Webhook. Possible causes include: the Webhook connection has been invalidated, the creator's account was deactivated or removed, or the Webhook was manually deleted. Zoom's error response (HTTP 400 `Failed to send bot message`) does not indicate the specific cause.
 
-**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
+**Troubleshooting steps:**
+1. Create a new Incoming Webhook connection in Zoom
+2. Test the new Webhook URL in your Flashduty escalation rule
+3. If the new Webhook works, the original connection has been invalidated (commonly caused by the creator leaving the organization and their account being deactivated) — replace it with the new Webhook
+4. If the new Webhook also fails, check the message content format or contact Zoom support
+
+**Prevention:**
+- Use a shared team service account (rather than a personal account) to create Webhook connections, preventing notification disruptions due to personnel changes
 </Accordion>
 </AccordionGroup>

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

@@ -14,7 +14,7 @@ Zoom 机器人是一种群聊通知渠道，您可以在协作空间的分派策
 2. **Verify Token**：用于验证请求来源的 Verify Token。
 
 <Warning>
-Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定。当创建者离职或账号被停用时，其创建的所有 Webhook 连接将自动失效。**强烈建议使用团队共享的服务账号**（而非个人账号）来创建 Webhook 连接，避免因人员变动导致通知中断。
+Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定。当创建者离职或账号被停用时，其创建的所有 Webhook 连接将自动失效，且 Zoom 返回的错误信息不会明确指出原因。**强烈建议使用团队共享的服务账号**（而非个人账号）来创建 Webhook 连接，避免因人员变动导致通知中断。
 </Warning>
 
 ## 配置步骤
@@ -87,10 +87,15 @@ Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定。当创建者
 </Accordion>
 
 <Accordion title="通知发送失败，提示 Failed to send bot message？">
-该错误通常表示 Webhook 连接已失效。Zoom Incoming Webhook 的连接与创建者的 Zoom 账号绑定，当创建者离职或账号被停用/删除时，其创建的所有 Webhook 连接将自动失效，导致通知发送返回 HTTP 400 错误。
+该错误表示 Zoom 无法通过该 Webhook 发送消息，可能的原因包括：Webhook 连接已失效、创建者账号被停用或离职、Webhook 被手动删除等。Zoom 返回的错误信息（HTTP 400 `Failed to send bot message`）不会明确指出具体原因。
 
-**解决方法：**
-- 由当前在职的 Zoom 用户重新创建 Incoming Webhook 连接，并更新 Flashduty 中配置的 Webhook 地址和 Token
-- 建议使用共享服务账号（而非个人账号）创建 Webhook 连接，避免因人员变动导致通知中断
+**排查方法：**
+1. 在 Zoom 中创建一个新的 Incoming Webhook 连接
+2. 在 Flashduty 分派策略中使用新的 Webhook 地址进行测试
+3. 如果新 Webhook 发送正常，说明原 Webhook 连接已失效（常见原因是创建者离职导致账号被停用），使用新的 Webhook 替换即可
+4. 如果新 Webhook 同样失败，请检查消息内容格式或联系 Zoom 支持
+
+**预防建议：**
+- 使用团队共享的服务账号（而非个人账号）创建 Webhook 连接，避免因人员变动导致通知中断
 </Accordion>
 </AccordionGroup>