Phone leads, in the portal

A clear path from first dial to closed deal.

What was broken

  1. Phone leads only lived inside the dialer.
  2. The Leads page was built for walking in the door.
  3. KPIs counted voicemail boxes as “connects”.

Call today, and why

Open Leads. The top list says who to call and why.

Overdue first. Tap Call and the dialer opens on that lead.

Call today, and why

Every lead has a stage

Newnever dialed
Attemptingno real talk yet
Connectedtalked, no next step
Callbackon the calendar
Setdemo booked
Demo heldnow close it
Wondeal closed

Moves happen from dialer outcomes, the calendar, and one-tap buttons. Lost: not interested, bad number, do-not-call.

Your pipeline at a glance

Counts per stage. Tap a lead for calls, notes and what they said.

In-person deals keep their own tab.

Your pipeline at a glance

Every callback goes on the calendar

No date and time, no save.

Times are the prospect’s local time.

A callback is a real path to a close.

Every callback goes on the calendar

Don't set wood

A set needs the decision maker, an agreed time, and why they want it — in their words.

Missing one? Make it a callback.

Don't set wood

KPIs you can read

Dials → pick-ups → conversations → callbacks → sets → demos held → closes.

Tap (i) for exactly what a number counts.

KPIs you can read

What the numbers mean

Pick-up
the line answered — a person, voicemail or phone menu.
Conversation
you talked to a person.
Set
a demo on the calendar, credited to the setter.
Close
a phone deal that went live.

Before this ships

  1. Merge + deploy? Backend goes live on merge; the portal needs a manual build.
  2. Apply the notes table? Optional — without it, notes save onto the lead.
  3. Leads opens on Phone leads for every rep — OK?
  4. Strict set gate: no “book anyway” button — OK?
  5. Switch the daily KPI email to pick-ups vs conversations?
  6. Team KPIs now stop at region lines — OK?
1 / 10