Partial Enrichment Before Sequencing: Decide What to Send, Hold, or Retry
TL;DR: Do not treat enrichment as globally complete or failed. Define required fields for each channel and decision, preserve provenance for every returned value, and route each contact to send, hold, retry, review, or skip. One missing phone number need not block verified email, but a missing required personalization fact must never be invented.
Partial enrichment is normal because different sources cover different fields and entities. A contact can have a verified email but no phone, a current title but uncertain company match, or a valid person record with no evidence for the personalization field a sequence expects. One global complete flag hides these distinctions.
The enrollment decision should be channel-specific and claim-specific. Our B2B data and sequencing pages describe a workflow from prospecting and enrichment into outreach, but a team must define which fields are mandatory, which can be retried, and which failures should stop action. The rules below are an operating model, not a published native retry policy.
| Record state | Phone | Personalization | Decision | |
|---|---|---|---|---|
| Verified work email, no phone | Eligible if policy passes | Unavailable | Use only verified fields | Send email path, omit call |
| No email, verified direct phone | Unavailable | Eligible if policy passes | Use only verified fields | Route to call task or hold |
| Reachable channel, missing required claim | Potentially reachable | Potentially reachable | Required evidence absent | Hold or use approved generic copy |
| Conflicting company or role | Do not send | Do not call | Identity uncertain | Review or skip |
| Provider exhausted, no reachable channel | Unavailable | Unavailable | Irrelevant | Skip and record reason |
What does partially enriched mean at the field level?
A partial record contains some usable values and some absent, stale, conflicting, or unverified values. Missing is not the same as wrong. A blank phone field does not invalidate a verified email, while a company mismatch can invalidate every downstream field because the person may be attached to the wrong account.
Store status per field: value, source, observed or verified time, method, confidence or verification state, and overwrite decision. Do not collapse these into a single enriched timestamp. Field-level provenance lets the sequence gate inspect only what its action needs.
Which fields should be required before enrollment?
Start from the action. Automated email needs a permissible and deliverable email, correct identity, owner and suppression checks, and all facts used in copy. A call task needs a supported phone value and current role context. Social or research tasks need their own requirements.
Separate routing fields from message fields. Account owner and lifecycle state control whether outreach is allowed. Email or phone controls reachability. A product, hiring, or technology observation controls whether a specific sentence is safe. The record may pass one gate and fail another.
When should the workflow retry enrichment?
Retry when a source failure is temporary, another approved provider may cover the field, or a refresh window has elapsed. Cap attempts by field and preserve each provider outcome. Repeating the same request with no changed input wastes credits and can obscure the original failure.
Use a next-eligible time and terminal reason. A retry queue should show provider, field, attempt count, last result, next action, and owner. Stop retrying when the source set is exhausted, the contact is no longer relevant, the record enters a protected state, or the expected value does not justify more cost.
How should missing personalization fields affect copy?
Remove or replace the claim with approved copy that does not require the missing field. Do not ask a model to fill the gap from context. A generic but accurate sentence is safer than a fabricated specific one. If the sequence was designed around that fact, hold the record instead of changing the message without review.
Maintain copy dependencies. Each dynamic section should name the field or evidence it needs and the fallback approved for that absence. Review fallbacks separately because a fallback can change the promise, audience, or tone. A blank token, guessed value, or literal placeholder is a failed preflight.
How do our data and sequencing products fit the handoff?
Our B2B Company and Contact Data page describes prospecting, enrichment, verification, and access to multiple sources. Our Sequencing page describes coordinated email, phone, and social workflows. The handoff should pass field status and provenance, not merely a contact ID.
Our public Signals catalog also lists contact-data sources with different coverage. Source diversity can improve coverage, but it does not make every field complete or current. Test the exact record states your team sees, verify plan availability, and define how downstream actions behave when a value remains unknown.
How should the team audit send, hold, retry, and skip decisions?
Sample records from every terminal and nonterminal path. Confirm that sent records met all channel and message requirements, held records have an owner and review date, retries changed an input or provider, and skipped records preserve a reason. Look for contacts that entered more than one path.
Measure workflow quality with decision counts, override reasons, stale queue age, downstream bounce or invalid-number outcomes, and unsupported-copy defects. Do not treat provider fill rate as the same thing as contact usability. A filled field can be wrong, and an incomplete record can still support a safe action.
How should field authority work when sources disagree?
Define which source may create, refresh, or overwrite each field. A verified email provider may be authoritative for deliverability while the CRM remains authoritative for account ownership. A public profile can support a current title without being allowed to overwrite a contractual customer state. One universal source priority is usually too coarse.
When two approved sources disagree, keep both values and route the field to a conflict rule. Store the selected value, rejected value, source times, and reason. Never hide disagreement by keeping whichever result arrived last. Downstream sequences should read only the resolved field state and should fail closed when the required field is still disputed.
What should happen after a bounce or invalid phone result?
Treat the downstream outcome as new evidence about the field, not as proof that the entire person record is unusable. Suppress the failed channel immediately, attach the outcome to the source used, and decide whether another approved source can provide a replacement. Preserve the original value for audit without allowing reuse.
Feed verified outcomes into provider and workflow review. Compare failure reasons by source, geography, role, and age while keeping denominators clear. Do not declare a provider inaccurate from a small convenience sample, but do investigate repeated defects and adjust source order, refresh windows, or terminal rules.
Launch the workflow with controlled records
Before enabling buyer-facing actions, create a test pack that represents the decisions the workflow must make. Include a clean eligible record, a record with missing required data, a contradiction, an existing owner, a protected lifecycle state, and a record that changes while processing. Write the expected action, stop reason, owner, and stored fields before running the test. This prevents a plausible but unintended result from being accepted after the fact.
Inspect the complete path in the system of record. Confirm that the input evidence remains available, one policy version explains the decision, one owner receives the work, and the intended state is written back exactly once. Re-run the same pack after changing a source, prompt, field mapping, routing rule, sequence, or integration. Production volume should increase only after the controlled records remain explainable and the receiving team can clear the resulting review and follow-up work.
- Entry test: eligible records enter once and suppressed records do not enter
- Evidence test: every allowed message claim remains linked to the correct source and date
- Ownership test: conflicts hold for review instead of choosing an arbitrary owner
- Interruption test: replies, meetings, opt-outs, and lifecycle changes stop or transfer work
- Audit test: each outcome retains the rule version, reason, reviewer, and terminal state
Apply a reproducible review checklist
- Identity: confirm the person, company, location, and relationship used by the decision
- Evidence: preserve the source, observation time, verification state, and contradictory facts
- Ownership: identify the one person responsible for the next action and any protected lifecycle state
- Action: name the send, hold, retry, review, transfer, or skip decision explicitly
- Audit: record the policy version, reason, outcome, and correction without rewriting history
Run the checklist on controlled records before changing live outreach. Include a clean case, an ambiguous case, a stale case, an ownership conflict, a suppressed record, and a record whose state changes mid-workflow. The expected behavior should be written before the test so a plausible but unintended result does not pass by convenience.
Use stop rules that fail closed
| Observed state | Immediate action | Resume condition |
|---|---|---|
| Identity conflict | Hold all channels | Person and account are reconciled |
| Suppression or active relationship | Stop net-new outreach | Current owner authorizes another path |
| Required claim missing | Use approved fallback or hold | Evidence becomes available |
| Retry limit reached | Skip field or record with reason | New source or changed input approved |
| Channel validation fails | Suppress that channel | New verified value replaces it |
A stop rule needs an observable condition, a recorded reason, and a named owner. “Needs review” without a reviewer or due state is another backlog. When a higher-priority buyer or CRM state appears, preserve the work already completed and transfer the context instead of letting two workflows continue independently.
Avoid common implementation mistakes
- Letting a missing value silently become a negative answer
- Treating an inferred relationship as a verified fact
- Starting a buyer-facing action before ownership and suppression checks finish
- Keeping no source, timestamp, or reason for the decision
- Increasing volume before reviewing failures and overrides
Teams ready to build the workflow can sign up for Unify and start with a controlled audience, explicit review ownership, and no live action until the test records behave as expected.
Frequently asked questions
Can a contact enter an email sequence without a phone number?
Yes, if email-specific identity, validation, ownership, suppression, and copy requirements pass. The missing phone should block only the phone path.
Should missing fields be filled by AI?
No. AI can research sources, but a required value or claim must remain unknown until supported by inspected evidence.
How many enrichment retries should a workflow allow?
Set a field-specific cap based on providers, cost, freshness, and expected value. There is no universal safe number.
What should happen when company identity conflicts?
Hold all buyer-facing channels until the person and company relationship is reconciled.
How should fallback copy work?
Preapprove copy that makes no claim dependent on the missing field and ensure it still fits the audience and sequence purpose.
What should an enrichment audit sample?
Include sent, held, retried, reviewed, skipped, overridden, bounced, and invalid-number records from the same policy version.
Glossary
- Field provenance: The source, time, and method associated with a value
- Channel eligibility: The requirements a record must pass for one communication channel
- Copy dependency: A field or fact required for a message element
- Retry queue: Records waiting for a changed source, time, or input before another attempt
- Terminal reason: The recorded explanation for ending enrichment or outreach
