Call History

Review past calls with participants, duration, recording state, notes, and follow-up actions in a searchable history. This example brings All calls and Missed together so team members can find the next task without losing context.

It includes representative records such as Weekly product sync and Northstar customer call. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Call History
Use this template in Figr

Template facts

Screen

Table

Primary action

Start call

Pattern

Table

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to start call while keeping calls this week, recorded and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: All calls gives users an obvious place to start.
  • Supporting view: Missed keeps the related context close.
  • Primary action: Start call stays visible when people need it.
  • First signal: Calls this week shows a useful value (42).
  • Second signal: Recorded gives additional context (28).
  • Sample record: Weekly product sync.
  • Next record: Northstar customer call.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

All calls → Missed → Start call → Review outcome

Patterns used

Table, All calls, Missed, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to all calls and missed. People need to distinguish Weekly product sync from Northstar customer call. Keep calls this week 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 “Start call”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Video Meeting Lobby, Email Composer, Shared Inbox Rules.

Start from this in Figr

Design a call history screen inside our existing product. Use our current components, tokens and content language. Include All calls and Missed views, credible records like Weekly product sync, and a clear “Start call” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr