Skip to main content
Open a person in the private research workbench and choose Find contact details. The lookup stays on the page. Saved emails and phone numbers appear in the person’s contact section, with their source and check date. Opening a person does not start a lookup. Reopening a person reuses the saved answer, including a lookup that found nothing. Phone results can arrive after the email. The page shows progress while they are being checked. The lookup uses the person’s confirmed professional profile. An unconfirmed identity needs research before provider details can be attached to it. A database match does not establish email delivery or permission to contact someone. Mobile, direct work and company numbers keep their provider labels, and a do-not-call result is not offered as a callable number.

​
Lookup status

If a lookup fails, its saved request remains available for the team to investigate. Reloading contacts checks saved progress. It does not purchase another lookup.

​
For workspace operators

Keep provider credentials and accounting inside the connected integration. Customer screens show the contact action and its result. Explicit requests use an authenticated, Page-bound event pipeline. A preparation recipe resolves the canonical person and freezes the confirmed profile. A managed dataset row action saves its provider receipt before invoking Apollo and reuses completed receipts when writeback is retried. An uncertain provider attempt requires reconciliation before another purchase. A separate bounded recipe polls an existing phone request. The daily public-source research recipe does not run paid enrichment. Contact requests and provider answers have their own datasets, so adding contact details does not replace financial research or team reviews.