Enrich

Enrich adds useful sales context to a contact record from the contact’s saved professional profile URL. It is designed for the point in a sales process where a name and a link are no longer enough: you want to understand the person’s current role, organisation, likely work contact details, and relationship to the rest of the account record before deciding what to do next.

The result is written back to the CRM as structured record data. Depending on the fields in your workspace and the information available from the profile, enrichment may fill configured AI-enabled fields, add a possible work email, or update a current organisation relationship. It runs as a background task, so you can continue working while it processes.

Enrichment is research assistance, not an automatic sales decision. Always check the result before using it for outreach, routing a lead, changing a deal stage, or treating a contact as qualified.

Use cases

Prepare a short list before outreach

You have collected 15 people who may fit your target customer profile. Their records contain names and profile links, but the list does not yet tell you who is a founder, who owns a relevant function, or which organisation each person currently works for.

Add the links, enrich the selected contacts, and review the current role and organisation fields. Your email campaign can then use a more relevant opening, and you can remove people who are clearly outside the campaign before sending anything.

This is most useful for a small, deliberate campaign. A founder or sales lead can review a manageable list in one sitting instead of enriching an entire contact database without knowing how the information will be used.

Turn an inbound lead into a useful CRM record

An enquiry arrives from a website form, referral, or conversation. The contact record has an email address and a profile URL, but no useful sales context.

Enrich the contact before the first call. Use the returned role and organisation information to decide whether the person should enter the active pipeline, which questions to ask, and which existing company record should be connected. This gives a founder enough context to prepare without creating a separate research spreadsheet.

Keep the current account relationship accurate

A contact may have changed jobs since the last time anyone spoke with them. Enrichment prioritises the person’s current or active role and organisation rather than treating every historical position as current.

Run enrichment on a contact whose profile URL is already stored, then check the organisation relationship and the date-sensitive fields. If the workspace has a compatible relation field, the workflow can reuse a confidently matched organisation or create a minimal related record when no safe existing match is found. It does not merge records simply because two names look similar.

Support account-based selling

You are working several contacts connected to the same target account. The contact records have different levels of completeness, and you want to identify the people most relevant to a buying process.

Create a focused view, select only the contacts you have permission to edit, and enrich the group. Review roles, current organisation links, and any configured qualification fields together. You can then decide whether the next action is an email, a meeting, a proposal follow-up, or an internal handoff.

Refresh stale contact context before a follow-up

Before returning to a dormant opportunity, you want to know whether the person is still in the same role. Enrich the small set of contacts tied to that opportunity instead of refreshing every record in the workspace.

Compare the result with the existing timeline, notes, and email history. If the role or organisation changed, update the sales plan and verify that the opportunity is still connected to the right people.

Give a small team a better handoff

In a team of one to twenty people, the person who collected the lead may not be the person who follows up. Enrichment can provide a starting point for the handoff: current role, organisation, possible work email, and any relevant structured fields configured by the team.

The receiving teammate should still read the record and the original conversation. Enrichment reduces repetitive research; it does not replace the source evidence or the team’s judgement.

Getting started

What you need

Before starting, make sure you have:

an account signed in to the correct workspace;
access to the Contacts table and the group or view containing the record;
permission to edit the contact records you want to change;
at least one text field configured as a URL field in the Contacts table; and
the full professional profile URL saved in that field.

The profile URL must be a complete, supported profile address. A person’s name, a profile search page, a shortened link, a company homepage, or text pasted around the address is not enough. The current client validation expects an HTTPS URL in the supported profile format; tracking parameters and extra path text may cause it to be rejected.

You do not need to create a separate enrichment record or prepare a spreadsheet. The contact record and its saved profile URL are the starting point.

Check your permission

Enrichment changes CRM data, so it is available only where you can edit the relevant records. In the current group permission model:

Access level	Can start enrichment?	What it means
Group owner, administrator, or editor	Usually yes, for records they can edit	They can start a single-record or eligible bulk update.
Viewer or read-only access	No	They can inspect records but cannot start an action that writes changes.
Mixed selection	Only when every selected record is editable	The bulk action is disabled when the selection cannot be edited as a whole.

