Chat and Notifications
Use chat for conversation and alerts for actionable system state.
Mental Model
- Alerts = triage stream (what changed, what needs action).
- Chat = conversation stream (team and member discussion).
Treat alerts as your queue, chat as your workspace.
Daily Operating Flow
- Open Alerts and clear actionable items first.
- Jump from alerts into event/hub/ticket context.
- Continue discussion in Chat when coordination is needed.
- Return to alerts to verify the state change is complete.
Delivery Setup
Use Notification Delivery for:
- push subscription health,
- email preference controls,
- repair and diagnostics tools,
- test send actions.
Mention and Channel Boundaries
- Mentions are scoped to valid channel members.
- If someone cannot be mentioned, verify they are in the channel.
- Event/hub privacy settings can affect channel visibility and reach.
When Notifications Fail
- Confirm browser notification permission is
Allowed. - Run push repair in Notification Delivery.
- Confirm topic-level delivery preferences are enabled.
- Check blockers/extensions/shields.
- Send a test notification and capture result.
If still failing, escalate with URL + UTC timestamp + subscription diagnostics.
Alert Hygiene Best Practices
- Clear or archive read alerts regularly.
- Use selection mode for bulk cleanup after high-volume periods.
- Keep critical alert types enabled for event-day operations.
Related Guides
Last updated on