Before you start
- Use an administrator account with system configuration and risk control management rights.
- Applicable team members, corporate language conventions, and normal service hours have been identified and internal testing sessions have been prepared.
Where to find it
SalesEpoch admin console → SCRM Management → System Configuration; Content Rules: Risk Control Management → Risk Control Settings
Distinguish between time control and content control #
System configuration is used to stipulate that team members cannot use PC or mobile phones during certain periods. Risk control settings are used to check specific content sent by team members. The two solve different problems: when a message is not sent, you should first confirm whether it is a time limit, sensitive word rule, or other sending problem; do not regard all situations as network failures.
Configure team member ban time #
- Enter the disable time setting of "System Configuration" and add a new rule.
- Select the applicable days of the week and blackout time range.
- Select the device type and screenshots provide PC and mobile options.
- Clearly apply for team members by "selecting team members" to avoid selecting all by mistake.
- Confirm after reviewing the time and team member range, and check whether the target team members are subject to expected restrictions during the agreed period.
The manual does not explain the time zone used for the time, how to fill in the cross-day period, and how to handle logged in sessions. When cross-time zone teams are involved, confirm these rules on the current interface before applying them.
Configure rules for team members to send sensitive words #
- Enter "Risk Control Settings" and click "Add Sensitive Words".
- Fill in the words that need to be checked, and select the matching method and risk control level. Fuzzy matching means that if the word is included in the sent content, it will be triggered.
- Select the sending rule: send the original word, do not send it, or replace it with asterisks.
- After saving, use an internal test session to verify the content containing words and not containing words, and check the actual display of the message and the admin console reminder.
| rule | expected behavior |
|---|---|
| Original word sent | The content is still sent and the administrator is warned. |
| Do not send | Content containing sensitive words is blocked and administrators are warned. |
| Replace with asterisk | Sensitive content is replaced by interface rules and administrators are warned. |
View warnings and adjust for false triggers #
Go to risk control alerts, risk control notifications or risk control statistics to view the triggering team member, time, recipient and content. Confirm the business context first and then decide how to handle it. Fuzzy matching may override normal service terms, so don't directly restrict all team members with common short words. The manual does not fully describe the rules for capitalization, special symbols, and multi-language matching, and actual performance in the required languages should be confirmed through internal testing.
Check your result
- The team member, day of the week, and device ranges for the disabled day rule are correct.
- Test content is allowed, blocked, or replaced based on selected rules.
- The administrator finds the corresponding test record on the relevant warning page.
Frequently asked questions
Even if sensitive words are set, why is the message still sent?
First check whether "Send Original Word" is selected. This rule allows sending but provides a warning to the administrator.
What should I do if my normal speech is intercepted?
Check the matching method and sensitive word range. Fuzzy matching will be triggered when the word is included. You can use internal testing to locate the false triggering conditions first, and then adjust the rules.
Why are team members unable to use the client during a certain period of time?
The administrator first checks the disabled period, device type and applicable team members in the system configuration, and then checks the account qualifications and other login prompts.
According to pages 57, 64, 65, and 66 of the "2026-SalesEpoch Operation Manual".
Menus and features may vary by client version or account access. Follow the current interface and verify critical workflows with a test account first.