The client checks edit access before showing the single-record action and before enabling the bulk start button. The server checks access again when the workflow writes, so seeing a button is not a guarantee that every record in a complicated permission setup can be changed.

If you need enrichment but do not have edit access, ask the group owner or workspace administrator to give you the appropriate group role, or ask an editor to run the action on the intended records.

Make the Contacts table ready

The current client exposes profile enrichment only for the Contacts table. It also requires at least one text field whose input type is URL.

If the table is not ready:

Open the Contacts table in a group or view where you can manage fields.
Add a text field for the professional profile URL, or select the existing field used for that purpose.
Set the field’s input type to URL.
Save the field and return to the contact records.
Paste the full profile address into the field and save the contact.

The field’s display name can be customised. The client checks the field type and the saved value, not only the label. If there are several URL fields, a valid supported profile address in any of them can make the contact eligible.

Optional: configure fields for AI fill

If your workspace has AI Fields, you can decide which fields should be filled automatically and what each field means. This is useful when your sales process has custom objects or a custom qualification model.

In the table’s AI field settings:

Review the fields available for AI fill.
Turn on the fields you want enrichment to populate.
Add a short plain-language instruction for each field.
Save the settings before running enrichment.

Examples of useful instructions are:

“Record the person’s current job title in a short phrase.”
“Choose the closest customer segment from the available choices.”
“Record the current organisation only; do not use a previous employer.”
“Write one concise sentence explaining why this person may be relevant to our target customer profile.”

The system supports common structured field types such as text, numbers, dates, choices, multiple choices, and compatible relationships. Fields that are disabled for AI fill, fields with no matching information, and unsupported field types remain unchanged. A field prompt is an instruction for mapping information into that field; it is not a request to invent an answer.

Where to find the action

There are two current entry points:

One contact: open a contact record. The Enrich button appears in the record header or side panel only when the record is in the Contacts table, the table has a URL-type field, the saved value is valid, and you have edit access.
Several contacts: open a group or view, select contacts, and use Enrich in the selected-record bulk bar. The bulk menu shows how many selected records it will process and identifies records that are not eligible.

The current client flow is selection-based for bulk enrichment. If an older screen or help text says Enrich All Records, do not assume it will process every record in the view: select the intended records and confirm the count shown by the current bulk bar before starting.

How to use it

Enrich one contact

Use this path when you are preparing for one conversation or need to check one person’s current account relationship.

Open the contact record or open it in the record side panel.
Check the contact name, email, phone number, and organisation information already stored. This gives you a baseline for review.
Open the URL field and confirm that it contains the person’s full professional profile address. Remove surrounding text and save the field if you changed it.
Select Enrich in the record header.
Wait for the action to be accepted. The lookup and record update run in the background.
When the enrichment status changes to completed, return to the contact and review the changed fields.
Check the current organisation relationship and any possible work email before using them in outreach.

If the button is not visible, the record is not currently eligible. Work through the checks in Troubleshooting rather than trying to start the action from a different table.

Enrich selected contacts

Use the bulk flow when you have a defined campaign, account list, or follow-up set.

Open the group or view containing the Contacts table.
Filter the view first so it contains the business set you actually want to work on. For example, filter by campaign, opportunity, owner, or a “needs review” field.
Select the intended contact records.
In the selected-record bulk bar, select Enrich.
Read the count in the menu. It describes the selected records being prepared for enrichment.
Review the records listed as missing a valid profile URL. Use Open to inspect one, or Remove to take it out of the selection.
Add or correct the missing URLs, or remove those records from the selection. In the current strict bulk flow, Start remains disabled while invalid records are still selected.
When every selected record is eligible and you have edit permission for all of them, select Start.
Keep working in the workspace while the background task runs. The selection is cleared after the task starts.
When the task is complete, refresh the view if necessary and review a sample of the updated records. For an important campaign, inspect every record before sending messages.

