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
Core features
- 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.
- Mobile handling: Complete core operations on your phone, including searching, viewing details, acknowledging, closing, and escalating incidents.
- Voice number sync: The App can automatically sync Flashduty On-call voice notification numbers to phone contacts, avoiding misinterception.
Enable and use
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
Not receiving App push notifications
- Check if notification permissions are enabled for Flashduty App in phone system settings
- Confirm App push is set as one of the notification channels in your escalation rules
- If “Follow Personal Preferences” is set, check if Flashduty App is selected in personal notification settings
- 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
Voice, SMS, email
- Use Cases
- How to Enable
- Voice Numbers
- 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
Why can't I receive voice notifications?
Why can't I receive voice notifications?
- 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
- Check carrier services: Some users may have carrier-level high-frequency spam call blocking enabled; check and configure through your carrier’s official account
- Ported number users: Check blocking status across multiple carriers
Why are emails going to spam?
Why are emails going to spam?
- Check “Spam” or “Junk” folders, mark Flashduty On-call emails as “Not Spam”
- Add Flashduty On-call’s sending domain or address to your email whitelist
- 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 those tools.App integration (recommended)
App integration provides the most complete interactive experience: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.
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
- Feishu/Lark Bot
- Dingtalk Bot
- WeCom Bot
- Telegram
- Slack
- Generic Webhook Bot
- Zoom
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 URL3
Integrate with Flashduty On-call
Copy Webhook URL, add Feishu/Lark bot in Flashduty On-call’s Channel → Escalation Rules
Advanced settings
All bot types support the following advanced options, accessible by expanding Advanced Settings during configuration:FAQ
Zoom notification fails with 'Failed to send bot message'?
Zoom notification fails with 'Failed to send bot message'?
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:
- Create a new Incoming Webhook connection in Zoom
- Test the new Webhook URL in your Flashduty escalation rule
- 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
- If the new Webhook also fails, check the message content format or contact Zoom support
Bot @ mentions are not working?
Bot @ mentions are not working?
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
General configuration
- Customize notification content: Edit message formats for each channel under Template Management in the console. See Notification Template Configuration.
- Different notification strategies for different severities: Routing rules (Integration Center → Alert Events → your integration → Routes) decide which channel an alert goes to. Escalation rules (Channel → Escalation Rules) decide who is notified, through which channels, and how to escalate when no one responds. See Escalation Rules.
- Notifications for @mentions in comments: For channels and defaults, see Personal Settings - Collaboration & follow-up.
Related topics
Escalation Rules
Configure alert notification rules and escalation paths
Notification Templates
Customize notification content format for each channel