Enrichment: reverse IP-to-company lookup review queue

Outcome. Contacts a connected IP-to-company enrichment tool matches with low confidence get routed to a human check before the guessed company is treated as reliable, instead of a wrong or generic ISP match silently sitting on the record as if verified.

Workflow map Enrollment, branches and actions at a glance data-quality-043

flowchart TD
    A[IP-matched company candidate known] --> B[Delay 1 day]
    B --> C{IP match confidence}
    C -->|High| D[Confirmed]
    C -->|Medium or Low| E[Needs review + task]
    C -->|unknown| F[Not checked]

When to use it, when not to

• UseUse it when a connected reverse-IP or visitor-identification tool, a native integration or a third-party app, writes a candidate company name and a confidence indicator to contact properties, and a review step is wanted before that candidate feeds anything downstream, like a company auto-association.
• UseUse it as the review layer, not the lookup itself. HubSpot does not natively look up a company from an IP address inside a workflow; this fiche assumes a connected app already does that and writes the result to properties this workflow reads (check in your portal: confirm which connected integration in your portal writes an IP-based company candidate and to exactly which properties, naming and confidence-field format vary widely by vendor).
• SkipDo not use it to auto-associate the candidate company to the contact directly from this workflow. A low-confidence IP match is often a shared office, a VPN exit node, or an ISP, not the visitor's actual employer, so route it to a human rather than creating a wrong association automatically.
• SkipDo not use it if your enrichment vendor already exposes its own confidence-based review workflow inside its own app. Duplicating that logic here is redundant; use this fiche only if the vendor hands you a raw candidate with no built-in review step.