Section 4 · Nutshell — Turn 30,000 Records Into an Asset
4.7Human activity feeds back to AI
Designed for Phase 2- No.
- 4.7
- DMA's reference
- Decision Book p.15
- Phase
- Phase 2
- Autonomy
- L3 · Act within rules
- DMA's decision
- Yes
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.15
When a rep calls or emails someone, that becomes part of the AI's context next time.
Why it matters to DMA: It keeps the AI's picture of an account current, not stale from the last AI-only touch.
In our words, from DMA's Product Decision Book v3, page 15.
How we do it
- DMA's book schedules this for Phase 2 and asks for rep activity to be pulled in on the same cadence as everything else.
- Much of it runs already: anything a rep logs in Nutshell (notes, activities, tasks, stage changes) reaches the mirror within seconds, and a change re-reviews and re-scores that account.
- Phase 2 adds activity that never reaches Nutshell today: the reps' own email and phone systems, with the logging discipline the book mentions.
Already in place
- Rep notes, activities, tasks and stage changes in Nutshell reach the mirror within seconds and trigger a re-score of that account.
- Calls logged through the team workspace (Zoom transcripts) are already read and written back.
What the later phase adds
- Connectors for the reps' email and phone systems.
- A "last human touch" signal in the score and the brief.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
A rep acts
A call, an email, a note.
- Person
- Stored data
- AI
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Rep activity
Source
Nutshell today; email and phone in Phase 2.
- 2Sync
Copies Nutshell changes into the bridge database
Mirrors Nutshell activity within seconds.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
Activities and notes on the account.
- 4AI
Claude models, only through DMA's own gateway
Re-reviews the account.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved.
- 6Nutshell
The system of record
Where reps log today.
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 |
|---|---|---|
| crm.activities | Mirrored Nutshell activities. | 21 |
Worked example
Synthetic demo data: every name, business and number is made up.
Designed behaviour (synthetic).
After a rep's call
- Logged in Nutshell
- Call with Dana, 10 minutes, "wants a proposal"
- In the AI's next brief
- Last human touch: yesterday, a call; Dana asked for a proposal
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.