Confidential · © 2026 Space-O Technologies Inc. · Prepared exclusively for DMA. Please do not copy, save or share.

Part B · The screens

B.6Pipeline hygiene

What the data-quality rules found on the CRM copy: stuck deals, deals with no next step, records owned by people who left, contacts who left or bounced, and likely duplicates. People fix the records in Nutshell; a flag closes on the next run.

No.
B.6
Dashboard address
/hygiene

What you can do here

Each core task, and how many clicks it takes from this screen.

TaskClicksHow
See every open flag1Pipeline hygiene in the sidebar: highest severity first, with what each rule saw in words.
Show one kind of flag2Pipeline hygiene → the chip (Stuck deal, No next step, Former owner, Left or bounced, Possible duplicate).
Open the record behind a flag2Pipeline hygiene → the record's name: its Account 360.

How it works behind the scenes

  • The rules run with every review of the CRM and again after each sync. No AI model is involved in most flags: a stuck deal is 60 or more days with no activity, note or contact; a missing next step is an open deal with no open task; a former owner is a record owned by a disabled Nutshell user.
  • People who left or bounced come from the notes ("she has moved on", "mail returned"), quoted as evidence, and from the e-mail checks.
  • Likely duplicates compare company names and web domains, and people's names, e-mails and phones; the pair is shown with what matched. Merging is done by a person in Nutshell.
  • Each flag records the rule and its version, and is read as the signed-in person: a rep sees only their own records.
  • The screen is read-only: flags never change Nutshell.

Rules and switches that apply here

  • Severity is higher for late-stage deals (proposal, negotiation), so the list starts with the deals closest to money.
  • A flag closes by itself once the record is fixed in Nutshell and the next run no longer finds the problem.

The tables behind it

ai.hygiene_flagsPKiduuidsubject_typetextflag_codetextseveritytextdetailsjsonbrule_versiontextdetected_attimestampresolved_attimestamp+ 2 more columnsai.duplicate_candidatesPKiduuidentity_typetextscorenumericmatched_ontext[]statustext+ 5 more columns

PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)

TableWhat it holdsColumns
ai.hygiene_flagsOne open flag per record and problem (stuck deal, missing next step, former owner, bad email, duplicate), with severity, details and the rule version.10
ai.duplicate_candidatesPairs of records that look like the same company or person, with the score and what matched.10

The screen

localhost:13301/hygiene
Pipeline hygiene: every open flag (live counts, synthetic data).

1 / 3Pipeline hygiene: every open flag (live counts, synthetic data).

  1. 1One chip per kind of flag, with counts.
  2. 2The flag.
  3. 3What the rule saw, in words.

Dashboard · Pipeline hygiene, every open flag. Captured from the running POC on September 25, 2026; synthetic data.

Not yet

  • Fixes happen in Nutshell, by people: the screen detects and explains, it doesn't edit records.

See it live

Opens the screen in the running POC, in a new tab.

OpenWhereWhat to try
Pipeline hygieneDMA AI dashboardPick a chip; click a record for its Account 360.
B.6 Pipeline hygiene · DMA AI proof