AI Chat Workspace

Work with an AI assistant in persistent conversations with files, sources, model context, history, and clear handoff between threads. This example brings Chats and Projects together so AI product teams can find the next task without losing context.

It includes representative records such as Launch positioning review and CRM redesign exploration. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

AI Chat Workspace
Use this template in Figr

Template facts

Screen

Inbox

Primary action

New chat

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new chat while keeping chats today, files attached and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Chats gives users an obvious place to start.
  • Supporting view: Projects keeps the related context close.
  • Primary action: New chat stays visible when people need it.
  • First signal: Chats today shows a useful value (18).
  • Second signal: Files attached gives additional context (12).
  • Sample record: Launch positioning review.
  • Next record: CRM redesign exploration.

States worth designing

  • No items match the selected filter: say what changed, protect progress, and offer a clear next step.
  • Message or task loading: say what changed, protect progress, and offer a clear next step.
  • Reply or assignment failed: say what changed, protect progress, and offer a clear next step.
  • Item resolved: say what changed, protect progress, and offer a clear next step.
  • Escalation required: say what changed, protect progress, and offer a clear next step.
  • Permission to read restricted content missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Chats → Projects → New chat → Review outcome

Patterns used

Inbox, Chats, Projects, contextual actions, error recovery

Why these choices work

Keep the current item close to its history, owner and urgency. Put the next action on the record rather than making people open several panels.

Pay attention to chats and projects. People need to distinguish Launch positioning review from CRM redesign exploration. Keep chats today 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 “New chat”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Agent Builder, Tool Connector Setup, Knowledge Source Manager.

Start from this in Figr

Design a ai chat workspace screen inside our existing product. Use our current components, tokens and content language. Include Chats and Projects views, credible records like Launch positioning review, and a clear “New chat” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr