Typical Workflows

Dawnvox provides two main workflows for content moderation: automated moderation with callback notifications, and manual moderation through the dashboard. These workflows allow users to control how content is moderated on their platform and ensure they are always informed about the status of their content.

Automated content moderation workflow

This is the default workflow where content is moderated automatically based on predefined rules. Users can take actions based on the callback result.

Process

1. Content Submission: A user submits content for moderation (e.g., review, feedback, comment, image).
2. Moderation Process: Dawnvox automatically evaluates the content using predefined rules (e.g., HATE, SPAM, SEXUAL).
   • The content is assigned a status:
     • APPROVED: The content is deemed safe.
     • BLOCKED: The content is flagged as inappropriate.
     • PENDING: The content requires further review.
3. Callback Notification: Once the moderation process is complete, Dawnvox sends a callback to your platform with the moderation result (e.g., approved, blocked, or pending).
4. User Action Based on Callback:
   • Publish Content Immediately: If the content is APPROVED, the platform can immediately publish the content.
   • Store for Further Review: If the content is PENDING, the platform may store the content until it is moderated.
   • Block Content: If the content is BLOCKED, the platform can automatically block or remove it.

Workflow Example

• A comment is submitted to the platform.
• Dawnvox analyzes the content and flags it as HATE (BLOCKED).
• The platform receives the callback, sees that the content is blocked, and automatically removes the comment.

Manual content moderation workflow

For content that requires human intervention or for more sensitive cases, the content can be queued for manual review. This workflow provides users with the ability to manage content directly in the dashboard.

Process

1. Content Flagged for Review: Content may be flagged for manual review if it is marked PENDING or if it needs further attention based on the rules (e.g., uncertain or borderline content).
2. Manual Review in Dashboard: The content is placed in the Manual Moderation Queue. Moderators can review the content and view reasons for the flagging (e.g., SPAM, SEXUAL, HATE).
3. Moderator Decision:
   • Approve: The moderator can approve the content if they believe it is appropriate.
   • Block: The moderator can block the content if it violates rules.
   • Leave Pending: The moderator may decide to leave the content in the PENDING state if further clarification is needed.
4. Update and Callback: After the manual decision is made, the content status is updated and a callback is sent to your platform to notify it of the new status.

Workflow Example

• A user submits a comment that is flagged as PENDING due to unclear context.
• The content is added to the Manual Moderation Queue.
• The moderator reviews the content and decides to block it due to HATE speech.
• The platform receives the updated status via callback and removes the content.

How you should handle content that is published

Publish content and take action based on callback

• Content Submitted: User submits content for moderation.
• Callback Received: Once Dawnvox sends the callback, the user can immediately publish the content if it’s approved or block it if it’s flagged as inappropriate.
• Action Taken:
  • If approved, publish immediately.
  • If blocked, automatically reject or remove the content from the platform.

Store content in the background and wait for confirmation

• Content Submitted: User submits content.
• Background Processing: The platform stores the content in the background and waits for a callback notification.
• Callback Received: Once the callback is received, the platform can then make an informed decision to:
  • Publish: If approved, the content is published to the platform.
  • Hold for Further Review: If pending, the platform can hold the content for manual review.
  • Block: If blocked, the content is rejected or flagged for removal.

Workflow Example

• A user submits a feedback comment.
• The platform stores the comment in the background and awaits the moderation result.
• Once the callback is received:
  • If APPROVED, the content is displayed on the platform.
  • If PENDING, the content is queued for manual review.
  • If BLOCKED, the content is removed or flagged for review.