This page explains how Console moderators and administrators manage real‑time chat: broadcasting, monitoring live streams, filtering, enforcing policy, handling mentions, and applying message-level actions.
Broadcast
Send official announcements in Broadcast channels
Monitor Live
Track real‑time message flow & pause stream
Filter
Surface flagged or threaded parent messages
Enforce
Delete, clear flags, mute, ban, blocklist
Mentions
Govern @user and @all usage
Optimize
Refine quality & reduce noise
Broadcast Messages
Broadcast channels allow only admin / authorized staff to post while all other members are read‑only—ideal for high-signal announcements, policy updates, campaigns.1
Create Broadcast Channel
Create channel → select type Broadcast (see Channel Management for creation basics).
2
Open Channel
Select the broadcast channel from list.
3
Compose
Click Broadcast Message → choose message type → write content.
4
Mention (Optional)
@ to mention up to 30 members (strategic, not spammy).
5
Send
Click Broadcast and verify delivery.
Overusing broadcast channels for routine chatter reduces member trust. Reserve for material value updates.
Live Message Monitoring
Admins can enter any eligible channel to observe real‑time messages, apply filters, enforce policies, and send official interventions.Use Cases
Use Cases
Crisis escalation, abuse response, event moderation, launch day traffic, sentiment sampling.
Capabilities
Capabilities
View live flow, pause stream locally, filter flagged / threaded parents, inspect mentions, action messages.
Performance Note
Performance Note
Pausing stream does not halt user posting; backlog is applied once unpaused.
Pausing Data Stream
If messages scroll too quickly for review, pause to stabilize viewport:1
Assess Need
Identify rapid influx / potential violation cluster.
2
Activate Pause
Click Pause (stream stops updating locally).
3
Review & Action
Perform deletions, flag clearing, member actions.
4
Resume
Unpause to apply buffered messages.
Pause is a local console viewing control—users continue real‑time conversation unaffected.
Message Types
The system supports multiple structured types:| Type | Description |
|---|---|
| Text | Plain textual content |
| Image | Message containing an image asset |
| File | Message containing a downloadable file |
| Audio | Message containing an audio clip |
| Custom | Developer-defined payload / structured custom data |
Custom messages should be clearly explainable in moderation notes to ensure consistent enforcement.
Filtering
Displays only messages flagged by users/admins for priority moderation.
Mentions Governance
@user
@user
Tag specific member for directed clarification or escalation. Use sparingly to avoid dogpiling.
@all
@all
Notifies entire channel—restrict to high-importance updates. Can be disabled in Feature Settings.
Viewing Mentions
Viewing Mentions
Open channel in management view → Mentioned Users column lists resolved user displayName(UserId) pairs.
Disabling @all
Disabling @all
Settings → Feature Settings → Uncheck “Allow to mention everyone in the channel”. @user stays enabled.
Excessive @all usage increases notification fatigue; audit usage frequency monthly.
Message Actions
Removes all flags post-review to restore normal status signals.
Ban before removing if long-term exclusion is intended; removing first may clear enforcement state.
Enforcement Workflow Example
1
Detect
Filter Flagged or observe pattern manually.
2
Stabilize
Pause stream (optional) for heavy influx.
3
Evaluate
Open context thread; inspect history & mentions.
4
Action
Delete / Ban / Blocklist / Mute as appropriate.
5
Document
Log rationale in internal system (if required).
6
Restore
Clear flags where resolved → Resume stream.
Best Practices
Operational Discipline
Operational Discipline
- Use Pause only when necessary (avoid missing fast-moving signals).
- Batch similar actions to reduce context switching.
- Revisit blocklist quarterly for false positives.
Quality & Safety
Quality & Safety
- Delete only when content violates policy; otherwise educate via reply.
- Prefer Mute for temporary disruption vs immediate ban.
- Escalate self-harm / threat content per protocol before deletion.
Broadcast Hygiene
Broadcast Hygiene
- Consolidate multiple small announcements into a single structured broadcast.
- Avoid marketing repetition; track engagement drop-off metrics.
Mentions Strategy
Mentions Strategy
- Encourage targeted @user use for clarity.
- Limit @all to critical updates (target threshold e.g., <2 per week per channel).
Troubleshooting
| Issue | Likely Cause | Resolution |
|---|---|---|
| Stream not resuming | Pause still active | Click Resume; verify UI state |
| Flag not clearing | Permission or stale state | Refresh; confirm role; retry |
| @all still works after disable | Cached settings | Refresh channel view; re-save setting |
| Blocklist term not applied | Formatting mismatch | Add normalized (lowercase / trimmed) variant |
| Broadcast failed | Network or missing rights | Retry; verify broadcast privilege |
| User keeps reoffending | Mute instead of ban | Apply ban + document rationale |
| Deleted message visible shell | Expected placeholder | No action—design for audit clarity |
Quick Reference
Mention Limit
30 users / message
Filters
Flagged • Threaded Parent
Actions
Clear • Delete • Blocklist • Mute • Ban