Section 7 · Next Best Action for Every Lead
7.3Rep-specific priority list
Built in the POC- No.
- 7.3
- DMA's reference
- Decision Book p.19
- Phase
- Phase 1
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
What DMA asked for · Decision Book p.19
Each salesperson starts the day with the accounts most worth their time.
Why it matters to DMA: It makes every rep more productive without adding people.
In our words, from DMA's Product Decision Book v3, page 19.
How we do it
- A rep signs in to the dashboard or the team workspace with their own account, linked to their Nutshell user.
- The database itself limits what a rep can see to the accounts they own in Nutshell, and everything attached to them. This is enforced in the database, not in the screen, so no question or tool can reach another rep's accounts.
- So the same Today list becomes each rep's own list: their revivable accounts in the same ranking order, each with its reason and one next action. In the team workspace, "what should I work on today?" returns the same list.
- Owners, the president and managers see every account.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
A rep signs in
With their own login, linked to their Nutshell user.
- Person
- Rule in code
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Nutshell owners
Source
Who owns each account in Nutshell.
- 2Sync
Copies Nutshell changes into the bridge database
Keeps ownership current in the mirror.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
Row-level rules limit every read to the rep's own accounts.
- 4AI
Claude models, only through DMA's own gateway
Not involved in building the list.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved: the list only reads.
- 6Nutshell
The system of record
Ownership stays managed in Nutshell.
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.scores | Scores and actions; reads are limited to the rep's own accounts. | 20 |
| ai.account_twin | Each account's picture, under the same scope. | 16 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ai.scores.prompt_id | agent.prompts | The application (by id) |
| ai.account_twin.prompt_id | agent.prompts | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
Two synthetic reps and their own top accounts from the same run.
Same run, two lists
| Rep | Their top account | Next action |
|---|---|---|
| Tom Alvarez | Briivo Pet Grooming Franchising | Resurrection email to Dalia |
| Jenna Walsh | Zenara Kids Gym Franchising | Follow-up email to Rosa |
In the running POC
Today: the list a rep sees is the same screen, scoped to the accounts they own.
- 1Each account's reason.
- 2The one next action.
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 | Sign in as a rep to see only their accounts. |
Status
Built in the POC. This capability runs in the POC today, on synthetic data, end to end.