Why @ mention
In busy WeCom group chats, responders can miss alert notifications. By enabling @ mention, the bot automatically @ mentions the corresponding responders when pushing incident notifications, ensuring they are alerted immediately. Flashduty supports two approaches for WeCom bot @ mention. Here’s how they compare:Approach 1: Default (phone number matching)
This is the simplest approach with no extra configuration required. The system automatically matches WeCom members using the phone number bound to their Flashduty account.Prerequisites
- The phone number bound in Flashduty must exactly match the phone number on the WeCom account
Configuration steps
1
Verify phone number consistency
Ensure Flashduty member phone numbers match their WeCom account phone numbers. You can view and edit member phone numbers in Platform → Organization → Members.
2
Enable @ mention
Go to the target channel’s Escalation rule, find the WeCom bot notification channel, expand Advanced, and enable the Enable @ mentions toggle.
Approach 2: Mapping table (user_id matching)
If member phone numbers differ between the two platforms, or you prefer @ mentions to appear inline within the notification content, use the mapping table approach. This approach requires you to maintain a mapping table between Flashduty member emails and WeCom user_ids.Prerequisites
- You have obtained the WeCom user_ids for your members (available from the WeCom admin console or API)
Configuration steps
1
Obtain WeCom user_ids
Log in to the WeCom admin console, go to Contacts, click on a member to view their details, and find the Account field — this is their user_id.You can also obtain user_ids in bulk through the WeCom API.
2
Create a mapping table
- Go to the target channel’s Escalation rule and edit the WeCom bot notification channel.
- Expand Advanced, enable Enable @ mentions, and click Quick create mapping schema beside User information mapping.
- Enter a mapping table name and team, then upload a CSV file. This entry presets the source label
emailand result labelwecom_userid. Use the following columns and data:
3
Configure escalation rule and link the mapping table
Go to the target channel’s Escalation rule, find the WeCom bot notification channel:
- Expand Advanced and enable the Enable @ mentions toggle.
- In the User information mapping dropdown, select the mapping table created in the previous step.
Verify the result
After completing the configuration, trigger a test alert to verify that @ mention works:- Confirm the target channel has a WeCom bot configured as a group chat notification channel.
- Trigger a test alert and check the notification message in the WeCom group chat.
- Verify that the responders are correctly @ mentioned.
Default approach: @ mention not working
Default approach: @ mention not working
- Confirm the Enable @ mentions toggle is enabled
- Confirm the member’s phone number in Flashduty exactly matches their WeCom account phone number (including country code)
- Confirm the member is in the group chat where the bot is configured
Mapping table approach: @ mention not working
Mapping table approach: @ mention not working
- Confirm the Enable @ mentions toggle is enabled and the correct User information mapping is selected
- Confirm the email-to-user_id mappings in the table are correct
- Confirm the WeCom user_ids are accurate (verify in the WeCom admin console under Contacts)
- Confirm the member is in the group chat where the bot is configured
Further reading
Notification channel configuration
Learn about all bot types, configuration methods, and advanced options
Escalation rules
Learn about notification methods and group chat configuration in escalation rules