The bulk action uses the full contact objects loaded by the client. For selections larger than 200 records, the current client warns that Enrich will use the first 200 records and skip the rest. Reduce the selection or split the work into intentional batches when the whole list matters.

What enrichment can change

The workflow reads the profile data, matches it to the intended contact, and maps useful results into the workspace schema. The exact result depends on the source profile and the fields available in your table.

It may:

fill compatible AI-enabled structured fields;
provide profile details such as a current role or organisation;
return a possible work email when one can be found; and
update or create a related organisation record when the current relationship is clear and the workspace has a compatible relation field.

It normally prioritises the person’s current or active position. Historical positions are not treated as current unless the request specifically asks for history.

It does not:

guarantee that every field will be filled;
guarantee that a work email will be found or that it is safe to use without checking;
replace existing information simply because a new value is available;
treat a name similarity as proof that two people or organisations are the same;
delete records; or
make an outreach, qualification, or deal-stage decision for you.

Existing values are generally preserved unless the source provides a major contradiction or the instruction explicitly asks for an update. Missing information is left blank rather than guessed. This means a successful run can legitimately leave some fields unchanged.

How matching protects the right record

The saved profile URL is the strongest identity clue in this flow. The workflow also receives the selected contact’s record identity, checks exact identifying information first, and uses name-based search only as a fallback.

This matters when two people have similar names or when an organisation has several legal or trading names. The workflow is designed to avoid putting one person’s role, email, or organisation onto another person. If an organisation relationship is ambiguous, it is safer to review it manually than to force a link.

If a current organisation is clearly identified but no existing organisation record can be matched confidently, the workflow may create a minimal related organisation record and connect the contact to it. Review that new relationship before using the account in a campaign or reporting view.

Review the result as part of your sales process

Enrichment is most valuable when it leads to a clear next action. After the run:

Open the contact and compare the updated fields with the source profile.
Confirm that the person is still relevant to the opportunity, campaign, or target account.
Check whether the current organisation relation is correct.
Verify a possible email address before sending a campaign or personal email.
Update your CRM’s own qualification, owner, segment, or next-step fields manually when the business decision requires judgement.
Add a note or task if the information changes the plan for the next meeting or follow-up.

Do not copy a long summary into a single description field when the workspace has dedicated fields for the same information. Structured values are easier to filter, report on, and use in later sales steps. Use a notes field only for concise, high-value context that has no suitable structured field.

Scenario: prepare a campaign list

Suppose a founder has a view called “New product prospects”. It contains contacts collected during the last two weeks. Each contact has a profile URL, but the founder does not know which people are decision makers.

The practical flow is:

Filter the view to the intended campaign and remove obvious duplicates or contacts already in an active conversation.
Select a small batch.
Run Enrich and resolve any missing or invalid URLs shown in the menu.
Review current roles, organisations, and the configured fit or segment fields.
Remove contacts who are not a fit, link the remaining contacts to the correct account records, and only then prepare the campaign message.

The benefit is not simply “more data”. The benefit is a cleaner campaign audience and a better reason for each message.

Scenario: prepare for a first meeting

An inbound contact has booked a meeting, but the record contains only a name and email. The profile URL is available from the original enquiry.

Enrich the single contact before the meeting, then check the current role and organisation. Use the result to prepare two or three relevant questions, but keep the conversation open: profile information can be incomplete or out of date. After the meeting, use the recorder, notes, or timeline to store what the person actually said; enrichment should not be treated as a substitute for the conversation record.

Scenario: revive a dormant opportunity

The last contact on an opportunity has not replied for several months. Before sending a follow-up, enrich the contact and check the current organisation relationship.

If the person changed roles, find the right current stakeholder and update the opportunity plan. If the person is still relevant, use the refreshed context to write a specific follow-up rather than sending a generic reminder. Record the decision in the CRM so another teammate can see why the opportunity was reopened or paused.

Scenario: build an account view for a small sales team

