Outreach: Leads Inbox

By Summit53 Team

Overview

The Leads page is the default view in the Outreach section (/outreach/leads). It is your leads inbox: a single place to work manual prospect leads inside Summit53, bulk-enrol them into email sequences, and convert the qualified ones into CRM records. Because leads live inside the Revenue Engine, the full engagement history travels with a lead when it converts to a pipeline opportunity.

The header gives you five quick actions: Connect Gmail, Add Lead, Import Leads, Refresh, and Acquisition Overview.

Card and Table views

Two layouts share the same data, toggled with the Card view and Table view buttons. Your choice is remembered in the browser between visits.

  • Card view โ€” a Kanban-style board grouped by stage. It focuses on active leads and excludes Converted, Archived, Bounced, and Unsubscribed leads. If the board hits its display cap, a warning banner appears so you know results are limited.
  • Table view โ€” a paginated table with columns for Lead, Owner, Status, Stage, Fit, Tier, Activity / Next Action, and Actions.

Status and Stage

Each lead carries two separate fields. Status reflects engagement state; Stage reflects where the lead sits in your qualification or touchpoint cadence.

Status

The available statuses are:

  • New โ€” added but not yet worked
  • Working โ€” outreach is active
  • Engaged โ€” a positive signal (open, click, profile view) without a reply
  • Replied โ€” the lead has responded
  • Converted โ€” promoted to a CRM opportunity
  • Bounced โ€” an email bounced
  • Unsubscribed โ€” the lead opted out
  • Archived โ€” removed from active work

Stage

Stage values are Prospect, Qualifying, Nurturing, Ready, and the touchpoint stages T0 through T7. In Card view, leads are grouped into columns by their stage value.

Fit, Tier, and Touchpoint Stage

  • Fit rating โ€” how well the lead matches your ICP: Strong, Good, Moderate, or Weak.
  • Tier โ€” outreach priority: Tier 1, Tier 2, or Tier 3.
  • Touchpoint stage โ€” relationship warmth: Cold, Warming, Engaged, or Hot.

Filtering and follow-up

A row of follow-up tabs sits above the list: All, Overdue, Due today, Due this week, and No date, each showing a live count so you can triage by what needs action.

The filter bar offers:

  • Search โ€” match by name, company, or email
  • Status โ€” filter to a single status
  • Owner โ€” filter by the rep who owns the lead
  • More โ€” reveals additional filters for Stage, Tier, and Fit rating

Activity and next action

Each lead shows a compact activity summary (for example, "6 sent ยท 2 replies ยท 3 clicks") alongside its next action and due date. Next action types are Email, LinkedIn Connect, LinkedIn Message, Call, Research, Follow Up, and None. Overdue actions are badged so they stand out.

Per-lead row actions are:

  • Draft โ€” open the draft review panel for an AI-prepared message (see below)
  • Done โ€” mark the current next action complete
  • Snooze โ€” push the next action date out
  • Convert โ€” promote the lead to a CRM opportunity

Gmail reply review

Connect a Gmail account with Connect Gmail to bring replies into Summit53. When Google-sourced replies arrive, a banner reports how many need review. The Draft action opens a review panel showing an AI-generated reply draft, with a grounded-by footer listing the knowledge assets used to write it. From there you can review the draft and Mark reviewed before sending.

Bulk actions

Select multiple leads to apply an action across all of them:

  • Enroll in sequence
  • Assign owner
  • Set status
  • Set stage
  • Set next action
  • Set fit rating
  • Set tier
  • Archive

Adding leads manually

Use Add Lead to enter a single lead by hand โ€” useful for referrals or conference contacts. The form captures contact details plus Stage, Fit rating, Tier, and Touchpoint stage. For lists, use Import Leads instead.

Converting to a CRM opportunity

When a lead qualifies, Convert creates a CRM opportunity and carries over the contact details, company, engagement history, and qualification fields. This is the handoff where Acquisition meets Pipeline โ€” no context is lost.