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.
Channel TypeNotification FormInteractiveRatingDescription
Flashduty AppDirect Message✅ Native⭐⭐⭐⭐⭐Top choice for mobile work, supports incident handling, full-featured
Voice CallDirect Message✅ Keypad⭐⭐⭐⭐High availability, used for major incident escalation, forced delivery
SMSDirect Message❌ Text only⭐⭐High availability, covers no network signal scenarios
EmailDirect Message❌ Text only⭐⭐Fallback notification channel, suitable for detailed incident reports
IM App IntegrationDirect/Group Chat✅ Card interaction⭐⭐⭐⭐⭐Top choice for team collaboration, supports handling incidents directly in groups
IM BotDirect/Group Chat❌ Link redirect⭐⭐Quick integration alternative, simple configuration, no admin permissions needed

​
Core Notification Channel Configuration

​
Flashduty App

The Flashduty App is the most efficient mobile work tool for On-call engineers. Wherever you are, you can fully control the incident handling process just like at your computer. Flashduty App
Critical Notifications, Must Reach Users: iOS critical alerts are based on Apple’s official Critical Alerts protocol, penetrating silent and Do Not Disturb modes; Android supports system-level push channels from mainstream manufacturers, ensuring App receives notifications even in 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

Search “Flashduty” in App Store or major Android markets, or scan QR code in console personal center
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

​
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 via 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, etc.

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 does not validate the domain of bot webhook URLs, so you can select any bot type (e.g., Dingtalk Bot) and set the webhook URL to your own server endpoint. Simply implement the corresponding IM platform’s message push protocol on your server to receive Flashduty alert notifications. This approach is ideal for custom notification systems or integrating with 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:
SettingSupported Bot TypesDescription
AliasAllSet an alias for the bot to help remember and distinguish different notification channels
Severity filterAllSelect which alert severity levels trigger notifications. Incidents with unselected severity levels will not be pushed
Notification event typesFeishu/Lark, Dingtalk, WeCom, Slack, ZoomSelect which event types trigger notification pushes (e.g., triggered, acknowledged, closed). All selected by default
@ MentionsFeishu/Lark, Dingtalk, WeCom, Slack, ZoomWhen enabled, @ mentions corresponding responders. Feishu/Lark and Zoom require a user mapping table; WeCom optionally supports one; Dingtalk matches by phone number by default. Dingtalk also supports @ all
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 has been invalidated (commonly caused by the creator leaving 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, etc.) 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. This is mainly achieved through 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, you can configure: P1 level incidents first notify primary on-call via Flashduty App and Feishu/Lark app; if no one acknowledges within 5 minutes, notify their supervisor via voice call.

Escalation Rules

Configure alert notification rules and escalation paths

Notification Templates

Customize notification content format for each channel