SocialEpochHelp Center
Browse Help Topics
Group operationsFor: Employees and administrators

Send Notifications and Manage Messages with Group Assistant

Choose the notification scope for the right group and configure moderation and sensitive-word rules with administrator access.

Page contentsBefore you startFirst check the group and operation scopeSelect members who need to be reminded and send notificationsUse group management operations with cautionConfigure matching and processing of sensitive wordsCheck accumulation rules and resultsCheck your resultFrequently asked questions

Before you start

  • Logged into an account that participates in the target group and has permission to send notifications.
  • Management actions such as banning, removing members, or deleting other people's messages require corresponding group management permissions.
  • Sensitive word configuration requires the corresponding permissions of the admin console. Verify the rules in your own test group first.

Where to find it
Client→Group Assistant; sensitive words: admin console →group risk control management→sensitive word configuration→add.

First check the group and operation scope #

Open the Group Assistant, first select the target group, and check the group name, account, and membership range. Group message reminders and group management are different types of operations: sending notifications should only be directed to group members who need to receive the content, while banning, deleting messages, or removing members requires administrative permissions and clear reasons.

For first-time use, check the results on the company's own test group first, and do not treat the production group as a test subject.

Select members who need to be reminded and send notifications #

  1. Select the group to which you want to send messages.
  2. According to the notification recipient, you can choose to remind everyone, exclude administrators and group owners, or customize the selection of members.
  3. Enter the notification content and add images and other materials according to the method supported by the current editor.
  4. If you use translation, check the translation result first and then confirm sending.
  5. Check the group and reminder range again before sending, and check the actual messages in the group after sending.

Reminding members is a notification method, which does not guarantee that everyone will read it, nor does it guarantee that account risks will be reduced.

Selection scope, content and management operations of Group Assistant · Manual page 18 · Click to enlarge

Use group management operations with caution #

The data lists related operations such as reading, exiting the group, banning, and removing members. Before executing, you should check the scope of objects displayed on the interface: exiting all groups has different effects than exiting one group; prohibiting members from speaking is not the same operation as ordinary notifications.

For actions such as exiting, banning or removing members, first check the selected group and members, current account permissions and confirmation prompts, and do not skip the verification just because the name contains "one click". The information is unclear on the difference between the two read operations, so the current prompt should prevail.

Configure matching and processing of sensitive words #

  1. Go to the admin console to enter group risk control management, sensitive word configuration, and click Add.
  2. Fill in the words that need to be processed and select the matching method: fuzzy matching is for messages containing the word, and precise matching is for messages that are exactly the same as the word.
  3. Choose an action: Warn only, Delete, Delete and warn, or Delete and remove the member.
  4. Warnings should describe which group rule was triggered and use clear, appropriate language.
  5. After completing the configuration, verify the hit and miss messages in the test group to confirm that normal discussions will not be mishandled.

Check accumulation rules and results #

If you need to give members an opportunity to make corrections, you can configure cumulative deletion or warning conditions in the automatic removal related settings, and set the frequency of warnings within a certain period of time as needed. The threshold should be configured according to the enterprise group rules and the current interface, and the number of examples should not be used directly.

When the rule does not take effect, first check the matching method, rule content, target group and account management permissions; when a hit occurs by mistake, you should first check the scope of the rule and not just increase the punishment. The execution results need to be confirmed individually within the test group.

Check your result

  • Notifications in the test group correspond to the correct group and the expected alert member range.
  • In the sensitive word test, hit and miss messages were processed as expected.
  • The cumulative processing conditions and warning frequency are consistent with the actual configuration, and normal messages are not mishandled.

Frequently asked questions

What is the difference between fuzzy matching and exact matching?

Fuzzy matching is based on whether the message contains sensitive words, while precise matching requires that the message content is completely consistent with the sensitive words. Check the boundaries with test messages first to avoid mishandling normal discussions.

Can turning on reminder for everyone ensure that group members can see it?

No. The reminder range is not equal to the reading results, nor can it be used as a guarantee of account security or message reach.

Can ordinary group members delete other people's messages or remove members?

These are group management actions and require corresponding permissions. First check whether the current account has administrative permissions. The absence of a tool entrance means that the operation must be executable.