flashcatcloud · ysyneu · Mar 26, 2026 · Mar 26, 2026
diff --git a/en/on-call/advanced/war-room.mdx b/en/on-call/advanced/war-room.mdx
@@ -3,6 +3,8 @@ title: "War Room"
 description: "War Room is an automated collaboration feature designed for incident emergency response, capable of creating and managing dedicated communication groups on mainstream instant messaging platforms."
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Flashduty On-call War Room is an automated collaboration feature designed for incident emergency response. It creates and manages dedicated communication groups on mainstream instant messaging (IM) platforms throughout the entire incident lifecycle, ensuring teams can respond and collaborate efficiently.
 
 ## Key Features

diff --git a/en/on-call/analytics/insights.mdx b/en/on-call/analytics/insights.mdx
@@ -3,6 +3,8 @@ title: "Insights"
 description: "Use insights for data analysis, with statistics and analysis of incident data across multiple dimensions such as channels, teams, and individuals. Supports data download and export to enable data-driven business growth"
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 ## Key Features
 
 <CardGroup cols={2}>

diff --git a/en/on-call/channel/noise-reduction.mdx b/en/on-call/channel/noise-reduction.mdx
@@ -3,6 +3,8 @@ title: "Noise Reduction"
 description: "Reduce alert noise through grouping, silencing, inhibition, and other strategies to improve processing efficiency"
 ---
 
