Skip to Content
Chat and Notifications

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

  1. Open Alerts and clear actionable items first.
  2. Jump from alerts into event/hub/ticket context.
  3. Continue discussion in Chat when coordination is needed.
  4. 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 and hub privacy settings can affect who can see, join, and mention people in a channel.

Starting Chats and Channels

Open Chat when you want to start a direct message, private group, hub channel, or event channel.

  • /chat is the universal create entry point for all four conversation types.
  • The creator now uses the same plain-language flow everywhere: choose what you are starting, where it belongs, who it is for, and what it should be called.
  • Hub and event pages reuse the same creator with the current scope already selected, so you do not have to choose the hub or event again.
  • Organisers can also create hub or event channels directly from /chat by searching for the hub or event they manage.
  • Use Hub -> Admin -> Chat and Event -> Admin -> Chat when you need to manage an existing channel roster over time.
  • Members still experience one inbox model, with hub/event labels and imagery doing the separation work.

Hub Channels

Use Hub -> Admin -> Chat when you need to manage which hub channels exist and who can access them.

  • General is for broad hub conversation.
  • Staff is for staff-only coordination.
  • Custom lets you create a purpose-built channel for a specific group or workflow.
  • Hub organisers can create long-lived support or ops channels here, then still use /chat for quick one-off starts when needed.

Access rules matter:

  • All hub members means every member can see and post in the channel.
  • Invite only means access is limited to the people you explicitly add.
  • Open is the loosest setting and should be used deliberately.

Before creating a new channel, answer these questions:

  1. Who needs to see this?
  2. Who needs to post in it?
  3. Is this a permanent hub channel or a temporary coordination space?

Event Chat Channels

Use Event -> Admin -> Chat as the main place to manage the event channel roster.

  • Ticket holders means anyone with an active ticket for that event can join, even if they are not a hub member.
  • Ticket holders who are members keeps the event chat inside the hub membership boundary for public-event/private-hub cases.
  • Staff is for event staff coordination.
  • Verified attendees (after check-in) is a later/additional channel for people whose attendance has actually been confirmed.
  • Organisers can rename event channels to match the job, such as Door team or Afterparty chat, without changing the underlying audience rule.
  • Use Event -> Admin -> Chat when you need to manage the live event channel roster over time.
  • Event chat appears once the event has at least one active event channel, and it disappears from the event page again when there are no active event channels left.
  • If you disable one event channel on purpose, you can restore it later from Event -> Admin -> Chat.
  • Use event updates for organiser announcements. Event chat no longer includes a separate event announcements channel.

When Notifications Fail

  1. Confirm browser notification permission is Allowed.
  2. Run push repair in Notification Delivery.
  3. Confirm topic-level delivery preferences are enabled.
  4. Check blockers/extensions/shields.
  5. 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.
Last updated on
Purchases and RefundsPhotos and Privacy