The team has a target-account group with several contacts per account. Some contacts are complete, while others are missing current role details.

Create a view filtered to the target accounts and contacts with a valid profile URL. Select a controlled batch, enrich it, and review the organisation relations and role fields. Then use the view to identify missing buying roles, assign follow-up owners, and prepare meeting outreach. Repeat in batches rather than launching one large run that is difficult to check.

Re-run enrichment safely

You can re-run a contact when the profile changed or the first result was incomplete. Before doing so:

make sure the saved URL is still the correct person’s profile;
check whether the existing values were intentionally entered by a teammate;
change the AI field instructions if the result needs a different format; and
run one contact first when changing the table setup.

The exact profile URL and selected record give the workflow strong identity evidence, so a re-run is intended to update or reuse the existing contact rather than create a duplicate. Still review the result, especially if the person has recently changed organisations.

Understand task status

After starting, the client shows a small enrichment status item. It can indicate that enrichment has started, is processing, has completed, or has been cancelled. The item includes the number of records in the task and can be dismissed from the status area.

The backend processes records as a background workflow and keeps counts for processed, successful, failed, and skipped items. A task can therefore finish even when a few records could not be updated. Use the completion message as a prompt to inspect the records, not as proof that every selected contact changed.

Avoid starting the same large batch repeatedly while a previous task is still running. The workspace limits the number of active enrichment tasks, and repeated retries make it harder to tell which result is the latest one.

Troubleshooting

The Enrich button does not appear for a contact

Check each condition:

Is the record in the Contacts table rather than a company, deal, task, or custom table?
Does the Contacts table have a text field whose input type is URL?
Is the profile URL saved in that field, rather than still being edited?
Is it the full supported profile address, beginning with https://?
Do you have edit permission for the record’s group?

The client hides the single-record action when there is no valid eligible URL or when the user cannot edit the record. Adding a URL field to an unrelated table will not enable this feature there.

The URL looks correct but is rejected

Copy the address from the person’s actual profile page and paste only the address into the URL field. Remove:

a person’s name before or after the URL;
spaces, quotation marks, or line breaks;
a search-results address rather than the profile address;
a shortened or redirected link; and
tracking parameters or extra path segments.

Save the contact, close and reopen the record, and check whether Enrich appears. If the address is a valid profile but the client still rejects it, keep the URL saved and contact support with the table name and the exact validation message; do not paste the URL into a different field type as a workaround.

The bulk Start button is disabled

Open the Enrich menu and read the invalid-record list. The current bulk flow is strict: every selected record must have a valid profile URL before Start is enabled.

For each invalid record, choose Open to add or correct the URL, or choose Remove to take it out of the selection. After editing a record, select the intended records again if the menu still shows the old selection.

The bulk action says I do not have permission

Bulk enrichment requires edit access for every selected contact. One record with viewer access, a restricted group, or a record-level restriction can prevent the whole selection from starting.

Try a smaller selection to identify the restricted record. Ask the group owner or workspace administrator to grant the appropriate edit role, or have an authorised teammate run the action. Do not assume that being able to view a contact means you can change it.

More than 200 selected records are not processed

This is expected in the current client flow. The bulk bar warns when a selection is larger than 200 and uses only the first 200 full records for Enrich. Split the work into smaller batches and verify the selected count before each run.

For large batches, also consider whether your sales process depends on change-triggered automations. The client warns that large bulk changes may not emit an individual record event for every row, so an automation that expects one event per record may not run as it does for a manual single-record edit.

The task is still processing

Enrichment is asynchronous. Keep the workspace open long enough to see the status change, and refresh the relevant group or record if the values are not visible immediately.

If the task remains active for an unusually long time:

Do not start the same large batch again immediately.
Check whether another enrichment task is already running in the workspace.
Try one contact with a confirmed profile URL.
If the single contact also remains stuck, record the approximate start time and contact support.

The service also limits how many enrichment tasks can run at once. A new task may be refused while existing tasks are still active; wait for them to finish before retrying.

