Weekly Sales Briefing
98 leads in, 0 site visits done, 0 bookings — and the pipeline is 57% RNR.
Week of Thu 14 – Tue 19 Aug 2026 · window Thu 14 00:00 → Wed 20 00:00 IST · Sales team: Biki & Vishnu Raj (+ AI broker) · every number verified against the live CRM
Two views below. Part A — where we stand: a 484-lead live pipeline of which 278 (57%) are RNR — people worked repeatedly who won't pick up — and 323 are past SLA. All-time bookings: 10. Part B — this week: 349 human calls + 323 AI calls, 98 new leads, 7 leads advanced toward a site visit, but 0 site visits completed and 0 bookings. The backward-move count looks bad (110 vs 55 forward) but 90 of those are junk being disqualified on arrival, not deals lost.
0
site visits done · bookings
323
AI-broker calls this week
📋 How to read this — definitions
An SLA is the maximum time a lead should sit before it's acted on. Two clocks:
Dwell (RNR / funnel statuses): time parked in the status. Breach = stuck too long.
Cadence (Nurture): time since the last touch. Breach = missed the keep-warm rhythm.
- RNR — "Ringing, No Response": dialed, didn't pick up. Split by where in the journey the lead went cold.
- Attempts / touches — every logged contact (call + note + WhatsApp). Manual calls are typed as notes, so this counts all real outreach.
- Blind push — a follow-up date moved forward with zero contact that day. Hides the lead from the queue without working it.
- AI-broker pool — breached + still actively dialed (last attempt ≤14 days) + heavily attempted (≥8). The human number is saturated; the AI broker retries from a fresh number.
- This week — Thu 14 Aug 00:00 to Wed 20 Aug 00:00 IST (six days: Thu 14 → Tue 19). Live snapshot figures are current state, not windowed.
Part A · Where we stand — live pipeline (all-time state)
1The whole book
Every lead ever created, by outcome. This is the standing state, independent of this week.
| Bucket | Leads | Share |
|---|
| Live (in play) | 484 | 29% |
| Booked (all-time) | 10 | 1% |
| Dead (Lost / Not Qualified / Duplicate) | 1,200 | 71% |
| Total | 1,694 | 100% |
10 bookings from 1,694 leads is the conversion baseline to hold in your head. 71% of everything ever created is dead — most of it disqualified junk (see Part B, section 9). The live 484 is the only pipeline that matters, and section 2 shows it's clogged.
2Live funnel — where the 484 sit
278 of 484 (57%) live leads are in an RNR status — worked, not answering. Booking excluded (it's an outcome, not a stage).
The RNR wall. 141 never got a first touch answered, 106 went cold after connecting once. More than half the "live" pipeline is stalled on contactability, not on interest. This is the single structural fact of the sales team — and the reason the AI broker exists (sections 5 & 8).
3SLA breaches — overdue, and who's neglected vs unreachable
323 of 484 live leads are past their SLA. But two very different failures hide inside that number.
| Status | Breached | Called (no answer) | Worked, no call | Never touched |
|---|
| RNR — After Connected | 100 | 99 | 1 | 0 |
| RNR — Before First Touch | 99 | 89 | 7 | 3 |
| Nurture — Monthly | 59 | 4 | 27 | 28 |
| Connected | 19 | 13 | 1 | 5 |
| Nurture — Weekly | 18 | 11 | 5 | 2 |
| RNR — After Details Sent | 13 | 11 | 2 | 0 |
| Others (5 statuses) | 15 | 11 | 3 | 4 |
| Total | 323 | 226 | 46 | 51 |
Two problems, two fixes. The RNR breaches (200+) are "called, no answer" — effort was spent, the number just won't connect → route to AI (section 5). But Nurture — Monthly is genuine neglect: 55 of 59 were never called (27 worked-by-note-only + 28 untouched). That's recoverable pipeline quietly rotting. Same for the 5 untouched "Connected" leads — those had already picked up once.
4AI-broker hand-off pool
69
leads where the human phone number is saturated
Each is breached, still being dialed 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 live.
| Status | Pool | Avg attempts | Avg days since last |
|---|
| RNR — After Connected | 37 | 11.8 | 7.6 |
| RNR — Before First Touch | 27 | 9.6 | 8.7 |
| RNR — After Details Sent | 4 | 19.3 | 7.1 |
| Nurture — Weekly | 1 | 17.0 | 7.6 |
| Total → AI broker | 69 | — | — |
RNR — After Details Sent averages 19.3 attempts per lead. Those numbers are completely burned for the human team — stop spending rep hours on them.
Part B · This week — activity Thu 14 → Tue 19 Aug
5Effort scorecard — human reps
Calls placed, calls connected, and distinct leads touched this week.
| Rep | Calls | Connected | Connect % | WhatsApp | Leads touched |
|---|
| Vishnu Raj | 178 | 78 | 44% | 27 | 146 |
| Biki | 171 | 31 | 18% | 3 | 113 |
| Total | 349 | 109 | 31% | 30 | — |
Near-identical call volume, opposite connect rates (Vishnu 44% vs Biki 18%). Don't read this as skill alone — connect rate is heavily driven by which lead lists and what call hours each rep worked, which differ. The action is investigate why (same cohorts? same time-of-day?), not "Biki is worse." Vishnu also sent 27 WhatsApps to Biki's 3.
6AI broker this week — DAIT Caller
What the AI broker did in the six-day window, carrying the brute-force dialing load off the humans.
| Metric | Value |
|---|
| Calls placed | 323 |
| Distinct leads worked | 81 |
| Connected | 57 |
| RNR (no answer) | 258 |
| Busy / switched off | 8 |
| Callbacks booked | 0 |
The AI made 323 calls across 81 leads and got 57 connects — nearly matching the two humans' combined call volume on its own. 0 callbacks is the number to watch: it's connecting but not yet converting those connects into scheduled next-steps.
7Inflow — where this week's 98 leads came from
New leads created in the window, by source.
69% of inflow is Meta/FB (68 of 98). Sachi WhatsApp is now the #2 source at 19 — a real second channel. Google is thin at 7. Heavy single-channel dependence on Meta; see section 9 for the quality cost of that channel.
8Lead movement this week
199 real status moves (plus 98 new-lead creations). Direction split below.
110
backward (incl. 90 lost)
| Top transitions this week | Leads |
|---|
| New → Not Qualified — Junk | 54 |
| New → RNR — Before First Touch | 25 |
| RNR — Before First Touch → Not Qualified — Junk | 11 |
| Requirement Gathered → Details Sent | 6 |
| New → Connected | 6 |
| Details Sent → RNR — After Details Sent | 6 |
| New → Details Sent | 5 |
| Connected → Lost — Not Interested | 4 |
Read the backward number carefully. 110 backward > 55 forward looks like collapse, but 90 of the 110 are junk being disqualified on arrival (54 New→NQ-Junk + 11 RNR→NQ + more) — that's pipeline hygiene, not deals lost. Genuine losses this week: ~4 (Connected → Lost — Not Interested). The 54 junk-on-arrival is a lead-quality signal on the Meta channel, worth a look for Atul.
9Follow-up discipline — worked vs blind
Follow-up dates pushed this week, split by whether the lead got any contact that day. Blind = date moved with zero contact.
Pushed with a touch
Blind — no contact
~40% of all follow-ups this week were blind date-pushes — the CRM shows activity that didn't happen. Vishnu pushed 59 of 123 blind (48%), Biki 36 of 117 (31%). Note this is the inverse of the connect-rate story: Vishnu reaches more people on the phone but clears more follow-ups without contact. Pushing a date without working the lead just hides it from the queue.
10The honest output — bottom of funnel
Where leads actually advanced this week. This is the number that matters most.
| Advanced to | Leads this week |
|---|
| Site Visit Interested | 4 |
| Site Visit Scheduled | 3 |
| Site Visit Done | 0 |
| Booking Done | 0 |
Six days, 672 total calls (349 human + 323 AI), 98 new leads — and 7 leads moved toward a site visit but none completed one, and nothing booked. Read alongside Part A: the pipeline isn't idle, it's stalled on contactability and on converting connects into visits. Turning the 7 site-visit-interested into completed visits is next week's single most important job.