Daily Sales Briefing

The pipeline is mostly stuck. Here's what to hand off.

Fri 15 Aug 2026 ยท Sales team: Biki & Vishnu Raj ยท pipeline health is a live snapshot; activity is today so far
217 of 276 live RNR leads are past their 14-day SLA โ€” worked an average of 7.8 times each and still not answering. 77 of those have saturated the human phone number (8+ attempts, still being dialed): hand them to the AI broker on a fresh number. Nurture has 30 quiet leads with no recent touch. Below: the health snapshot, then today's calls and moves.

๐Ÿ“‹ How to read this โ€” SLA definitions

An SLA is the maximum time a lead should sit before it's acted on. Two clocks:

Dwell (RNR statuses): time parked in the status. Breach = stuck too long.
Cadence (Nurture): time since the last touch. Breach = missed the keep-warm rhythm โ€” total time in nurture is fine as long as it's touched on schedule.

StatusClockLimit
RNR โ€” Before First Touchdwell14 days
RNR โ€” After Connecteddwell14 days
RNR โ€” After Details Sentdwell14 days
RNR โ€” After Scheduling Visitdwell14 days
RNR โ€” After Site Visitdwell14 days
Nurture โ€” Weeklycadence1 touch / 7 days
Nurture โ€” Monthlycadence1 touch / 30 days
Part A ยท Pipeline health โ€” live snapshot

1RNR โ€” worked hard, not answering

217 of 276 live RNR leads are over their 14-day SLA. Every one was called repeatedly and still went cold.
RNR statusLiveBreachedAvg attemptsWorst dwell
After Connected1091008.9245d
Before First Touch1361006.4179d
After Details Sent251311.8182d
After Site Visit433.3247d
After Scheduling Visit216.058d
Total2762177.8โ€”
Across all 217 breached RNR leads, humans averaged 7.8 attempts each (median 7). This is not neglect โ€” the numbers are worked to exhaustion. The question is not "call more," it's "which channel next."

2Nurture โ€” cadence discipline

70 of 113 live Nurture leads are past their touch-cadence SLA. Split by whether they're still being worked.
Nurture statusLiveBreachedActive (overdue)Quiet (no activity)Worst gap
Monthly89562729155d
Weekly2414131122d
Total113704030โ€”
40 active โ€” being touched, just overdue โ†’ nudge the cadence. 30 quiet โ€” no activity since entering nurture โ†’ dropped, and good candidates to reassign or automate.

3AI-broker hand-off pool

77
leads where the human phone number is saturated
Each of these is breached, still being dialed (last attempt ~5 days ago) and hit 8+ times from the human number. The lead won't pick up that number anymore. The AI broker calls from a fresh number โ€” a real second shot, while the lead is still active.
StatusPoolAvg attemptsAvg days since last
RNR โ€” After Connected4511.25.1
RNR โ€” Before First Touch279.64.3
RNR โ€” After Details Sent419.04.2
Nurture โ€” Weekly112.012.1
Total โ†’ AI broker77โ€”โ€”
RNR โ€” After Details Sent averages 19 attempts per lead. Those numbers are completely burned for the human team.
Part B ยท Daily activity โ€” Fri 15 Aug, as of now

4Follow-up discipline

Follow-up dates pushed today, split by whether the lead got any contact. Blind = date moved with zero contact.
Pushed with a touch Blind โ€” no contact
Vishnu pushed 39 of 49 follow-ups blind today โ€” dates moved forward with no call, note or message. Biki blind on 36 of 97. Pushing a date without contact just hides the lead from the queue.

5Lead movement โ€” worked today, where it went

Left = the status each lead was in at the start of today (with how many worked). Right = where it ended up. Arrow number = leads on that path. No arrow = stayed put.
moved forward moved backward lost / junk
Sources: every number traces to a saved, verified script against the live CRM โ€” status_sla.py (RNR, Nurture, AI-broker pool), followup_discipline.py (follow-ups), and status-history queries (movement). Pipeline health = live snapshot at load. Activity = 15 Aug up to now.