Section 20 · Sales Rep Work Elimination / Zero-Entry CRM

20.15Automatic task creation

Built in the POC

What DMA asked for · Decision Book p.39

Create the tasks reps should have, without them typing.

Why it matters to DMA: A deal with no next task is a deal nobody is working.

In our words, from DMA's Product Decision Book v3, page 39.

Tasks come from promises on calls (20.4), each with a due date worked out from the meeting date.
Open deals with no open task are flagged by the hygiene rules (20.23), so the gaps are visible even where no call was logged.
A task is written to Nutshell only after the batch is approved.

It plays on its own while it's on screen; hover or use the controls to pause or step through.

Step 1 of 4

A promise

"I'll send you a proposal by Tuesday."

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.

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
ctrl.outbox	The write gate: each proposed Nutshell change, its approval and what it replaced.	28
ai.hygiene_flags	Data-quality flags found by rules (duplicate, stuck deal, missing next step, bad e-mail, former owner…).	10

How the tables connect (1)

Column	Points to	Kept by
ctrl.outbox.approval_id	ctrl.approvals	The database (foreign key)

Synthetic demo data: every name, business and number is made up.

Tasks from the Summit HVAC call.

Who promised	Task	Due	Sure
DMA (Tom)	Send proposal for PPC and local listings	Tuesday 29 September	95%
Prospect (Greg)	Follow up: Greg Hollis to provide access to Google Ads account	Friday 25 September	95%

localhost:13301/approvals

The CRM updates from one logged call, waiting for one-click approval (a real run on synthetic data).

1The note; the proposed tasks follow, each with its quote and due date.
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.

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.
Pipeline hygiene: no next step	DMA AI dashboard	Open deals with no open task.

Built in the POC

Built in the POC. This capability runs in the POC today, on synthetic data, end to end.