Section 20 · Sales Rep Work Elimination / Zero-Entry CRM
20.31End-of-day CRM cleanup
Designed for Phase 2- No.
- 20.31
- DMA's reference
- Decision Book p.42
- Phase
- Phase 2
- Autonomy
- L2 · Prepare, then wait for approval
- DMA's decision
- Yes
What DMA asked for · Decision Book p.42
At the end of the day, give each rep a short list to tidy their CRM.
Why it matters to DMA: Five minutes a day keeps the pipeline clean without a cleanup project.
In our words, from DMA's Product Decision Book v3, page 42.
How we do it
- Scheduled for Phase 2 in DMA's book.
- Each afternoon, one short list per rep: calls not logged, approvals waiting, their deals with no next step or gone stale. Each item is one click.
Already in place
- Pipeline hygiene, where a rep sees only their own book.
- Approvals with one-click batches (20.5).
What the later phase adds
- A daily list per rep, by e-mail or in the workspace.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Gathered
The rep's flags and waiting approvals.
- Stored data
- Screen
- Person
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Bridge database
Source
Flags and approvals.
- 2Sync
Copies Nutshell changes into the bridge database
Not involved.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The rep's open items.
- 4AI
Claude models, only through DMA's own gateway
No AI model is involved: rules decide.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Changes go through approvals as today.
- 6Nutshell
The system of record
Nutshell is not changed.
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.hygiene_flags | One open flag per record and problem (stuck deal, missing next step, former owner, bad email, duplicate), with severity, details and the rule version. | 10 |
| ctrl.approvals | The approval queue: one row per batch waiting for a person, with its risk and the undo window. | 22 |
Worked example
Synthetic demo data: every name, business and number is made up.
A designed example (synthetic).
Tom's list, 4:30 pm
- Waiting
- 1 call batch to approve
- No next step
- 2 deals
- Stale
- 1 deal idle 61 days
In the running POC
There is no screen for this one yet: it is designed for Phase 2, as DMA's book decides. The parts listed under “Already in place” run in the POC today.
Status
Designed for Phase 2. DMA's book schedules this for Phase 2. The design is ready and builds on parts that already run in the POC.