Outcome. Contacts with no linked company are flagged and queued for a rep to fix, instead of quietly skewing company-level reporting and account-based routing.
flowchart TD
A[Contact created, or association changed] --> B{Has associated company?}
B -->|no| C[Flag: Missing]
C --> D[Add to list + create task]
B -->|yes| E[Flag: Resolved]

When to use it, when not to
- UseUse it when reps create contacts manually without linking a company, or when an import process leaves the association blank.
- UseUse it as a lightweight, native alternative to data-quality-006 when the portal does not have Operations Hub, or when a purely detect-and-queue approach is enough without automatic domain matching.
- SkipDo not use it on portals where most contacts are genuinely personal, with no company to link (consumer-facing businesses). The flag will fire on nearly every record and the queue becomes noise.
- SkipDo not use it expecting an automatic fix. This workflow only flags the record and creates a task; a human still has to search for and attach the right company. See data-quality-006 for the automated match, which needs Operations Hub Professional.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





