FIGR / UI TEMPLATE

Lead Inbox

Triage inbound leads, see source and account context, and assign the next action without losing momentum. The screen connects Inbox and Leads so sales teams can find the “Assign lead” action while checking new leads and qualified.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Acme Systems · demo request and Northstar Labs · pricing page, rather than an empty visual shell.

Lead Inbox

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

Assign lead

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

Sales teams need a clear “Assign lead” action without losing sight of new leads, qualified and the affected records. Keep the decision and its outcome clear before moving to the next task.

What to look for

  • Primary action: Assign lead is clearly available where the task happens.
  • Main view: Inbox keeps the starting point obvious.
  • Connected view: Leads supplies nearby context.
  • Metric: New leads is visible with a meaningful value.
  • Another signal: Qualified helps people judge what to do next.
  • Representative record: Acme Systems · demo request makes the example specific.
  • Second record: Northstar Labs · pricing page 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 inbox without changing the layout unexpectedly.
  • Attachment or reply failed; explain the problem and preserve work.
  • Permission denied for leads; clarify who can continue.
  • Success after choosing Assign lead; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where it fits

Inbox → Leads → Assign lead → Review outcome

Patterns in this screen

Inbox, Inbox, Leads, Accounts, 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 Acme Systems · demo request with Northstar Labs · pricing page. Make new leads clear, then use qualified 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 “Assign lead” action. The happy path alone is not enough.

Related UI examples: Deal Pipeline, Account Detail, Contact Import.

Try a similar screen in Figr

Design a lead inbox screen for our existing software product. Use our real design-system tokens, components and product language. Show Inbox and Leads, include believable records such as Acme Systems · demo request, and make assign lead 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 ↗