Section 10 · Human Sales Team Superpowers
10.2Hot-lead alerts
Built in the POC- No.
- 10.2
- DMA's reference
- Decision Book p.22
- Phase
- Phase 1
- Autonomy
- L3 · Act within rules
- DMA's decision
- Yes
What DMA asked for · Decision Book p.22
A high-value prospect immediately triggers an alert with the score, company, problem and recommended action.
Why it matters to DMA: Speed to lead is one of the strongest predictors of winning the deal.
In our words, from DMA's Product Decision Book v3, page 22.
How we do it
- When a visitor books a call, the host gets an email straight away: who booked and when, their company and site, the AI score and tier, the three fixes the AI shared, and a signed link that opens the live chat.
- When a visitor asks for a person, a case goes to whoever is on call on DMA's roster, by email, with a short brief. If they don't respond in time, it moves to the backup.
- Every alert goes through the send governor, so it is logged and obeys the email kill switch. Slack is available as an optional channel; DMA chooses.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
The visitor books
A real time in the booking card.
- Person
- Stored data
- Rule in code
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Website chat
Source
The booking, the review and the notes.
- 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 meeting, the score and the delivery log.
- 4AI
Claude models, only through DMA's own gateway
Not involved: the alert is assembled by code from stored facts.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
The lead goes to Nutshell through the write gate.
- 6Nutshell
The system of record
The lead carries the score and the review.
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 |
|---|---|---|
| ctrl.meetings | Each booked call: the time, the host and the conversation. | 16 |
| ctrl.mail_log | Every alert the governor sent or held. | 18 |
| ctrl.escalations | Cases for the person on call when a visitor asks for someone. | 33 |
How the tables connect (6)
| Column | Points to | Kept by |
|---|---|---|
| ctrl.meetings.conversation_id | conv.conversations | The application (by id) |
| ctrl.mail_log.approval_id | ctrl.approvals | The application (by id) |
| ctrl.mail_log.decision_id | ctrl.decision_log | The application (by id) |
| ctrl.escalations.conversation_id | conv.conversations | The application (by id) |
| ctrl.escalations.run_id | agent.runs | The application (by id) |
| ctrl.escalations.decision_id | ctrl.decision_log | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
The alert for a synthetic booking.
Hot lead: Dr. Maya Chen booked a call
- When
- Tuesday 29 September, 10:00 (Eastern)
- Company and site
- BrightSmile Dental · brightsmile-demo.test
- AI score
- 82 (tier A)
- The 3 fixes the AI shared
- Home page title; map links on the location pages; a 6 MB home page on phones
- Link
- Join the website chat (signed, opens the dashboard)
In the running POC
1 / 2The booking that triggers the alert: real times in the visitor's time zone.
- 1Open times.
- 2Name and email are asked only here, with consent recorded.
Website chat · booking card (not confirmed). 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 |
|---|---|---|
| Escalations | DMA AI dashboard | Cases routed to the person on call. |
| Escalation roster | DMA AI dashboard | Who gets each alert, the backup and the response time. |
Status
Built in the POC. This capability runs in the POC today, on synthetic data, end to end.