Sales Activity

Track calls, emails, meetings, and follow-ups against pipeline movement without turning activity into vanity metrics. The screen connects Activity and Calls so sales teams can find the “Log activity” action while checking calls and meetings.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Northstar Labs · call and Kinetic Cloud · email, rather than an empty visual shell.

Sales Activity
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Log activity

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Sales teams need a clear “Log activity” action without losing sight of calls, meetings and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Log activity is clearly available where the task happens.
  • Main view: Activity keeps the starting point obvious.
  • Connected view: Calls supplies nearby context.
  • Metric: Calls is visible with a meaningful value.
  • Another signal: Meetings helps people judge what to do next.
  • Representative record: Northstar Labs · call makes the example specific.
  • Second record: Kinetic Cloud · email shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading activity without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for calls; clarify who can continue.
  • Success after choosing Log activity; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Activity → Calls → Log activity → Review outcome

Patterns used

Analytics, Activity, Calls, Email, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Northstar Labs · call with Kinetic Cloud · email. Make calls clear, then use meetings 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 “Log activity” action. The happy path alone is not enough.

Related UI examples: Quote Builder, Revenue Operations, Territory Management.

Start from this in Figr

Design a sales activity screen for our existing software product. Use our real design-system tokens, components and product language. Show Activity and Calls, include believable records such as Northstar Labs · call, and make log activity easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr