Establish identity before retrieving contact data
Preserve the original profile URL and your source record ID. Normalize the URL only after verifying which parts identify the profile. Remove tracking parameters when appropriate, but do not substitute a company page for a person profile or infer identity from a display name alone. Compare the candidate’s name, company and role with the source evidence. When the person recently changed jobs, decide whether the job requires their current employer or the employer associated with an earlier event. A founder’s old company domain may no longer be a useful work-email input.Choose the lookup that matches the job
A person search finds candidates; an enrichment call retrieves additional information for a matched person. Apollo documents People Search separately from People Enrichment. Inspect the current endpoint and access requirements before assuming a search response includes usable email and phone data. In Deepline, start from the integration catalog or search the current tools. Ask the agent to show the chosen input contract, the identity fields it will use, the output fields it expects and the stopping rule. Use only providers and sources you are authorized to access. For a founder-contact workflow, confirm the founder’s identity and current company first. A public company website can help establish context, but guessing an address from a name pattern is not verification. Do not publish a person’s contact details as part of a content example.Verify email and phone independently
Apply your email verification policy to a candidate email. Preserve the raw provider status, verification time and any catch-all or unknown result. For phone data, record the returned number, country context, provider and observation time. Number formatting alone does not establish ownership, reachability or whether it is a mobile number. Retain the provider’s evidence for those attributes and label missing evidence as unknown. Use the phone enrichment workflow to define channel-specific acceptance. One lookup may return both channels, but the acceptance decision still belongs to each field. Do not let a verified email cause an unverified phone number to inherit a verified label.Worked match: a job change invalidates one field
Suppose a fictional source record identifies Alex Example at Example Labs. A new profile observation places Alex at Example Systems, while a contact provider returns a work email associated with Example Labs and a phone number with no ownership evidence. The task is to reach Alex in their current role. Here is the resulting decision:
A mailbox check cannot repair an employment mismatch. Another successful mailbox check on the same old address adds no evidence about the current role. Resolve the employer, then request a new email candidate using the matched profile and current company context.
If the job instead concerns a historical event at Example Labs, retain that event association separately. Do not overwrite the historical company just because the person’s current employer changed.