Section 20 · Sales Rep Work Elimination / Zero-Entry CRM
20.16Salesperson promise detection
Built in the POC- No.
- 20.16
- DMA's reference
- Decision Book p.39
- Phase
- Phase 1
- Autonomy
- L2 · Prepare, then wait for approval
- DMA's decision
- Yes
What DMA asked for · Decision Book p.39
Catch what our own rep promised on a call.
Why it matters to DMA: DMA's promises are the ones a prospect remembers when they aren't kept.
In our words, from DMA's Product Decision Book v3, page 39.
How we do it
- Each commitment is marked with who made it. DMA's own promises become tasks for the rep, dated from the words used.
- The quote stays with the task, so the rep sees exactly what they said.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Said
Tom promises the proposal by Tuesday.
- Person
- AI
- Nutshell
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Call transcript
Source
A call transcript: pasted, or a Zoom .vtt / .txt file dropped on the account (text only, 512 KB at most).
- 2Sync
Copies Nutshell changes into the bridge database
Reads the account, people and open deals from the mirror, to match the call to the right company.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The run, the facts with their quotes and the e-mail draft are stored; the transcript is kept encrypted.
- 4AI
Claude models, only through DMA's own gateway
The fast model reads the call and copies exact words; code checks every quote, date and amount. The conversation model drafts the follow-up.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Every change waits as one batch for one approval, then leaves through the write gate with 30 seconds to undo.
- 6Nutshell
The system of record
The note, the tasks and the fields appear on the deal, marked as written by DMA AI.
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.tasks | Nutshell's tasks, mirrored; ones the AI proposed are marked. | 18 |
| ai.scribe_runs | One row per logged call: the transcript's fingerprint, the account it matched, the extraction and the approval batch it produced. | 24 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ai.scribe_runs.conversation_id | conv.conversations | The database (foreign key) |
| ai.scribe_runs.approval_id | ctrl.approvals | The database (foreign key) |
Worked example
Synthetic demo data: every name, business and number is made up.
DMA's promise on the Summit HVAC call.
The promise
- Said
- "I'll send you a proposal for PPC and local listings by Tuesday, month to month."
- Task
- Send proposal for PPC and local listings, due Tuesday 29 September (95% sure)
In the running POC
The CRM updates from one logged call, waiting for one-click approval (a real run on synthetic data).
- 1The note; DMA's promise is the first task below it, with Tom's words.
- 2The follow-up e-mail, drafted and claim-checked; approving saves it, it never sends.
- 3One click approves the whole batch; each line can also be edited or dropped.
Dashboard · Approvals, the CRM updates from one call transcript. 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 |
|---|---|---|
| Accounts → Log a call | DMA AI dashboard | Open an account and paste or drop a Zoom transcript. |
Status
Built in the POC. This capability runs in the POC today, on synthetic data, end to end.