Data Quality - Lead

Customize how Delpha scores, enriches, and validates Salesforce Lead data. Leads act as a hybrid between a Contact and an Account and Delpha monitors both sides using a specialized set of rules.

Data Quality – Lead Configuration in Delpha

The Data Quality – Lead section in the Delpha Setup App allows you to configure how Lead records are evaluated, cleaned, and scored. This ensures that your Sales Development Reps (SDRs) only focus on conversion-ready prospects.

Key Configuration Areas

  • Lead Assessment Criteria Field: Filter which Leads should be assessed using a Boolean field (default: Lead.Delpha__Do_Not_Assess__c). You can replace this with a custom formula field for dynamic control (e.g., only assess Leads created this year).

  • Lead Assessment: Enable this to assess all existing and newly created Leads once.

  • Lead Continuous Assessment: Automatically reassess Lead records whenever a monitored field changes.

  • Lead Reassessment: Schedule regular reviews even if the record hasn't changed to catch data decay.

    • Options: Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.

Important Note on Token Consumption: These settings activate automation that consumes tokens. To optimize usage:

  • Do not activate both Continuous Assessment AND aggressive Reassessment schedules simultaneously unless necessary.

  • If you perform mass updates on Leads, consider temporarily disabling Continuous Assessment.

Monitored Fields

Delpha monitors specific fields that are critical for Lead Conversion. For each field, you can enable/disable scoring and set automatic recommendation rules.

Profile & Identity (Contact-side)

  • Name: Validates capitalization and removes suspicious characters.

  • LinkedIn Contact: Ensures the profile URL is valid.

Contactability (Reachability)

  • Email: Checks syntax, domain validity, and deliverability.

  • Phone & Mobile Phone: Standardizes to E.164 format and validates line type.

  • Address: Standardizes street, city, postal code, and country.

Company Data (Account-side)

  • Website: Validates domain resolution.

  • LinkedIn Account: Links the Lead to a corporate entity.

Automatic Recommendation Rules

For each monitored field, you can define Triggering Conditions to automatically apply Delpha's recommendations:

  • When value is Incomplete: (e.g., fill in a missing Country based on Phone Number).

  • When value is Invalid: (e.g., fix a typo in an email domain).

  • When value is Inconsistent: (e.g., match the Company Name to the Website domain).

Lead Global Scoring & Metrics

Delpha calculates a Global Quality Score and engagement metrics daily. These are crucial for sorting Leads in list views.

  • D Score (0-100): The composite quality score.

  • Engagement Counters:

    • D Email Count: Volume of email interactions.

    • D Call Count: Number of logged calls.

    • D Event Count: Number of meetings/demos.

Key Takeaways for Users

  • Hybrid Validation: Delpha checks both the person (Email/Phone) and the company (Website) simultaneously.

  • Visual Feedback: Use the Score Meter component on the Lead layout to see quality at a glance.

nsures that your Sales Development Reps (SDRs) only focus on conversion-ready prospects.

Key Configuration Areas

  • Lead Assessment Criteria Field: Filter which Leads should be assessed using a Boolean field (default: Lead.Delpha__Do_Not_Assess__c). You can replace this with a custom formula field for dynamic control (e.g., only assess Leads created this year).

  • Lead Assessment: Enable this to assess all existing and newly created Leads once.

  • Lead Continuous Assessment: Automatically reassess Lead records whenever a monitored field changes.

  • Lead Reassessment: Schedule regular reviews even if the record hasn't changed to catch data decay.

    • Options: Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.

Important Note on Token Consumption: These settings activate automation that consumes tokens. To optimize usage:

  • Do not activate both Continuous Assessment AND aggressive Reassessment schedules simultaneously unless necessary.

  • If you perform mass updates on Leads, consider temporarily disabling Continuous Assessment.

Monitored Fields

Delpha monitors specific fields that are critical for Lead Conversion. For each field, you can enable/disable scoring and set automatic recommendation rules.

Profile & Identity (Contact-side)

  • Name: Validates capitalization and removes suspicious characters.

  • LinkedIn Contact: Ensures the profile URL is valid.

Contactability (Reachability)

  • Email: Checks syntax, domain validity, and deliverability.

  • Phone & Mobile Phone: Standardizes to E.164 format and validates line type.

  • Address: Standardizes street, city, postal code, and country.

Company Data (Account-side)

  • Website: Validates domain resolution.

  • LinkedIn Account: Links the Lead to a corporate entity.

Automatic Recommendation Rules

For each monitored field, you can define Triggering Conditions to automatically apply Delpha's recommendations:

  • When value is Incomplete: (e.g., fill in a missing Country based on Phone Number).

  • When value is Invalid: (e.g., fix a typo in an email domain).

  • When value is Inconsistent: (e.g., match the Company Name to the Website domain).

Lead Global Scoring & Metrics

Delpha calculates a Global Quality Score and engagement metrics daily. These are crucial for sorting Leads in list views.

  • D Score (0-100): The composite quality score.

  • Engagement Counters:

    • D Email Count: Volume of email interactions.

    • D Call Count: Number of logged calls.

    • D Event Count: Number of meetings/demos.

Key Takeaways for Users

  • Hybrid Validation: Delpha checks both the person (Email/Phone) and the company (Website) simultaneously.

  • Visual Feedback: Use the D Score Meter component on the Lead layout to see quality at a glance.

  • Prioritization: Sort your Lead Lists by D Score (Descending) to focus on the highest-quality prospects first.

  • Automation: Configure Lead Continuous Assessment to catch invalid data immediately upon entry (e.g., from web forms).

Last updated

Was this helpful?