+<Tip>**Plan requirement**: Alert aggregation, storm warning, and inhibit rules require an On-call Standard or higher subscription. Silence rules are available on all plans. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Noise reduction is one of the core capabilities of Flashduty On-call. When an alert storm hits, you might receive hundreds of similar notifications. The noise reduction feature groups these alerts into a single incident, so you only need to handle it once instead of being overwhelmed by repeated notifications.
 
 {/*

diff --git a/en/on-call/configuration/custom-fields.mdx b/en/on-call/configuration/custom-fields.mdx
@@ -3,6 +3,8 @@ title: "Custom Fields"
 description: "Add custom metadata to incidents to record specific business information"
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Custom fields extend incident description information. Flashduty On-call supports integrating most common alert systems, displaying pushed content in Labels. But you may need to record additional information, such as manually marking whether an incident is a false alarm. Custom fields are designed for this purpose.
 
 {/*

diff --git a/en/on-call/configuration/service-calendar.mdx b/en/on-call/configuration/service-calendar.mdx
@@ -4,6 +4,8 @@ description: Service calendars define workdays and rest days, working with escal
 
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 {/*
 ## Video Introduction
 

diff --git a/en/on-call/configuration/templates.mdx b/en/on-call/configuration/templates.mdx
@@ -4,6 +4,8 @@ description: Notification templates control the content format of incident notif
 
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 ## Use Cases
 
 The system uses templates when assigning incidents in the following scenarios:

diff --git a/en/on-call/incident/outlier-incidents.mdx b/en/on-call/incident/outlier-incidents.mdx
@@ -3,6 +3,8 @@ title: "Outlier Incidents"
 description: "Outlier incident detection for quick handling of new incidents"
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 An outlier incident is one that has never occurred in the past period. If an incident is identified as an outlier, responders should be alert. This is critical for On-call engineers because outlier incidents may have unknown impacts, and handling procedures may need to be decided on the spot. Some engineers may only care about outlier incidents—they create standardized processes or SOPs for resolving such incidents.
 
 ## View Outlier Incidents

diff --git a/en/on-call/integration/alert-integration/label-enhancement.mdx b/en/on-call/integration/alert-integration/label-enhancement.mdx
@@ -3,6 +3,9 @@ title: "Label Enhancement"
 description: "Label enhancement automatically generates new labels during alert ingestion to supplement source data. Examples: extract IP from description, map resource ID to readable name, combine multiple fields to generate jump links, query external systems via API for dynamic data"
 keywords: ["label enhancement", "auto labels", "data extraction", "field mapping", "alert labels", "API mapping", "dynamic labels"]
 ---
+
+<Tip>**Plan requirement**: Basic label enhancement requires an On-call Standard or higher subscription. Advanced label enhancement (such as API mapping) requires a Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 {/*
 ## Video Introduction
 <video

diff --git a/en/on-call/integration/change-integration/custom-event.mdx b/en/on-call/integration/change-integration/custom-event.mdx
@@ -3,6 +3,8 @@ title: "Custom Change Events"
 description: "Push change events from your own systems to Flashduty On-call via standard protocol. Most incidents are caused by changes, and linking changes with alert events helps quickly identify incident root causes"
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 <Tip>
 Flashduty On-call has adapted webhook protocols for some common ticketing and deployment systems. For these systems, you should first use the corresponding integrations. This integration provides a standard HTTP interface that requires your development adaptation, with the benefit of integrating with any deployment system.
 </Tip>

diff --git a/en/on-call/integration/instant-messaging/dingtalk.mdx b/en/on-call/integration/instant-messaging/dingtalk.mdx
@@ -3,6 +3,8 @@ title: "Dingtalk"
 description: "By integrating a Dingtalk custom app, you can receive and respond to alerts within Dingtalk"
 ---
 
+<Tip>**Plan requirement**: IM integration requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 <Note>
 This documentation uses the new version of Dingtalk Open Platform as an example.
 </Note>

diff --git a/en/on-call/integration/instant-messaging/lark.mdx b/en/on-call/integration/instant-messaging/lark.mdx
@@ -3,6 +3,8 @@ title: "Feishu/Lark"
 description: "By integrating a Feishu/Lark custom app, you can receive and respond to alerts within Feishu/Lark"
 ---
 
+<Tip>**Plan requirement**: IM integration requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 <div className="hide">
 {/*
 ## Video Introduction

diff --git a/en/on-call/integration/instant-messaging/microsoft-teams.mdx b/en/on-call/integration/instant-messaging/microsoft-teams.mdx
@@ -3,6 +3,8 @@ title: "Microsoft Teams"
 description: "By integrating the Microsoft Teams third-party app, you can receive and respond to alerts within Microsoft Teams"
 ---
 
+<Tip>**Plan requirement**: IM integration requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 <Warning>
 Microsoft Teams integration is currently in Beta stage. The following steps must be completed by a Microsoft Teams administrator.
 </Warning>

diff --git a/en/on-call/integration/instant-messaging/slack.mdx b/en/on-call/integration/instant-messaging/slack.mdx
@@ -3,6 +3,8 @@ title: "Slack"
 description: "By integrating the Slack third-party app, you can receive and respond to alerts within Slack"
 ---
 
+<Tip>**Plan requirement**: IM integration requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 <span id="install-app"></span>
 
 ## 1. Install App

diff --git a/en/on-call/integration/instant-messaging/wecom.mdx b/en/on-call/integration/instant-messaging/wecom.mdx
@@ -3,6 +3,8 @@ title: "WeCom"
 description: "By integrating a WeCom third-party app, you can receive and respond to alerts within WeCom"
 ---
 
+<Tip>**Plan requirement**: IM integration requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 This documentation supports [Third-Party App Integration](#third-party) or [Custom App Integration](#self) methods.
 
 <div className="hide">

diff --git a/en/on-call/integration/webhooks/alert-webhook.mdx b/en/on-call/integration/webhooks/alert-webhook.mdx
@@ -1,3 +1,5 @@
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Configure alert Webhook. When specific operations occur on alerts (such as trigger or close), the system makes an HTTP callback to your configured address. The callback content includes the alert's latest key information, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>

diff --git a/en/on-call/integration/webhooks/custom-actions.mdx b/en/on-call/integration/webhooks/custom-actions.mdx
@@ -1,3 +1,5 @@
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Configure incident custom actions, allowing you to quickly call external interfaces during incident troubleshooting to achieve self-healing, information enrichment, or any custom operations.
 
 ## 1. Create Action

diff --git a/en/on-call/integration/webhooks/incident-webhook.mdx b/en/on-call/integration/webhooks/incident-webhook.mdx
@@ -1,3 +1,5 @@
+<Tip>**Plan requirement**: This feature requires an On-call Standard or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Configure incident Webhook. When specific operations occur on incidents (such as trigger or close), the system makes an HTTP callback to your configured address. The callback content includes the incident's latest key information, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>

diff --git a/en/on-call/integration/webhooks/jira-sync.mdx b/en/on-call/integration/webhooks/jira-sync.mdx
@@ -3,6 +3,8 @@ title: "Jira Sync"
 description: "Associate incidents with Jira Issues through Jira Sync Webhook."
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Through Jira Sync Webhook, synchronize Flashduty incidents with Jira Issues for linkage between Flashduty and Jira.
 
 ## Prerequisites

diff --git a/en/on-call/integration/webhooks/servicenow-sync.mdx b/en/on-call/integration/webhooks/servicenow-sync.mdx
@@ -3,6 +3,8 @@ title: "ServiceNow Sync"
 description: "Associate incidents with ServiceNow Incidents through ServiceNow Sync Webhook."
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Through ServiceNow Sync Webhook, synchronize Flashduty incidents with ServiceNow Incidents for linkage between Flashduty and ServiceNow.
 
 ## In ServiceNow

diff --git a/en/on-call/post-mortem/ai-generate-post-mortem.mdx b/en/on-call/post-mortem/ai-generate-post-mortem.mdx
@@ -10,9 +10,7 @@ The hardest part of writing a post-mortem is often getting started — staring a
 
 Flashduty's AI-assisted generation can help you get past that. It analyzes all the context around the linked incident and, following the template's section structure, produces a complete first draft. All you need to do is adjust the wording, fill in details, and add your team's conclusions.
 
-<Note>
-The post-mortem feature is available on the Professional plan only.
-</Note>
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
 
 ## How to Use
 

diff --git a/en/on-call/post-mortem/create-edit-post-mortem.mdx b/en/on-call/post-mortem/create-edit-post-mortem.mdx
@@ -4,6 +4,8 @@ description: "Learn how to create a post-mortem report from an incident, collabo
 keywords: ["create post-mortem", "edit post-mortem", "collaborative editing", "publish post-mortem", "delete post-mortem", "image upload"]
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 ## Create a Post-Mortem Report
 
 Once an incident has been closed, you can begin the post-mortem process.

diff --git a/en/on-call/post-mortem/manage-templates.mdx b/en/on-call/post-mortem/manage-templates.mdx
@@ -8,9 +8,7 @@ keywords: ["post-mortem template", "template management", "custom template", "bu
 
 Having to think from scratch about "what should we cover" every time you write a post-mortem is both time-consuming and error-prone. Templates solve this by defining sections and guidelines upfront, so every report follows a consistent structure — and giving AI a clear framework to generate content from.
 
-<Note>
-The post-mortem feature is available on the Professional plan only.
-</Note>
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
 
 ## Built-In Templates
 

diff --git a/en/on-call/post-mortem/what-is-post-mortem.mdx b/en/on-call/post-mortem/what-is-post-mortem.mdx
@@ -12,9 +12,7 @@ If you don't take the time to review and reflect, the same issues are likely to
 
 Flashduty integrates post-mortems directly into your incident management workflow — create a report from the incident detail page with one click, let AI draft the initial content, collaborate with your team to refine it, and produce an archivable, traceable post-mortem report.
 
-<Note>
-The post-mortem feature is available on the Professional plan only.
-</Note>
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
 
 ## What Does a Post-Mortem Report Look Like
 

diff --git a/en/on-call/statuspage/statuspage.mdx b/en/on-call/statuspage/statuspage.mdx
@@ -3,6 +3,8 @@ title: "Status Page"
 description: "Achieve efficient internal and external communication during incidents through a unified service status dashboard"
 ---
 
+<Tip>**Plan requirement**: This feature requires an On-call Pro or higher subscription. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Service interruptions are inevitable, but communication efficiency can be systematically improved.
 
 When service status fluctuates, relying on manual emails or instant messages for notifications can no longer meet enterprise requirements for information timeliness and consistency. Flashduty Status Page provides a standardized, unified information publishing window to ensure that both internal and external stakeholders maintain real-time awareness of service status.

diff --git a/en/platform/pricing.mdx b/en/platform/pricing.mdx
@@ -1,6 +1,7 @@
 ---
 title: "Pricing"
 description: "Learn about the pricing models and plans for Flashduty products"
+keywords: ["pricing", "license subscription", "pay-as-you-go", "pricing model", "plan comparison"]
 ---
 
 ## On-call Pricing
@@ -23,6 +24,47 @@ Each License corresponds to one account member. Only members with a License can
 
 For detailed feature comparison, visit: [Pricing Page](https://flashcat.cloud/flashduty/price/)
 
+### Resource Limits
+
+| Resource | Free | Standard | Pro |
+| --- | --- | --- | --- |
+| Maximum users | 5 | Unlimited | Unlimited |
+| Maximum schedules | 1 | Unlimited | Unlimited |
+| Maximum channels | 1 | Unlimited | Unlimited |
+| Daily alert limit | 100 | Unlimited | Unlimited |
+| Data retention | 30 days | 180 days | 360 days |
+| Audit logs | Not available | 10 days | 30 days |
+
+<Warning>
+The Free plan accepts a maximum of 100 alerts per day. Alerts exceeding this limit are **silently dropped** with no error returned. Upgrade to Standard or Pro for unlimited alerts.
+</Warning>
+
+### Notification Quota
+
+Each plan includes free notification quotas, calculated **per user per month**. Total quota = per-user allowance × number of Licenses.
+
+| Channel | Free | Standard | Pro |
+| --- | --- | --- | --- |
+| Free SMS | 10/user/month | 500/user/month | 1,000/user/month |
+| Additional SMS | Notifications stop | ¥0.05/message | ¥0.05/message |
+| Free voice calls | 10 min/user/month | 50 min/user/month | 100 min/user/month |
+| Additional voice calls | Notifications stop | ¥0.12/minute | ¥0.12/minute |
+| Free emails | 100/user/month | 2,000/user/month | 5,000/user/month |
+| Additional emails | Notifications stop | ¥0.0018/email | ¥0.0018/email |
+| Webhook | Unlimited | Unlimited | Unlimited |
+
+<Warning>
+On the Free plan, notifications **stop** once the quota is exhausted. On Standard and Pro plans, additional usage is billed on demand; notifications also stop if the account balance is insufficient.
+</Warning>
+
+### Customer Support
+
+| Plan | Support Channel | Service Hours |
+| --- | --- | --- |
+| Free | None | — |
+| Standard | Email / Ticket | 5×8 hours |
+| Pro | Dedicated support group | 7×8 hours |
+
 ### License Types
 
 <Tabs>
@@ -88,6 +130,13 @@ RUM uses a **pay-as-you-go** model, billed by the number of sessions used.
 | **Advanced Dashboards** | ❌ | ✅ |
 | **Frontend-Backend Correlation** (Tracing) | ❌ | ✅ |
 
+### Data Retention
+
+| Data Type | Free | Pro |
+| --- | --- | --- |
+| Sessions / Views / Errors / Actions | 30 days | 30 days |
+| Resources / Long Tasks | 15 days | 15 days |
+
 <Tip>
 The Free plan is suitable for evaluating product features. The Pro plan is billed based on actual usage with no large upfront costs.
 </Tip>
@@ -121,13 +170,20 @@ The Free plan is suitable for evaluating product features. The Pro plan is bille
   </Accordion>
 
   <Accordion title="Is private deployment supported?">
-    Yes. Flashduty offers a private deployment version that is nearly identical to the SaaS service.
-
+    Yes. Flashduty offers an **On-Premises** edition with all Pro features, plus:
+    - Local data storage
+    - Internal system integration
+    - No public network dependency
+
     <Warning>
     Private deployment has higher maintenance costs and a different pricing model than SaaS. Unless you have specific requirements, we recommend using the cloud service.
     </Warning>
-
-    Please contact us if you need the private deployment version.
+
+    Please contact us for On-Premises pricing.
+  </Accordion>
+
+  <Accordion title="Is a free trial available?">
+    Yes. The On-call Pro plan offers a free trial with full access to all Pro features. Contact our sales team to request a trial.
   </Accordion>
 </AccordionGroup>
 

diff --git a/en/platform/team-members.mdx b/en/platform/team-members.mdx
@@ -96,7 +96,7 @@ In the member list, a warning icon appears next to unverified email addresses or
 
 <Note>
   - The system will send SMS or email notifications to invitees
-  - Daily invitation limit is 200 people, with a maximum of 20 people per invitation, and up to 5 invitation resends per day
+  - Daily invitation limit is 200 people, with a maximum of 20 per invitation and up to 5 resends per day
   - Unactivated accounts cannot receive alert-related notifications
 </Note>
 

diff --git a/zh/on-call/advanced/war-room.mdx b/zh/on-call/advanced/war-room.mdx
@@ -4,6 +4,8 @@ description: "作战室 (War Room) 是专为故障应急响应设计的自动化
 keywords: ["作战室", "War Room", "应急响应", "协同沟通", "群组管理"]
 ---
 
+<Tip>**版本要求**：此功能需要 On-call 专业版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 Flashduty On-call 作战室（War Room）是专为故障应急响应设计的自动化协同功能。它能够围绕故障的整个生命周期，在主流的即时通讯（IM）平台中创建并管理专属沟通群组，确保团队能够高效响应与协作。
 
 ## 关键特性

diff --git a/zh/on-call/analytics/insights.mdx b/zh/on-call/analytics/insights.mdx
@@ -4,6 +4,8 @@ description: "通过分析看板进行数据分析，可以基于协作空间、
 keywords: ["分析看板", "数据分析", "故障统计", "报表导出", "运维指标"]
 ---
 
+<Tip>**版本要求**：此功能需要 On-call 标准版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 ## 关键特性
 
 <CardGroup cols={2}>

diff --git a/zh/on-call/channel/noise-reduction.mdx b/zh/on-call/channel/noise-reduction.mdx
@@ -4,6 +4,8 @@ description: "通过聚合、静默、抑制等策略减少告警噪音，提升
 keywords: ["告警降噪", "告警聚合", "静默策略", "抑制策略", "噪音减少"]
 ---
 
+<Tip>**版本要求**：告警聚合、风暴预警和抑制策略功能需要 On-call 标准版及以上订阅，静默策略在所有版本中可用。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 告警降噪是 Flashduty On-call 的核心能力之一，当告警风暴来袭时，您可能会收到数百条相似通知。降噪功能将这些告警聚合为一条故障，让您只需处理一次，而非被重复通知淹没。
 
 {/*

diff --git a/zh/on-call/configuration/custom-fields.mdx b/zh/on-call/configuration/custom-fields.mdx
@@ -4,6 +4,8 @@ description: "为故障添加自定义元数据，记录特定业务信息"
 keywords: ["自定义字段", "元数据", "故障属性", "业务信息", "字段配置"]
 ---
 
+<Tip>**版本要求**：此功能需要 On-call 标准版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 自定义字段用于扩展故障的描述信息。Flashduty On-call 已支持接入大部分常见告警系统，将推送内容放到 Labels 展示。但您可能还需要记录额外信息，比如人工标记故障是否为误报。自定义字段正是为此设计。
 
 {/*

diff --git a/zh/on-call/configuration/service-calendar.mdx b/zh/on-call/configuration/service-calendar.mdx
@@ -5,6 +5,8 @@ keywords: ["服务日历", "工作日", "休息日", "节假日", "差异化处
 
 ---
 
+<Tip>**版本要求**：此功能需要 On-call 专业版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 {/*
 ## 视频介绍
 

diff --git a/zh/on-call/configuration/templates.mdx b/zh/on-call/configuration/templates.mdx
@@ -5,6 +5,8 @@ keywords: ["通知模板", "模板配置", "消息格式", "模板变量", "通
 
 ---
 
+<Tip>**版本要求**：此功能需要 On-call 专业版及以上订阅。[了解更多](https://flashcat.cloud/flashduty/price/)</Tip>
+
 ## 使用场景
 
 系统在以下场景分派故障时会使用模板：
-Original file line number
+Diff line change
@@ Expand Up / @@ -3,6 +3,8 @@ title: "Noise Reduction" @@
     description: "Reduce alert noise through grouping, silencing, inhibition, and other strategies to improve processing efficiency"
     ---
+    <Tip>**Plan requirement**: Alert aggregation, storm warning, and inhibit rules require an On-call Standard or higher subscription. Silence rules are available on all plans. [Learn more](https://flashcat.cloud/flashduty/price/)</Tip>
     Noise reduction is one of the core capabilities of Flashduty On-call. When an alert storm hits, you might receive hundreds of similar notifications. The noise reduction feature groups these alerts into a single incident, so you only need to handle it once instead of being overwhelmed by repeated notifications.
     {/*
@@ Expand Down @@