Data enrichment helps FirstTouch find or improve prospect and company information for outreach, routing, and personalization.
Enrichment Types
Results are not guaranteed. A lookup can return no usable result, partial data, or data that requires review.
Saved Team results can be reused. Flow Plans have separate contact-profile, company-profile, email, and phone enrichment controls. New plans default contact and company enrichment on, and email and phone enrichment off.
Where Enrichment Appears
Enrichment can appear in:
- Chrome Extension
- HubSpot UI Card
- Flow Plan enrichment steps
- Flow settings
- MCP requests when data is already known or an enrichment tool is explicitly requested
- Activity details and task context
Credits
Some enrichment actions consume FirstTouch credits. Current credit rules depend on your plan, action type, and billing configuration. Use Billing as the source of truth.
HubSpot Writes
For Flow Plans with CRM integration enabled, FirstTouch automatically writes supported mapped values, including LinkedIn URLs, to matched HubSpot records when the HubSpot integration is connected. A separate CRM Enrichment step is needed only to copy a value into a specific custom HubSpot property. Writes still depend on matching, mapping, permissions, and overwrite behaviour.
A standalone enrichment lookup returns its result to the requesting surface. It does not automatically apply that result to an existing Flow Enrollment, Awaiting candidate, Audience Contact, saved prospect, or HubSpot record. Using a standalone result elsewhere requires a supported write action. Flow Plan enrichment and its automatic mapped HubSpot write-back follow the Flow Plan’s CRM integration setting.
Using Enriched Data In Flow Plans
Enriched fields can improve personalization and routing when they are available on the Flow Enrollment before the relevant step runs. A CRM action copies supported FirstTouch properties to mapped CRM properties; it does not create or enrich the CRM record. If a required variable cannot resolve, the step may wait, require fallback copy, or fail validation depending on configuration.
