Chapter 06

Dashboard and Runs

Single view of all outreach activity. Shows per-user data (each team member sees only their own runs, sends, and quota usage).

Last updated 27 May 2026

Dashboard

Single view of all outreach activity. Shows per-user data (each team member sees only their own runs, sends, and quota usage).

Date range dropdown

Top-right. Options:

  • This billing month — current calendar month, aligned to plan quota reset.
  • This week — Monday through today.
  • This month — 1st → today.
  • Last month — full previous calendar month.

Charts

Phase 2 Dashboard shows visual charts (bar/pie/spider) instead of tabular stats. Orange on dark background. Each chart represents:

  • Emails sent
  • LinkedIn connection requests (with/without note)
  • InMails sent
  • Prospects enriched
  • Searches run
  • Contacts pushed to CRM

Hover values; legend below each chart.

Recent runs table

Below the charts. Last 5 runs with status, type (email/LinkedIn), processed/skipped/errored counts, started-at timestamp. Click a row to open the run detail page.

Active run

When a run is in progress, a live progress bar appears at the top. Actions:

  • Pause — stops picking up new leads; in-flight sends complete then idle.
  • Resume — continue a paused run.
  • Cancel — permanently stop. Already-processed leads stay processed.

Run detail page

Click any row in Recent Runs (or History) to see per-lead details. Each lead line shows:

  • Lead name + company
  • Status: sent / skipped / errored
  • Reason (for skipped / errored)
  • Timestamp
  • For LinkedIn: the connection message sent
  • For Email: subject + snippet

History page

Separate page with ALL runs (not just recent 5). Sortable by date, filterable by type (email/LinkedIn) and status.

Usage vs quota

Dashboard also shows plan quota usage:

  • Used — count in the selected period.
  • Cap — plan's monthly quota. "— no cap —" for uncapped channels.
  • Remaining — how much is left before the next reset.

Quotas are per-user since Phase 2 — your teammates' sends don't eat into your cap. Each user on their assigned plan has their own quota bucket.