Skip to main content
Managers create named group chats on a gig. Crew with the app chat on mobile, managers chat on web or mobile, and crew without the app take part by text message. Read the QA testing guide before you start, and see Chat for how the feature works.

At a glance

Before you start

  • An org with the flag on. If the gig has no Chats section, confirm with the QA lead that the org has event-chats.
  • A published gig. Use an active gig, not a draft, that is not the sample gig. Crew who are only invited cannot open a draft gig.
  • Staffed crew. At least two crew members who accepted, each signed in to the app on their own device.
  • For the text message checks: one crew member with a real mobile number and no Soundcheck account.
  • Two devices or two browsers at once for any check where one person sends and another receives.
Chat sends pushes and texts to real people. Add only test accounts and test phone numbers to a test chat.

Where chats live

  • Crew on mobile: the gig’s Chats section. Crew with no chats on the gig do not see the section.
  • Managers on mobile: the gig’s More → Chats.
  • Web: the gig’s Chats tab, and the Chats button in the work dock.

In scope

Create and manage chats

Messages

Mentions

Pins

Read receipts and status

Unread and scrolling

Notification settings

Text message crew

These checks need a real phone that receives texts, on an environment whose text-message number pool is approved for sending. Ask the QA lead which environment that is before you start.

Push notifications

These checks need a real phone or a simulator that receives pushes, and two accounts.

Out of scope

Do not file these as bugs. They are not built yet.
  • Direct messages between two people.
  • @crew, @here, or department mentions.
  • Sending PDFs or other files in chat. Use the gig’s Files.
  • Managers deleting other people’s messages.
  • Reactions, edits, mutes, or pins over text message (ENG-2032, ENG-2041).
  • Hiding read receipts for an org (ENG-2038).
  • A chat list for chat members who are not on the gig, and opening a chat by link on web (ENG-1956).
  • Link previews and links for street addresses.
  • Search across chats, a chat made for every gig automatically, CheckAI replies in a chat, and sending while offline.
  • An app icon badge for unread chats.
  • Picture messages to phones. The event-chat-mms flag is off, so phones get a “photo was shared” text instead.

Known limitations

  • The @ mark in the chat list updates only when the list reloads.
  • The New messages divider sits on the oldest loaded message when more than 30 are unread.
  • Add newly staffed crew also offers people who left or were removed from the all-crew chat.
  • The all-crew chat does not follow staffing changes on its own. A manager adds new crew with the button.
  • The existing Chat feature page is the reference for how chat behaves. Where this plan and that page disagree, this plan is newer. Report the gap to the QA lead.

For agents

  • Deep links: soundcheck://events/<eventId>/chats/<chatId> opens a chat inside its gig. soundcheck://chat/<chatId> opens a chat by its ID.
  • Two-account checks need two simulators, one signed in with npm run sim:e2e-login -- --as user and the other with --as member. See the agent runbook.
  • API: routes for creating, renaming, archiving, adding and removing members, and pinning return 403 for crew in the org and 404 for people outside it. With the flag off, chat routes return 404 FEATURE_DISABLED. List operations with npm run api -- ops chat.
  • The local emulator has no photos, no real texts, and no webhooks. Run photo and text checks on a hosted environment.
  • Push type: event_chat_message.
  • Analytics (PostHog): server events event_chat_created, event_chat_updated, event_chat_notifications_updated, event_chat_reaction_added, event_chat_message_updated, and event_chat_message_deleted. Mobile and web send event_chat_viewed, event_chat_message_sent, and event_chat_message_failed. Mobile also sends event_chat_seen_by_opened. Properties are in docs/engineering/reference/analytics-taxonomy.mdx in the repository.