FIGR / UI TEMPLATE

Team Chat

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.

Team Chat

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Inbox

Primary action

New message

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

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.

What to look for

  • Primary action: New message is clearly available where the task happens.
  • Main view: Channels keeps the starting point obvious.
  • Connected view: Direct messages supplies nearby context.
  • Metric: Unread is visible with a meaningful value.
  • Another signal: Channels helps people judge what to do next.
  • Representative record: # product-launch makes the example specific.
  • Second record: # design-system shows the pattern works beyond one item.

States to consider

  • Inbox empty after filters; show what people can do instead of leaving a blank panel.
  • Loading channels without changing the layout unexpectedly.
  • Attachment or reply failed; explain the problem and preserve work.
  • Permission denied for direct messages; clarify who can continue.
  • Success after choosing New message; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where it fits

Channels → Direct messages → New message → Review outcome

Patterns in this screen

Inbox, Channels, Direct messages, Mentions, accessible states, contextual actions

UX choices to review

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.

Try a similar screen in Figr

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.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