> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enrichment Setup Guide

## Creating Your First Enrichment Profile

Enrichment profiles are reusable configurations that define how to enrich your leads. You can attach these profiles to Skills and Flow steps across different workflows.

<Steps titleSize="h3">
  <Step title="Access Enrichment Settings">
    1. Navigate to **Settings** in the main menu
    2. Click **Enrichment** to view your enrichment profiles
    3. Click **Create Enrichment Profile** to start
  </Step>

  <Step title="Choose Your Enrichment Mode">
    **Advanced Enrichment** (Recommended)

    * Uses allGood-managed web search and multiple data providers
    * Higher hit rates and data quality
    * Automatically finds LinkedIn profiles first
    * Best for comprehensive lead enrichment

    **Basic Enrichment**

    * Single data provider lookup
    * Lower cost per enrichment
    * Predictable data sourcing
    * Best when you have a preferred provider
  </Step>

  <Step title="Configure When to Run">
    **Always**

    * Enriches every lead, even if data is already complete
    * Good for data validation and updating existing records
    * Higher cost but ensures freshest information

    **Only when missing data** (Recommended)

    * Only enriches leads with empty fields
    * More cost-effective for partial datasets
    * Skips leads that are already complete
  </Step>

  <Step title="Set Up Data Providers (Basic Mode Only)">
    If you chose Basic Enrichment:

    1. **Select Provider**: Choose from available data sources
       * ZoomInfo: Business contact database
       * LinkedIn: Professional profile data
       * Clearbit: Company and contact information

    2. **Choose Lookup Method**: Select how to find leads
       * By email address (most reliable)
       * By name and company
       * By LinkedIn URL
  </Step>

  <Step title="Configure Data Elements (Advanced Mode Only)">
    **Professional Email Discovery**

    * ✅ Enable for B2B campaigns requiring work contacts
    * Uses specialized email finding providers
    * Replaces personal emails automatically

    **Phone Number Discovery**

    * Enable only when phone outreach is critical
    * Significantly increases enrichment costs
    * Searches across multiple phone number providers
  </Step>

  <Step title="Select Fields to Enrich">
    Choose which fields should be enriched:

    **Essential Fields**

    * LinkedIn URL (highly recommended for unique identification)
    * Email (if you need professional contacts)
    * Job Title
    * Company

    **Additional Fields**

    * First Name / Last Name
    * Phone (only if phone discovery is enabled)
    * Industry
    * Company size/employee count
    * Location (City, State, Country)

    **Field Configuration Options**

    * **Instructions**: Specific guidance for each field
    * **Overwrite**: Whether to replace existing data
  </Step>

  <Step title="Add Metadata Fields">
    Metadata fields store information about the enrichment process itself:

    **Useful Metadata Fields**

    * **Enrichment Source**: Which provider found the data
    * **Confidence Score**: How confident the system is in the data
    * **LinkedIn Profile Found**: Whether a LinkedIn profile was located
    * **Enrichment Date**: When the enrichment occurred
  </Step>

  <Step title="Write Custom Instructions">
    Provide specific guidance for the enrichment agent:

    **Example Instructions**

    ```
    Focus on technology companies with 100+ employees.
    Only use LinkedIn data for C-level executives.
    Prioritize finding professional email addresses over phone numbers.
    Skip enrichment for leads from educational institutions.
    ```
  </Step>

  <Step title="Save and Test">
    1. **Name your profile** with something descriptive like "Standard B2B Enrichment"
    2. **Add a description** explaining when to use this profile
    3. **Save** the configuration
    4. **Test** with a small sample of leads first
  </Step>
</Steps>

## Using Your Enrichment Profile

### In Worksheets

1. Add an "Advanced Enrichment" step to your workflow
2. Select your enrichment profile from the dropdown
3. Run a test with sample data

### In Skills

1. When configuring agent skills, attach your enrichment profile
2. The agent will use these settings automatically during execution

### Multiple Profiles Strategy

Create different profiles for different scenarios:

**High-Value Leads Profile**

* Advanced mode with email and phone discovery
* Comprehensive field enrichment
* Always enrich (even if data exists)

**Bulk Processing Profile**

* Basic mode with preferred provider
* Essential fields only
* Only when missing data

**Event Leads Profile**

* Advanced mode focused on professional contacts
* Custom instructions for event context
* Metadata tracking for event attribution

## Next Steps

* **Monitor Performance**: Track enrichment hit rates and costs
* **Optimize Profiles**: Adjust settings based on results
* **Scale Up**: Apply successful profiles across more workflows
* **Advanced Features**: Explore custom field mappings and validation rules

## Troubleshooting

<AccordionGroup>
  <Accordion title="Low Hit Rates">
    * Add LinkedIn URL as a field (improves matching accuracy)
    * Use Advanced mode for better provider coverage
    * Check custom instructions for overly restrictive criteria
  </Accordion>

  <Accordion title="High Costs">
    * Switch to Basic mode for budget control
    * Disable phone number discovery
    * Use "Only when missing data" setting
  </Accordion>

  <Accordion title="Data Quality Issues">
    * Enable overwrite for fields that need updating
    * Add validation metadata fields
    * Use custom instructions to specify quality requirements
  </Accordion>

  <Accordion title="Provider Errors">
    * Check data provider API key configuration
    * Verify you have sufficient credits with the provider
    * Try switching to a different lookup method
  </Accordion>
</AccordionGroup>