Skip to main content

​
Overview

​
Supported channel matrix

Flashduty On-call provides a comprehensive notification matrix covering mobile App, traditional communication, and mainstream instant messaging (IM) tools.

​
Core notification channel configuration

​
Flashduty app

With the Flashduty App, you can handle incidents from your phone the same way you do at your computer. Flashduty App
Critical Notifications, Must Reach Users: On iOS, the App uses Apple’s Critical Alerts, which break through silent and Do Not Disturb modes. On Android, it uses system-level push channels from major manufacturers, so the App receives notifications even in the background.Efficient Mobile Handling: Complete all core operations on your phone including searching, viewing details, acknowledging, closing, and escalating incidents.Smart Voice Notification Recognition: App can automatically sync Flashduty On-call voice notification numbers to phone contacts, avoiding misinterception.
1

Download and Install

For download options, see Personal Settings - Flashduty APP
2

Login and Link Device

Open App and login with your Flashduty account, or scan to login from console. After login, current device automatically links to your account
3

Enable Key Permissions

  • iOS Users: In phone System Settings → Notifications → Flashduty On-call, enable Critical Alerts toggle
  • All Users: Recommend enabling Sync Contacts permission in App Settings → Voice Notifications
Why am I not receiving App push notifications?
  1. Check if notification permissions are enabled for Flashduty App in phone system settings
  2. Confirm App push is set as one of the notification channels in your escalation rules
  3. If “Follow Personal Preferences” is set, check if Flashduty App is selected in personal notification settings
  4. Android users: Check that both notification channels are on in system notification settings. The channel names appear in Chinese. “故障通知 (Incident notifications)” carries Warning and Info incidents. “紧急通知 (Urgent notifications)” carries Critical incidents, shows on the lock screen, and can bypass Do Not Disturb. You manage the two channels separately, and turning one off mutes that severity
What opens when I tap a push notification?Tapping a notification opens the corresponding incident detail page directly in the App, where you can immediately acknowledge, close, and perform other actions.

​
Voice, SMS, email

  • Incident Escalation: Use voice calls for forced delivery in the final stage of escalation rules
  • IM Fallback: When IM app message delivery fails, system automatically sends supplementary reminders by SMS or email
  • Offline Coverage: Cover team members in poor network environments or without smartphones
  1. Check phone blocking settings: Check phone’s blacklist or spam interception records. Flashduty On-call uses fixed numbers for voice push; you can download Flashduty App to sync number whitelist
  2. Check carrier services: Some users may have carrier-level high-frequency spam call blocking enabled; check and configure through your carrier’s official account
  3. Ported number users: Check blocking status across multiple carriers
  1. Check “Spam” or “Junk” folders, mark Flashduty On-call emails as “Not Spam”
  2. Add Flashduty On-call’s sending domain or address to your email whitelist
  3. Contact company email administrator to set Flashduty email whitelist at domain level (no-reply@notice.flashcat.cloud)

​
Instant messaging (IM) integration

Integrating Flashduty On-call with your team’s daily IM tools (like Feishu/Lark, Dingtalk) allows receiving and handling incidents in familiar collaboration environments, greatly improving On-call efficiency. App integration provides the most complete interactive experience. We strongly recommend teams with the capability to use this method.

Interactive Cards

Acknowledge, close, escalate directly on IM message cards without redirecting

Passwordless Operations

After linking member accounts with IM accounts, no need to re-login to Flashduty when operating

Full-featured

Supports getting complete incident details, viewing timeline, adding comments, and so on.

Simple Maintenance

One-time configuration, long-term effectiveness

​
Configuration guide

Feishu/Lark Integration

Feishu/Lark app integration

Dingtalk Integration

DingTalk app integration

WeCom Integration

WeCom app integration

Slack Integration

Slack app integration

Teams Integration

Microsoft Teams integration

​
Bot integration

If your team cannot do app integration temporarily, using bots is a simple, quick, and effective alternative. Use Cases:
  • Cannot obtain IM platform admin permissions to install apps
  • Only need basic incident notification push functionality, no complex online interaction needed
  • Need to quickly establish notifications in temporary project groups or cross-department groups
1

Create Custom Bot

Enter Feishu/Lark group chat → Group Settings → Group Bots → Add Bot → Select Custom Bot
2

Configure Bot Parameters

Set bot name and description, configure custom keyword: #, click Add to generate Webhook URL
3

Integrate with Flashduty On-call

Copy Webhook URL, add Feishu/Lark bot in Flashduty On-call’s Channel → Escalation Rules
Don’t use any of the above IM platforms? You can still use bot notifications. Flashduty doesn’t validate the domain of bot webhook URLs. Select any bot type (for example, Dingtalk Bot) and set the webhook URL to your own server endpoint. Implement that IM platform’s push protocol on your server to receive Flashduty notifications. This suits custom notification systems and non-standard IM tools. For step-by-step instructions, see the FAQ.

​
Advanced settings

All bot types support the following advanced options, accessible by expanding Advanced Settings during configuration:
The user mapping table defines the correspondence between Flashduty users and IM platform users. You can create and maintain mapping tables on the Platform Management → Mapping Table Management page.

​
FAQ

Check whether the Webhook URL is accessible in your current network environment. Telegram services may be restricted in some regions. Consider using a reliable proxy service address.
After adding the Bot to the target group, you can call the Telegram Bot API getUpdates method to obtain the group Chat ID. You can also use tools like @userinfobot.
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.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 is no longer valid, often because its creator left the organization — 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.
After adding the Incoming Webhook app in Zoom, use the /inc connect flashduty command. The returned connection information includes the Verification Token.
Verify the following:
  • The @ mentions toggle is enabled
  • Feishu/Lark, Zoom: a user mapping table is correctly selected with complete mappings
  • WeCom: if using a mapping table, verify the mappings are correct
  • Dingtalk: verify member phone numbers are correct
  • Slack: verify member account associations are correct

​
General configuration

Flashduty On-call allows you to customize personalized notification messages for different channels.Configuration Path: Console → Template ManagementHere you can select different notification types (like incident trigger, acknowledgment, closure, and so on) and edit message formats for each channel. Templates support variable references to dynamically display incident information.For more details, see Notification Template Configuration.
You can design refined notification workflows based on any dimension like alert severity, source, labels. You do this mainly with routing rules and escalation rules.
  • Routing Rules: Integration Center → Specific Integration → Routing Rules. Determines which alerts should be routed to which channel
  • Escalation Rules: Channel → Escalation Rules. Determines who incidents should notify, through which channels, and how to escalate when no one responds
For example, P1 incidents can first notify the primary on-call by Flashduty App and Feishu/Lark app. If no one acknowledges within 5 minutes, Flashduty calls their supervisor.
When you type @ to mention a member in an incident detail comment or a post-mortem report, Flashduty notifies that person. The notification has the comment summary, incident information, and a link to the incident.
  • Channels: Follows the mentioned person’s preferences. Options are SMS, email, and all IM apps (direct messages in DingTalk, Feishu/Lark, WeCom, Slack, and Microsoft Teams), and email is the default. Voice and Flashduty App push aren’t available here
  • Preference: The mentioned person can adjust this under Personal Center → Notification Preferences → Collaboration & follow-up → Collaboration Mention
  • No duplicates: The same comment never triggers duplicate notifications

Escalation Rules

Configure alert notification rules and escalation paths

Notification Templates

Customize notification content format for each channel