Message Search

Search conversations across channels and direct messages with filters for sender, date, attachments, and workspace. This example brings All messages and People together so team members can find the next task without losing context.

It includes representative records such as Launch plan decision and Pricing feedback thread. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Use this template in Figr

Template facts

Screen

Primary action

Save search

Pattern

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to save search while keeping results, channels and exceptions visible. The interface should show what changed and who should act next.

Key elements

Main workspace: All messages gives users an obvious place to start.
Supporting view: People keeps the related context close.
Primary action: Save search stays visible when people need it.
First signal: Results shows a useful value (342).
Second signal: Channels gives additional context (16).
Sample record: Launch plan decision.
Next record: Pricing feedback thread.

States worth designing

No results: say what changed, protect progress, and offer a clear next step.
Filters return zero matches: say what changed, protect progress, and offer a clear next step.
Search taking longer: say what changed, protect progress, and offer a clear next step.
Results unavailable: say what changed, protect progress, and offer a clear next step.
Saved search ready: say what changed, protect progress, and offer a clear next step.
Restricted content omitted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

All messages → People → Save search → Review outcome

Patterns used

Search, All messages, People, contextual actions, error recovery

Why these choices work

Preserve query and filters when moving into results. Suggest useful recovery when the search returns nothing.

Pay attention to all messages and people. People need to distinguish Launch plan decision from Pricing feedback thread. Keep results visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Save search”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Channel Directory, Announcement Composer, Direct Messages.

Start from this in Figr

Design a message search screen inside our existing product. Use our current components, tokens and content language. Include All messages and People views, credible records like Launch plan decision, and a clear “Save search” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr