Include detailed violation “Reasons” in moderation_engine_blocked Webhook Payload
Description:
Moderation is functioning correctly, and the CometChat Dashboard displays comprehensive Violation Details → Reasons whenever a message is blocked. However, the moderation_engine_blocked webhook payload currently only includes rule metadata such as:
rule_idrule_namerevisionactionblockedAt
The payload does not include the detailed “Reasons” explanation that is visible in the dashboard.
Problem Statement:
Since the webhook does not expose the violation reason, client applications can only show a generic message like “Message blocked” to end users. This limits transparency and negatively impacts user experience.
Requested Enhancement:
Enhance the moderation_engine_blocked webhook JSON payload to include a detailed violation_reasons (or similar) field, matching the Violation Details → Reasons shown in the dashboard.
Log in to comment and vote
No comments yet
Be the first to share your thoughts.