Development Guide

The IM service supports content moderation for IM messages.

• The IM service has a built-in sensitive word mechanism. Note that this mechanism is only a basic protection measure and is limited to text content (with a default maximum of 50 sensitive words). It cannot replace professional content moderation services.
• RC's Content Moderation Service Product provides comprehensive support for IM content moderation, including text, images, voice clips, and short videos, with accurate identification of sensitive information.
• If you wish to implement your own moderation system or integrate with a third-party moderation service, you can use the Message Callback Service.

If a message is blocked due to being flagged as inappropriate, the sender will not be notified by default. If your app wants to notify the sender that the message has been blocked, you can enable the Blocked Message Status Callback to Sender feature in the Basic Features section of the RC Console (requires Android/iOS SDK version ≧ 5.1.4, Web ≧ 5.0.2). For more details, see Message Block Notification Callback.

tip

By default, if a one-to-one chat message is blocked due to containing sensitive words or failing moderation, it will still be stored in the sender's server-side message history. Additionally, the user will receive this message as a compensation when logging in from other devices. If you do not want messages containing sensitive words or failing moderation to be saved in the sender's message history or received as compensation, you can enable the Skip history for filtered messages feature in the Security section under Configuration > Chat settings > Basic features in the RC Console.

Sensitive Word Mechanism

Note

• The client does not provide management interfaces for this feature, only callback interfaces to notify the sender when a message is blocked. For more details, see Message Block Notification Callback.
• To moderate text (with semantic detection), images, voice clips, and short videos, it is recommended to use RC's Content Moderation Service Product.

The Sensitive Word Mechanism is a basic protection measure that only supports identifying and filtering sensitive words in text messages. For messages that contain sensitive words, you can choose to block the message (not deliver it to the recipient) or replace the sensitive words according to specified rules before delivering the message.

Currently supported languages for sensitive word filtering include: Chinese, English, Japanese, German, Russian, Korean, and Arabic.

You can manage sensitive words in the development or production environment under your App Key through the following methods:

Function Description	Client API	RC Server API	Console
Add sensitive words, with optional replacement content	Not provided	Add Sensitive Word	Sensitive Word Settings page
Remove sensitive words	Not provided	Remove Sensitive Word	Sensitive Word Settings page
Batch remove sensitive words	Not provided	Batch Remove Sensitive Words	Sensitive Word Settings page
Get sensitive word list, including replacement content	Not provided	Get Sensitive Word List	Sensitive Word Settings page

Default Behavior

• By default, a maximum of 50 sensitive words can be set.
• By default, this mechanism only applies to messages sent from the client SDK.
• By default, it only supports identifying sensitive words in official built-in text message types (message identifier RC:TxtMsg). Supported conversation types include one-to-one chat, group chat, chatroom, and ultra group. Modified text messages in ultra groups are also subject to sensitive word identification, blocking, or filtering by default.

Configuration Adjustments

• Chat Premium Plan or Chat Ultimate Plan users can adjust the maximum number of sensitive words in the Extended Services tab under the Chat pricing plans page in the console. Specific features and fees are subject to the Billing Documentation.
• If you want to apply sensitive word filtering to messages sent via the server API, you can enable the Server API Message Filtering for Sensitive Words switch in the Basic Features section of the console.
• If you want to enable the sensitive word mechanism for custom message types, you can click Set Custom Messages on the Sensitive Word Settings page. Provide the ObjectName of the custom message type and the corresponding key in the content (Content) JSON structure to filter sensitive words in the value of that key.

IM Content Moderation Service

Note

The client does not provide management interfaces for this feature, only callback interfaces to notify the sender when a message is blocked. For more details, see Message Block Notification Callback.

If you want comprehensive moderation of IM content, you can use RC's Content Moderation Service Product, which provides IM Moderation and RTC Moderation services.

IM Moderation is designed for instant messaging and offers the following capabilities:

• Moderation of text content
• Moderation of images
• Moderation of voice clips
• Moderation of short videos
• Moderation of custom message types (requires submitting a ticket)
• Moderation of message modifications in ultra group conversations
• Viewing moderation reports in the console
• Querying IM moderation records in the console
• Moderation result callbacks

You can enable the IM Moderation service in the [IM Moderation] page of the console and configure the callback address for moderation results. For more details, see the server documentation Moderation Result Callback.

IM Content Moderation Billing

The content moderation service is a paid service. The development environment can be used for free, but the production environment requires pre-payment. For specific billing details, see Pricing · IM Moderation.

Message Callback Service

If you want to integrate your own moderation system or a third-party content moderation service, you can use the Message Callback Service.

The Message Callback Service (formerly Template Routing) provides a message filtering mechanism. You can synchronize messages to your specified server based on parameters such as sender ID, recipient ID, message type, and conversation type. In ultra group conversations, message content modifications and message extensions are also supported for synchronization to your specified server.

After messages are synchronized to your server, you can use your own moderation system or integrate with a third-party moderation system. The RC server will decide whether to deliver the message, replace its content, and how to replace it based on the response from your application server.

You can manage the status and routing rules of the Message Callback Service for your App Key in the development or production environment through the Message Callback Service page in the console.

For details on how to create routing rules and the callback parameters, refer to the Message Callback Service documentation.

Message Callback Service Billing

Fees are subject to the Billing Documentation.