How to set up sensitive words? Configure built-in sensitive word service

The Instant Messaging (IM) service includes a built-in sensitive word feature. This guide shows how to set it up in the Developer Console. Supported languages for filtering include: Chinese, English, Japanese, German, Russian, Korean, and Arabic.

:tipping_hand_man: The sensitive word feature is a basic protection tool for text only (default limit: 50 words). It doesn’t replace professional content moderation.

Steps

Go to the RC Console - Sensitive Words Settings page to:

  • Add or remove sensitive words

  • Choose actions: block messages or replace sensitive characters

  • Export the sensitive word list

  • Add custom message types for filtering (default: only works with RC’s built-in text messages, ObjectName: RC:TxtMsg)

Click Add on the Sensitive Words Settings page and select the tab to add words.

Notify senders when a message is blocked

By default, senders aren’t notified if a message is blocked due to sensitive words. If you want senders to know, submit a ticket to enable Blocked Message Status Callback to Sender and set up a listener on the client side (requires Android/iOS SDK version ≧ 5.1.4, Web ≧ 5.0.2).

See the “Message Block Notification Callback” docs for each client:

Enable sensitive word filtering for server API messages

By default, messages sent via the server API aren’t filtered. To enable it, go to the Basic Features section in the Developer Console and turn on Filter Server API messages.

Set up sensitive word filtering for custom messages

Click Set custom messages on the Sensitive Words Settings page. Provide the ObjectName of the custom message type and the key in the content JSON structure. Once set up, the value for this key will be filtered.

Notes on message identifiers:

  1. All message identifiers (ObjectName) you add will filter the content of their corresponding key. For example, the built-in “Text Message” type (ObjectName: RC:TxtMsg) filters the value of the “content” key in the message body.

  2. Custom messages must follow SDK standards and be valid JSON.

  3. Avoid starting with “RC:” to prevent conflicts with RC’s built-in message ObjectNames.

  4. Test in the development environment before deploying to production to ensure filtering works. If it fails, submit a ticket.

Adjust the sensitive word limit

Increasing the sensitive word limit is a paid service. The default is 50 words. To adjust, go to the Extended Services tab in the Chat Pricing Plans page in the Developer Console. Only Chat Premium Plan or Chat Ultimate Plan users can do this. See billing details for costs.

References

Need help?

Submit a ticket if you have questions.