The run is refused because of a usage limit

Enrichment is also subject to the workspace or user’s usage allowance. This is different from a task being busy: waiting may release an active-task slot, but it will not restore an allowance that has already been used.

If the message refers to usage, quota, or allowance:

Check the workspace’s usage or plan information if it is available to you.
Avoid repeatedly retrying the same batch.
Ask the workspace administrator whether the allowance has been reached or whether the plan needs attention.
If you need to continue immediately, enrich only the contacts that are most important to the next sales action once capacity is available.

Do not work around a usage restriction by copying the same contact into several records. That makes the CRM less reliable and does not improve the source data.

The task completed but some fields are blank

Blank fields do not necessarily mean the task failed. The source may not contain the information, the field may be disabled for AI fill, or the value may not fit the field’s type.

Check the following:

the profile is accessible and belongs to the intended person;
the field is enabled in the table’s AI field settings;
the field instruction is specific enough for the field;
the field type matches the value you expect, such as a number, date, or choice; and
the requested information is actually present in the source.

Do not fill the blank with a guess merely because you expected a value. Add it manually only when you have another reliable source.

The wrong person or organisation appears to be linked

Stop using the result for outreach until it is checked. Compare the saved profile URL, name, organisation, and other identity details with the source profile.

If the organisation relationship is wrong, correct the relationship manually using the CRM’s record controls and review whether the contact’s profile URL belongs to the right person. If two organisations have similar names, do not merge them based on name similarity alone. Ask an administrator or support for help if the record structure needs correction.

A work email was not found

Email discovery is best effort. A profile can be enriched successfully even when no work email is returned, and an email that is returned should still be verified before a campaign or personal outreach.

Use the existing verified email if one is already stored. If there is no safe address, continue with another approved channel or ask the contact directly rather than treating a missing result as a system error.

Existing information was not replaced

This is usually intentional. The enrichment workflow preserves existing values unless the new source presents a major contradiction or the instruction explicitly requests an update. This protects carefully maintained phone numbers, emails, ownership fields, and qualification decisions.

If a value is genuinely outdated, update it deliberately in the record and record the reason in a note or timeline entry. Then re-run enrichment only if you need additional profile context.

If the profile clearly identifies a current organisation but no existing organisation could be matched confidently, the workflow may create a minimal related record instead of attaching the contact to the wrong one.

Open the related record and check its name, website or other identity details. Merge or correct it only after confirming the organisation. If the relation is not appropriate for your sales process, remove or change the relation using the normal record controls; enrichment itself does not delete records.

The task failed or only part of the selection changed

A batch can contain successful, failed, and skipped items. Review which records changed and retry only the failed or incomplete contacts with confirmed URLs. A smaller batch is easier to diagnose.

If repeated attempts fail for the same contact:

confirm the profile URL still resolves to the intended person;
check the record’s edit permission;
confirm that the Contacts table and URL field have not been changed;
wait if the workspace is already running many enrichment tasks; and
contact support with the contact record, group, approximate run time, and visible error message.

Do not include private credentials or unrelated customer data in a support request.

AI field settings will not save

Check that you have permission to manage the table schema, not only permission to edit individual records. If you can edit records but cannot save field settings, ask a table or workspace administrator to configure the AI fields.

When changing a prompt, keep it short and field-specific. Save the prompt, test it on one contact, and inspect the result before applying the setting to a larger selection.

Recommended operating checklist

Before enrichment:

Filter the view to a meaningful sales set.
Confirm the contact and profile URL belong together.
Decide which fields the team actually needs.
Test one record when changing field settings.
Select only records you can edit.

After enrichment:

Review current role and organisation information.
Verify possible email addresses before outreach.
Check related records for duplicate or ambiguous organisations.
Correct important values manually when the source or business context requires it.
Record the next sales action in the CRM.

Used this way, Enrich turns profile research into a controlled CRM step: prepare the contact, enrich a focused set, verify the result, and use the improved context to move the right outreach, meeting, or opportunity forward.