Skip to main content
Plan requirement: This feature requires an On-call Pro or higher subscription. Learn more
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.

Quick start

1

Configure Integration

Go to On-call → Integration Center → Integration List → Instant Messaging, connect your IM application as needed, and follow the guide to enable war room functionality. At any given time, only one IM integration can have war room enabled.

Feishu/Lark Integration

Connect Feishu/Lark application

Dingtalk Integration

Connect Dingtalk application

WeCom Integration

Connect WeCom application

Slack Integration

Connect Slack application

Microsoft Teams Integration

Connect Microsoft Teams application
2

Create War Room

On any active incident’s details page, click Create War Room in the upper right corner.
Create War Room in Console

Create War Room in Console

3

Collaborative Handling

When incident responders change, relevant personnel are automatically synced to the war room. Other members can click View War Room on the incident details page to quickly join the conversation.In the war room, members can acknowledge, close, and snooze incidents, and receive incident status updates from Flashduty On-call.
Add Members in Console

Add Members in Console

4

Dismiss War Room

After the incident is closed, click Dismiss War Room from the … menu on the incident details page.
Dismiss War Room in Console

Dismiss War Room in Console

If someone later disables or deletes the war room’s IM integration, the console and the mobile app hide Add stakeholders to war room and Dissolve war room. In that case, ask an account owner or admin to open View war room on the incident details page and use Confirm unlink. It removes only the link between the incident and the group. It does not dissolve the group chat, and the timeline records “Requested war room unlink”. Before creating a new room, make sure the original group has been handled.
War room chats can’t be standing notification targets. War rooms open and close with their incidents. So neither the IM app groups picker in escalation rules nor the group chat channels picker in handoff notifications lists them. A saved chat that no longer exists (war room dissolved, bot removed, or group deleted) shows as Chat unavailable, and you can remove it.

Message sync

Flashduty posts key incident operations (acknowledgment, closure, snooze, comments, and so on) to the war room group in real time. Five action item and follow-up operations (created, assignees updated, completed, converted, and automatic conversion when the incident closes) are posted as plain text, for example:
  • Created: John created Action "Scale up the database connection pool"
  • Assignees updated: John updated assignees on Action "Scale up the database connection pool"
  • Completed: John completed Action "Scale up the database connection pool"
  • Converted: John converted Action "Scale up the database connection pool" to Follow-up
  • Automatic conversion: Incident closed. 3 unfinished action(s) became follow-ups; track them on the incident page.
  • In messages for follow-up operations, Action is replaced with Follow-up
  • When the operator cannot be resolved to a specific member, the message shows System as the operator

AI SRE

War rooms integrate deeply with AI SRE: you can @ AI SRE in the chat to follow up or start a new investigation; and when an enabled AI SRE automation whose trigger is War room created matches the incident’s channel and severity, that rule runs a first diagnosis in the group and posts its findings there as soon as the war room opens. See the AI SRE introduction and IM platforms.

AI SRE in the war room

Automatic first diagnosis

When the automation conditions above are met, a first round of findings is posted in the group as soon as the war room opens

Follow up in chat

@ AI SRE in the group to start or continue an investigation; the agent replies in the thread, visible to the whole team

Context-aware investigation

Reply to an alert or incident card and the agent resolves the referenced incident automatically — no manual context-pasting

Incident review

Generate structured post-mortems from the incident timeline and investigation evidence
To build a more comprehensive context of the incident’s full lifecycle, AI-generated post-mortem reads war room chat history. Ensure your IM integration has been granted the necessary permissions — see Feishu/Lark or Slack integration guides for details.

FAQ

Yes. When creating or connecting the related application, you need to manually grant the necessary permissions to ensure operational security.
Check the war room configuration steps on the integration configuration page or in Flashduty Docs → Integration Guide.To ensure Flashduty can successfully invite members, it needs to obtain their user ID on the IM platform. Ensure relevant personnel have completed at least one of the following:
1

Configure Notification Information (Recommended)

On the Flashduty On-call Personal Center → Personal Information page, fill in Notification Email and Notification Phone.
2

Use One-click Link Feature

If your IM integration supports it, use the One-click Link feature on the Link Users page. Flashduty On-call will use the notification email and phone configured in the user’s personal center to call application permissions for user information linking.
One-click Link Users Interface

One-click Link Users

3

Sign In Within IM App

If your IM integration supports it, complete a sign in within the IM app to automatically link accounts.
If the issue persists, contact Flashduty technical support.
WeCom requires application group chats to have at least 2 members. When creating a WeCom war room, Flashduty resolves the incident’s responders, incident owner, and the current operator into WeCom user IDs. If fewer than 2 members with linked WeCom accounts can be resolved, creation fails with the error:
Creating a WeCom war room requires at least two people. Add more linked WeCom members and try again.
Resolution: Ensure at least 2 of the incident’s responders have completed WeCom account linking (see the steps in “Why is my war room functionality not working as expected?” above). Use One-click Link or guide members to sign in within the WeCom app to complete the binding.
Creating a Microsoft Teams war room group chat requires at least 2 members with linked Teams accounts (resolved from incident responders, stakeholders, and the operator). Have members send linkUser {ID} in their personal Teams chat with Flashduty to link their accounts first.By design under least privilege, Flashduty never requests Microsoft Graph chat-deletion permissions. Dismissing a Teams war room sends an archival notice card to the group chat, unlinks it in Flashduty, and stops future event sync while keeping the Teams group chat and message history for post-incident review.