Coordinate fast-moving team work in persistent channels with threads, mentions, files, and clear ownership. The screen connects Channels and Direct messages so product teams can find the “New message” action while checking unread and channels.
Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as # product-launch and # design-system, rather than an empty visual shell.
Inbox
New message
Inbox
Default, loading, empty, error, permission, success
Adaptable product UI theme
Product teams need a clear “New message” action without losing sight of unread, channels and the affected records. Keep the decision and its outcome clear before moving to the next task.
Channels → Direct messages → New message → Review outcome
Inbox, Channels, Direct messages, Mentions, accessible states, contextual actions
Keep the active record close to its history, owner and status. Make urgent items easy to find without hiding the rest.
In this design, people should be able to compare # product-launch with # design-system. Make unread clear, then use channels to explain whether the next step needs attention.
Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New message” action. The happy path alone is not enough.
Related UI examples: Clinical Inbox, Security Incidents, Alerting Center.
Design a team chat screen for our existing software product. Use our real design-system tokens, components and product language. Show Channels and Direct messages, include believable records such as # product-launch, and make new message easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.