Enrichment fallback task when third-party enrichment finds no match

Outcome. Contacts that a connected enrichment tool fails to match get a manual research task after a short grace period, instead of quietly staying incomplete because everyone assumed enrichment handled it.

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

flowchart TD
    A[Contact created, email known] --> B[Delay 2 days]
    B --> C{Success field known?}
    C -->|yes| D[Status: Enriched]
    C -->|no| E[Status: No match - needs manual research]
    E --> F[Add to review list + create task]

When to use it, when not to

• UseUse it when a third-party or native enrichment integration populates a known set of fields shortly after contact creation, and you need a fallback for the records it cannot match.
• UseUse it when the field your enrichment tool writes on a successful match is known in advance, whether that is Industry, Number of employees, or a vendor-specific field.
• SkipDo not use it without confirming which specific property your enrichment integration writes on success; guessing the wrong property makes this workflow always fall back, even on genuine matches (check in your portal: the exact property your enrichment integration populates on success, checked directly in that integration's settings or field mapping).
• SkipDo not use it if your enrichment tool runs on a schedule longer than a day; extend the delay in Steps to match, or the fallback fires before the tool has had a real chance to match the record.