Incident types
Incidents from Safe Voice and Safe Text appear in the Moderation queue.
Moderation incident types
Player reports
Player submitted reports. The Moderation queue differentiates between reports submitted by players and automated reports triggered by behaviours. Player reports will automatically contain Safe Voice and Safe Text related data if they're present in your project.
Safe Voice incident types
Mute triggers
When a player mutes another player, a mute trigger incident is triggered. Moderators can see this action in an incident and see who muted who.
Ad-hoc audio requests
It's possible to send ad-hoc audio requests to trigger custom screenings based off properties of your choice. For example, you can require screening of all channels for a given player, or all players for a given channel. These incidents are marked as Custom in the dashboard.
Safe Text incident types
Safe Text reviews text messages sent between players.
Proactive text detections
When Safe Text detects toxic or disruptive behavior in text messages, it treats the offending messages as an incident, without a player having to report it themselves. Those incidents show up in the Moderation queue.
If a player does report the messages the text detections are attached to the submitted player report.
For more information on text detections refer to Context analysis.