Skip to main content
  • Post-Mortem is Here: Turn Every Incident into a Starting Point for Team Growth

    New

    Restoring service doesn't mean the incident is truly over. The real closure begins with a post-mortem.

    In practice, many teams quickly return to business as usual once an incident is resolved: root cause analysis is scattered across chat messages, follow-up actions remain verbal agreements, and similar issues quietly resurface down the road. The previous Resolution feature only supported basic field-level recording, falling short of a complete, structured post-incident analysis workflow.

    To address this, Flashduty officially introduces Post-Mortem, fully replacing the former Resolution. From incident review and root cause analysis to corrective action tracking, Post-Mortem helps teams build a more complete retrospective process, turning every incident into reusable organizational knowledge, rather than a forgotten cost.

    If you previously relied on custom data fields in Resolution, you can continue to achieve the same through Custom Fields.

    AI-Assisted Generation: Quickly Produce a Post-Mortem Draft

    Post-Mortem supports AI-generated report drafts. The system synthesizes incident details, response timelines, and discussion threads from Lark or Slack war rooms to automatically outline the sequence of events and extract key insights. This significantly reduces the effort needed to get started, allowing teams to focus on analysis and improvement.

    Real-Time Collaborative Editing: Reach Consensus More Efficiently

    An incident is never one person's responsibility, and neither should the post-mortem be. Multiple team members can co-edit the same report simultaneously, with changes synced in real time and auto-saved. No more passing documents back and forth or manually merging versions -- the entire team can align on facts, fill in details, and build consensus on a single page.

    Template System: Never Miss What Matters

    What happened? Why did it happen? How do we prevent it from happening again?

    Post-Mortem provides built-in templates covering six core sections: Summary, Root Cause, Impact, Timeline, Corrective Actions, and Lessons Learned. You can also create custom templates to codify your team's best practices into a standard workflow, ensuring every post-mortem is thorough, consistent, and high-quality.

    Incidents are inevitable, but the same issue happening twice doesn't have to be. With Flashduty Post-Mortem, teams can document root causes more clearly, track improvements more consistently, and accumulate lessons more systematically. This is more than a report. It's where organizational resilience begins to grow.

    Get Started

    Head to Flashduty Console -> On-call -> Post Incident to start using it.

    For more details, refer to the Flashduty documentation.

    This feature is available on the Flashduty Professional plan.

  • Flashduty Status Pages: Sevice Down, Trust Online

    New

    Service interruptions are inevitable. Trust should not go offline with them.

    In time-critical incident response, a lack of transparency often causes more damage than the incident itself. Repeated status inquiries from stakeholders consume team attention, while unclear service visibility quietly undermines customer confidence.

    The Flashduty Status Pages is designed to address this problem directly. By providing a single, transparent view of service availability, it removes unnecessary communication overhead for technical teams. Real-time updates replace guesswork, so even when a service is temporarily unavailable, professionalism and reliability remain visible.

    Reduce Repetitive Tickets at the Source

    Instead of reacting to questions, let information move first.

    The Flashduty Status Pages allows users to check service status at any time and subscribe to updates for the services they care about. When an incident occurs, the latest progress is automatically delivered to subscribers—no manual refresh or confirmation required. When information arrives before questions, repetitive inquiries naturally decline, allowing support teams to focus on resolving the issue itself.

    Make Maintenance Transparent and Controlled

    The Flashduty Status Pages is not limited to unexpected incidents. Planned maintenance is also clearly communicated.

    By publishing maintenance windows in advance, users can understand when changes will occur and which services may be affected. Upgrades become predictable, changes are explained, and maintenance is no longer mistaken for an outage. Clear maintenance communication ensures that every service adjustment reflects reliability and professionalism.

    Prove Stability with Data

    Stability is not a statement: it is a record. The Flashduty Status Pages automatically retains historical availability data, turning abstract SLA commitments into clear, verifiable uptime records. These objective data points provide direct evidence of service reliability and form a solid basis for demonstrating operational performance and earning long-term trust.

    With the Flashduty Status Pages, service status is no longer a black box running in the background. Whether it is an incident or scheduled maintenance, every update is visible and every historical event is traceable. Technical teams can return their focus to solving problems, while users stay informed with timely and accurate updates. This clarity, built in moments of uncertainty, is the strongest foundation for lasting customer trust.

    Try It Out

    Visit Flashduty Console → On-call → Status Pages to explore the feature.

    Visit Flashduty Docs for more information.

    You can also subscribe to the official Flashduty Status Pages to receive timely updates on Flashduty service status.

  • Routing Rules Update

    Improvement

    This release introduces significant enhancements to Alert Routing, focusing on better automation, improved readability, and a smoother configuration experience for complex routing scenarios.

    image.png

    1. Name Mapping–based Auto Routing

    Added support for Name Mapping, allowing alerts to be automatically routed to a channel whose name matches a label value.

    This eliminates the need to manually maintain explicit routing targets for each service or application, making it ideal for multi-service and multi-team environments.

    Example:

    • labels.application_name = "order-service"
    • The alert is automatically routed to the order-service channel

    2. Channel Filtering and Sorting

    When working with many routing rules, you can now filter and sort rules by channel, making it easier to locate, understand, and manage routing configurations.


    3. Routing Rules UI Improvements

    • Drag-and-drop support for reordering routing rules
    • Clearer presentation of rule conditions and actions
    • Cleaner layout for faster configuration and troubleshooting
  • Introducing War Room, Enhanced Change Management & Streamlined Incident Collaboration

    New

    War Room

    When critical incidents strike, every second counts. Now you can spin up a War Room with a single click to rally your team and accelerate incident response.

    Key Capabilities:

    • Instant Group Chat: Create a Lark, DingTalk, WeCom, or Slack channel in one click, automatically inviting responders and stakeholders
    • Live Updates: Incident cards are posted and pinned in the channel, updating in real-time as the situation evolves
    War Room Demo

    Webhook Call History

    No more guesswork when troubleshooting webhook issues. We now provide full visibility into webhook call history to help you pinpoint problems quickly.

    What's Logged:

    • Response status and error codes
    • Retry attempts
    • Complete request and response payloads
    Webhook Call History Demo

    Change Events

    Most incidents are caused by changes. We've significantly upgraded our change event management to help you correlate incidents with changes more effectively.

    What's New:

    • Dynamic Routing: Route change events to relevant collaboration spaces based on your business context
    • Label Enrichment: Enrich incoming events with additional metadata through post-processing
    • Redesigned UI: The change history page now supports custom views and label-based filtering for incident correlation
    Change Events Page

    Improvement

    1. Incident List: Bulk assign incidents to improve handling efficiency
    2. Novel Incidents: Option to disable novel incident detection
    3. Alert Storm: Configure multiple storm thresholds for tiered alerting
    4. Dispatch Policy: Specify severity levels for group chat channel configurations
    5. Incident Details: Custom label sorting and JSON view for incident labels
    6. Integration Hub: Added Zoho ServiceDesk Plus and Cloudflare integrations
  • AI Summary and ServiceNow

    New

    AI Summary

    Added AI Summary feature to quickly distill incident details, ideal for scenarios with numerous aggregated alerts. The summary focuses on:

    1. Incident Overview (key details)
    2. Impact Scope (resources, services, etc.)
    3. Actionable Steps (troubleshooting, mitigation, prevention)
    AI Summary

    ServiceNow Integration

    Introduced ServiceNow integration with bidirectional incident data synchronization:

    1. Supports manual and automatic sync triggers
    2. Enables two-way synchronization between Flashduty and ServiceNow for shared insights
    ServiceNow Integration

    Improvement

    Mobile App

    The new Flashduty mobile app is now available on app stores with a revamped UI and enhanced functionality:

    1. Added support for English language
    2. Integrated AI Summary feature
    3. Enhanced incident details with custom fields, improved tag display, and optimized text editing
    Mobile App

    Analytics Dashboard

    The analytics dashboard now supports filtering incidents by tags and custom fields, enabling more precise data analysis.

    Analytics Dashboard

    Microsoft Teams

    The Teams app now supports sending incident assignment notifications to channels or group chats, with interactive features, dynamic updates, and cross-platform synchronization.

    Microsoft Teams

    WeChat/Zoom/Lark Bots

    1. Added support for uploading email-to-account ID mappings for platforms like Lark
    2. Enhanced escalation rules to leverage mappings for targeted @mentions in group chat notifications
    Bot Enhancements
  • Changes in June

    New

    1. Link Integration
      Enables seamless connection with external systems, allowing direct navigation to CMDB host information pages based on machine hostname, boosting operational efficiency.

      Link Integration Demo
    2. DingTalk and Feishu Alert Integration
      Supports receiving alerts via DingTalk and Feishu Webhooks, streamlining team communication.

      DingTalk and Feishu Alerts

    Improvement

    1. Incident Merge Interaction Optimization
      Supports fuzzy matching and deletion of merged incidents, improving flexibility and accuracy in incident management.

      Incident Merge Optimization
    2. Alert Intelligent Grouping with Custom Fields
      Allows similarity calculations based on specified fields, enhancing the precision and efficiency of alert aggregation.

      Smart Aggregation
    3. Incident Timeout Closure Enhancement
      Introduces countdown-based closure triggered by the last merged event time, making incident management smarter.

      Timeout Closure
    4. Shared Integration Permission Management
      Allows setting management teams for shared integrations, restricting configuration changes to team members for enhanced security.

      Shared Integration
    5. Incident Suppression Upgraded to Flapping Detection
      Offers options to either continue notifications or silence them when an incident enters flapping status, providing flexibility for various scenarios.

      Flapping Detection
  • Fixed License and Alert Routing Version Management

    Improvement

    License Management

    1. New Fixed License Type: Valid indefinitely and non-preemptible, ideal for long-term platform users.
    2. Flexible License Assignment: Account administrators can assign fixed or temporary Licenses to members or revoke them.
    3. Member Self-Management: Regular members can voluntarily relinquish their License.
    4. Batch API Operations: Support for batch setting of member License types via API.
    image.png

    Routing Version Management

    1. Historical Version Viewing: The alert routing in the integration center now supports viewing historical versions.
    2. Version Comparison: Compare current routing rules with historical versions.
    3. One-Click Rollback: Roll back to any historical version of routing rules.
    image.png
    image.png
  • New Jira Integration and Template Management!

    New

    Jira Integration

    • Manual or Automatic Sync of Incident Data to Jira Issues: Choose to sync incident details to Jira Issues manually or automatically, ensuring your team can track and resolve issues promptly.
    • Support for Jira Cloud and Server Versions: Seamlessly integrates with both Jira Cloud and Server, accommodating your preferred deployment.
    • Sync Limited Scope of Incidents: Allows selective syncing of incidents within a defined scope, offering greater control over what gets synchronized.
    • Incident Field Mapping Management: Customize the mapping between incident fields and Jira Issue fields for accurate and tailored data transfer.
    image.png

    Coming Soon: We’re working on enabling Jira Issue syncing back to Flashduty incidents. Stay tuned!


    Improvement

    Template Management

    • Revamped Interaction Design: The template management interface has been redesigned for a more visually appealing and user-friendly experience.
    • Preview and Debug with Historical Incidents: Select past incidents to preview and debug templates, ensuring configurations are spot-on.
    • Smart Input Suggestions: Type {{ to trigger automatic input prompts, simplifying configuration and boosting efficiency.
    image.png

    Other Enhancements

    • IM Integration: Added support for private deployments of Feishu and DingTalk, meeting the needs of more enterprises.
    • Incident Webhook: Now supports subscribing to incident comment events for real-time updates.
    • Incident Suppression: Introduced incident suppression functionality, with options to enable or disable (disabled by default), helping you manage notifications more effectively.
  • Flashduty app now available, boosting response efficiency by 40%!

    New

    Dear Flashduty users,

    Today, we officially launch the Flashduty mobile app! No matter where you are, you can control everything just like at your workstation.

    image.png

    Key Feature Highlights

    1. Incident Management at Your Fingertips

    • Full Mobile Workflow: Supports incident retrieval, detailed viewing, claiming, closing, escalating, and manual triggering, with deep optimization for mobile interaction, increasing key operation response speed by 40%.
    • Multi-dimensional Information Aggregation: Incident timeline, handling records, and associated logs are centrally displayed to aid quick decision-making.

    Scenario Value: What you can do at your workstation, you can do just as efficiently on your phone.


    2. Critical Notifications, Never Miss a Beat

    • iOS Critical Alerts: Based on Apple's official Critical Alerts protocol, breaks through Do Not Disturb mode restrictions, ensuring 100% delivery of severe alerts.
    • Android System-level Channels: Supports system-level channels on all major Android manufacturers, allowing alerts to reach you even when the app is closed, preventing any misses.

    Scenario Value: "Sleeping? In a meeting? Severe incidents will still notify you."


    3. Voice Notifications, More Reliable

    • Smart Whitelist Synchronization: Automatically adds Flashduty voice numbers to your phone's contacts, avoiding the risk of operator misinterception.

    Take Action Now

    1️⃣ Download and Install
    👉 Go to the app store or click to download the Flashduty App (iOS/Android)
    2️⃣ Permission Configuration Suggestions

    • iOS users: Go to "Settings - Notifications" and enable Critical Alerts for Flashduty.
    • All users: In the app, go to "Settings - Voice Notifications" and enable Sync Contacts permission.

    Incidents don't wait, but you can always be one step ahead.

    — The Flashduty Team

  • Enhanced Label Mapping: Now Manage Data Directly in the Console!

    New

    Since its launch, the Label Enrichment feature has been well received, especially for mapping labels using mapping data. However, managing mapping schemas and handling data uploads/downloads was previously only possible via the API, which posed a challenge for some users.

    Now, we’ve added a Mapping Data Management feature to the console, allowing you to manage data easily through the UI—no API required!

    image.png

    📖 Learn more in our guide: Label Enrichment.

  • Brand new Insights dashbord!

    The new insights dashboard is now live! Thank you for your patience.

    Improvement

    Enhanced metric dimensions:

    Metric aggregation dimensions have been expanded from global and time-based views to include team, channel, and individual perspectives. This allows you to drill down from the global view into various sub-dimensions for metric analysis.

    image.png

    Time period segmentation:

    For 24/7 on-call coverage, treating each hour equally is not fair. In this new version, we've divided time into three segments, allowing you to analyze metrics across these dimensions:

    • Work hours: Weekdays 8am~7pm
    • Rest hours: Weekdays 7pm11pm, Non-workdays 8am11pm
    • Sleep hours: Daily 11pm~8am
    image.png

    New workload metrics

    When tracking team incident handling workload, looking at incident and alert counts alone is insufficient. We now support interruptions and response effort metrics.

    • Interruptions: High-priority messages like SMS, phone calls, and app notifications are marked as interruptions, which can disrupt flow state and reduce team efficiency and satisfaction.
    • Response effort: The sum of time between incident acknowledgment and resolution. This metric roughly estimates time spent on incident response.
    image.png

    Report download and data export

    You can now print reports directly from the console for work summaries. Below each report, we provide detailed data that can be exported to CSV for further analysis.

    image.png
  • Upgrade for Incident Isolation

    Many users have reported that Flashduty's incident permission control was relatively weak. We have now made improvements to address this.

    Improvement

    1. Collaboration spaces now support access levels. When set to private, incident data is only accessible to team members and account administrators. Other members can only view incidents in private spaces through shared links.
    image.png
    1. The incident list now supports My Channels filtering. When selected, it only shows incidents from your spaces.
    image.png

    Best Practices for Data Isolation

    We believe platform data isolation has three levels, in descending order of strictness. Each level has recommended implementation methods:

    1. Personnel Isolation: For teams requiring separate personnel and encrypted information.

      Register multiple entities, with complete isolation of personnel and resources, managed separately.

    2. Resource Isolation: When you don't want other members to see or handle your incidents.

      Set channel access level to private, preventing other members from seeing this channel and its incidents. Note that account administrators still have access.

    3. Visual Experience: When you don't want to see alerts unrelated to you or your team.

      Keep the My Channels filter selected in the incident list. When you need to view all data, simply remove this filter.

    We look forward to your feedback!