Section 5 · Reactivate Old Leads Now
5.4Forgotten-lead rescue
Built in the POC- No.
- 5.4
- DMA's reference
- Decision Book p.16
- Phase
- Phase 1
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
What DMA asked for · Decision Book p.16
Find strong leads that simply stopped getting follow-up.
Why it matters to DMA: Pure process-failure recovery: leads DMA had already earned and then dropped.
In our words, from DMA's Product Decision Book v3, page 16.
How we do it
- An open lead with no activity for 180 days or more is recognised as forgotten. The AI reads its notes to separate real buyers from vendors, job seekers and spam, and anything it calls junk must quote the evidence.
- Forgotten leads that are real buyers are scored like any other record and join the reactivation list as the "rescue" segment, with what was last said.
- Stuck deals and deals without a next step are also flagged for the team, so the leads that are still open don't become the next forgotten ones.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Gone quiet
An open lead with no activity since last spring.
- Nutshell
- AI
- Rule in code
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Open leads
Source
Leads with no recent activity.
- 2Sync
Copies Nutshell changes into the bridge database
Mirrors them.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The record type, junk evidence, the score.
- 4AI
Claude models, only through DMA's own gateway
Tells buyers from junk, with a quote.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
The next step to Nutshell.
- 6Nutshell
The system of record
The lead has an owner and a next step again.
The tables behind it
Drawn from the POC's database catalogue: structure only, no data.
PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)
| Table | What it holds | Columns |
|---|---|---|
| ai.account_twin | Each account's record type (lost deal, former client, forgotten lead) and next step. | 16 |
| tax.classifications | Lost reasons and churn reasons, each with its evidence. | 19 |
| ai.scores | The score, with the reason the record is revivable. | 20 |
How the tables connect (4)
| Column | Points to | Kept by |
|---|---|---|
| ai.account_twin.prompt_id | agent.prompts | The application (by id) |
| tax.classifications.node_id | tax.nodes | The database (foreign key) |
| tax.classifications.prompt_id | agent.prompts | The application (by id) |
| ai.scores.prompt_id | agent.prompts | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
Forgotten leads on Today
What you see
1.In the list with the rest
Rescued leads appear on Today with what was last said.

What happens in the system
- Rule engine
record typeOpen and quiet for 180 days or more: a forgotten lead; the AI's junk call needs a quote.
- Bridge database
ai.hygiene_flagsStuck deals and missing next steps flagged for the team.
The prototype's synthetic records by type.
Record types
| Type | Reactivation segment | Accounts |
|---|---|---|
| Forgotten lead | Rescue | 105 |
| Lost deal | Resurrection | 82 |
| Former client | Win-back | 48 |
| Open opportunity | None (sales is on it) | 45 |
| Not a buyer (test, vendor or job seeker) | None | 12 |
In the running POC

Today: rescued leads alongside the rest.
- 1The reason.
- 2The next step.
Dashboard · Today. Captured from the running POC on September 25, 2026; synthetic data.
See it live
Opens the exact screen in the running POC, in a new tab.
| Open | Where | What to try |
|---|---|---|
| Today | DMA AI dashboard | Rescue, win-back and resurrection accounts together. |
Status
Built in the POC. This capability runs in the POC today, on synthetic data, end to end.