Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 205 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

Delpha - User Documentation

DELPHA FOR SALESFORCE

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Install Delpha Connector for LinkedIn Enrichment

Install the Delpha Connector browser extension to link your LinkedIn account with Delpha and unlock powerful enrichment features. Compatible with Chrome and Edge for seamless integration.

Install the Delpha Connector for LinkedIn Enrichment

To enable advanced LinkedIn enrichment features in Delpha:

  • Install the Delpha Connector browser extension from the Chrome Web Store

  • The extension is compatible with both Google Chrome and Microsoft Edge

  • Once installed, it seamlessly connects your LinkedIn account to Delpha, allowing for smoother and more accurate data enrichment

This integration helps automate and enhance LinkedIn data collection within your Delpha workflows.

Build 3.58.6 (04tRl000001FVsXIAW)

Apply the package

If you are upgrading from a version below 3.58, you must run the migration script

Upgrade tasks

Migration steps are not cumulative. Depending on your initial version, you will have to apply all upgrade tasks listed on the main Build Item (eg: Build 3.58.x), all the way from your current version up to the version you are upgrading to.

Build 3.60.x

No migration step when upgrading from 3.58x.

Build 3.60.1 (04tRl000001IJTRIA4)

Apply the package

Welcome to Delpha Documentation

Explore Delpha’s documentation for setup, integration, deduplication, and LinkedIn enrichment. Includes FAQs, job tracking, and support options.

This Help Center is organized into structured categories to help you quickly find the guidance you need, whether you're setting up Delpha for the first time or fine-tuning deduplication rules.


DELPHA DOCUMENTATION

Start here to understand how Delpha works and how to get set up.

  • Welcome to Delpha: Introduction and overview

  • Delpha Setup:

  • Delpha Upgrade:

  • Delpha Apps:

  • Use Cases Setup:

  • Delpha Campaigns:


HOW TO – FAQ

Common tasks, step-by-step guides, and practical how-to articles.

  • Delpha Integration:

  • Delpha Job Tracking:

  • Delpha LinkedIn Connector:

  • Delpha Duplicate:


TROUBLESHOOT

For when you need assistance or something isn’t working as expected.

  • Grant Access for Delpha Support:


DELPHA API AND MCP

.

Assign a Delpha Permission Set Group

Assign the right Delpha permissions by selecting a persona-based permission set group—Admin, Data Steward, or User—for each Salesforce user. Simplify access control and role-based setup.

Assigning Delpha Permission Set Groups

To assign the correct permissions in Delpha, follow these steps:

  1. Determine the User’s Persona: Choose the appropriate role — Admin, Data Steward, or User — based on their responsibilities.

  2. Assign the Permission Set Group:

    • Go to Users in the Salesforce Setup.

    • Find the user and assign one of the following groups:

      • Delpha Admin – Full access including Setup and Data Quality tools

  3. Save your changes to apply the permissions.

This ensures each user has the appropriate access to Delpha features based on their role.

Do not forget to assign the Delpha Admin permission set group to you

Build 3.58.2 (04tRl000001EpLRIA0)

Duplicate Settings - Migration to the new JSON based format

From this version, the Duplicate Settings have been moved from SObejcts into a unique JSON.

This reduces the complexity of Duplicate settings spanned over many objects (mainly DDQ Duplicate Objects, DDQ Duplicate fields...). This change requires a migration step that is made simpler by using a dedicated migration package provided by Delpha.

  • After the main Delpha package is installed, add the DelphaUpgrade258 package (unmanaged) to your org. It will facilitate the migration process.

    • Package Id: 04tRl000001EAVBIA4

    • Package URL : /packaging/installPackage.apexp?p0=04tRl000001EAVBIA4

Once the upgrade package is installed, open a developer console and run the script below.

Connect the org to Delpha

Connect your Salesforce org to Delpha by using the Delpha Setup app and configuration tab. Fast integration in just a few clicks to enable full platform functionality.

Connecting Your Salesforce Org to Delpha

To link your Salesforce organization with Delpha's backend services:

  1. Open the Delpha Setup app in Salesforce

Build 3.58.8 (04tRl000001GhDJIA0)

Apply the package

If you are upgrading from a version below 3.58, you must run the

Install Delpha

Installing Delpha in Salesforce

To get started with Delpha in Salesforce, follow these quick setup steps:

  1. from the AppExchange

Build 3.58.5 (04tRl000001FAmTIAW)

Apply the package.

If you are upgrading from a version below 3.58, you must run the

Extra Tasks

Check your Salesforce org settings to optimize the use of Delpha to and install the LinkedIn Enrichment connector for enhanced data insights.

Extra Tasks – Delpha Setup

The Extra Tasks section provides additional configuration options to enhance your Delpha experience:

  1. Check my org settings:

Install Delpha package from the Salesforce App Exchange

Quickly enable Delpha for your Salesforce org with minimal setup.

How to Install Delpha from the Salesforce AppExchange

  1. Log in to Salesforce using an account with system administrator rights.

Assign a Delpha licence to the users

Assign Delpha licenses in Salesforce easily via Installed Packages or directly from user profiles. Ensure your users have access to Delpha features with quick license management.

Assigning Delpha Licenses in Salesforce

You can assign Delpha licenses using either of the following methods:

Delpha Setup

Setting Up Delpha in 3 Easy Steps

The Delpha Setup menu provides quick access to key configuration areas:

  • Install Delpha:

Import Conversations

Import conversations into Delpha to enable advanced data quality and deduplication use cases. Select recommended components for full feature coverage and smarter data management.

Importing Conversations into Delpha

For an initial setup, the conversations are automatically imported by applying the step Delpha Conversations in the Delpha Integration section of the Delpha Setup

Up to Build 3.50.6

For Delpha versions later than 3.50.6,

Build 3.58.7 (04tRl000001GPzZIAW)

Apply the package

If you are upgrading from a version below 3.58, you must run the

Delpha Data Steward – Access to Data Quality App, Score Meter, and Bot

  • Delpha User – Access to Score Meter and Bot only

  • Go to the Delpha Configuration tab

  • In the First Steps section, click Connect

  • A new window will open—follow the prompts to authorize and complete the connection

  • Once connected, Delpha can begin syncing data and enabling core features.

    The profile and permissions of the user that performed the connection are going to be used by Delpha. Make sure the user has an administrator profile and will keep the Delpha Licence and Delpha Admin permissions.

    • We recommend using a dedicated 'technical' user with Admin rights for that step.

    • This user should not be reused when connecting Sandboxes to Delpha. Using the same user to connect sandboxes will overwrite the current settings. In other words, you will disconnect from Delpha the org (prod or sandbox) where this user has done the initial connection.

    Delpha Technical Setup is done!

    Go to the Salesforce AppExchange and search for Delpha. or use the direct link to Delpha on the AppExchange
  • On the Delpha listing page, click “Get It Now” to begin.

  • Choose your environment (Production or Sandbox) based on where you want to install the package.

  • Log in again if prompted to confirm your identity.

  • Accept the terms and conditions by checking the agreement box.

  • Set the security level, selecting who should have access to Delpha (Admins only, All users, or specific profiles), then click Next.

  • Click “Install” to start the installation process.

  • Once complete, Salesforce will send you a confirmation email indicating that Delpha was successfully installed.

  • During the setup, you are asked to Approve Third-Party Access

    • api.hubapi.com: HubSpot endpoint used by Delpha to synchronize HubSpot and Salesforce records after Delpha merges Salesforce records during the Duplicate process. This integration is disabled by default and can be enabled only by a Delpha Administrator in the Duplicate Settings.

    • mail.delpha.services: Delpha endpoint used by the Email Insight feature to extract business information from incoming emails. This feature is off by default and is activated at the Delpha license level (FMA).

    Option 1: Via Installed Packages
    1. Go to Setup in Salesforce

    2. In the Quick Find box, search for and select Installed Packages

    3. Find Delpha in the list and click Manage Licenses

    4. Click Add Users, select the desired users, and click Add

    Option 2: Via User Profile

    1. Go to Setup > Users via the Quick Find box

    2. Click the name of the user you want to license

    3. In the Managed Packages section, find Delpha and click Assign

    4. Click Save to confirm

    Both methods will properly activate Delpha access for selected users.

    • Do not forget to assign a Delpha license to you

    • This step is useless when installing Delpha on a Sandbox org

    app. Later on, you can reimport or update the conversations following the steps below.

    To import conversations for use in Delpha’s data quality workflows:

    1. Open the Delpha Setup app in Salesforce

    2. Navigate to the Import Conversations tab

    3. Select the components you wish to import

    4. Click Import Data to begin the process

    For full functionality, it’s recommended to include the following components:

    • Version 3.56 and onward: the conversation package Data Quality is no longer needed. All the Data Quality topics being handled in the score meter.

    • Versions 3.60 and onward: most of the data quality and duplicate conversations are managed from the Score meter.

    • DuplicateLeadWD

    • DuplicatePersonAccount

    • LeadVsContact

    • LinkedInEnrichmentAdvanced

    • LinkedInEnrichment

    • Additional information on Delpha Conversations

    • By importing these components you add the Delpha standard conversations to the org. They are all listed in the app Delpha Setup below the Conversation Builder tab.

    Delpha Data Quality: Improve and maintain data health with dimensions and recommendations

  • Delpha Campaigns: Configure, run, and optimize campaign pipelines

  • Initial configuration steps
    Update your Delpha version safely
    Overview and usage of app-specific features
    Guide to configuring specific use cases (Duplicate, Data Quality)
    Launch and manage enrichment campaigns
    Add components, fields, and tokens to layouts
    Display and use job history, detect job changes
    Manage cookie setup, enrichment, connection troubleshooting
    All about deduplication — rules, merge logic, detection tuning
    Securely allow the support team to access your org to help you troubleshoot or complete setup.
    Connect and integrate with Delpha securely through APIs and MCP
    migration script
    Assign the Delpha Permission Set Group to users
  • Allocate Delpha licenses to the right users

  • Connect your Salesforce org to Delpha

  • This process ensures Delpha is fully installed, configured, and ready to use for your team.

    Delpha app is a managed package. It can be installed from the Salesforce App Exchange or directly from a package Id.

    Get in touch with Delpha ([email protected]) for further information.

    Install the Delpha package
    migration script

    Install Delpha Connector for LinkedIn Enrichment: Set up the connector to enable LinkedIn-based data enrichment

    These tasks help ensure optimal performance and unlock advanced enrichment features.

    Review key Salesforce org configurations related to Delpha
    Import Conversations: Option to bring Delpha Bot conversation into Delpha
  • Extra Tasks: Additional setup or administrative actions related to Delpha

  • Use this section to complete your initial setup and manage Delpha features within your org.

    Guide for installing and activating the Delpha package in Salesforce
    migration script

    Build 3.71.x

    delpha.DDQ_DuplicateSettingsMigration.quickMigration();
    Upgrade Delpha Using the Release Notes Document

    To upgrade Delpha to a newer version:

    1. Open the Release Notes (external document)

    2. Select the version you want to install and copy the Delpha Package ID

    3. Apply the upgrade using the virtual URL method:

    Replace MyOrgName with your Salesforce org domain and DelphaPackageId with the ID from the document.

    the upgrade steps and new capabilities are in the What's New section.
    https://MyOrgName.lightning.force.com/packagingSetupUI/ipLanding.app?apvId=DelphaPackageId

    Build 3.56 (04tRl000001D4hxIAC)

    From all versions below 3.50.6

    • Reconnect your Org to Delpha: App Delpha Setup / Section: Delpha Integration / Click the Connect button

    • Update conversations: App Delpha Setup / Section: Import Conversation

      • Remove Data: Select All conversation package and click on 'Remove Data

      • Import Data: Based on the use cases you are implementing, select your packages : DuplicateAccountsWD, Duplicate ContactWD, DuplicateLeadWD, DuplicatePersonAccount, LeadVsContact, LinkedInEnrichment, LinkedInEnrichmentAdvanced.

    Do not select the package Data Quality as the corresponding .

    • pairs following these steps

      • delete current scheduled tasks involving the Apex class: DDQ_DuplicateRecordAutoMerge

      • from the app Delpha Setup > Duplicate > Initialization, section Auto Merge Scheduler, select the hours to run the auto merge.

    • Apply a migration script.

    This script updates the existing Duplicate Expressions and Filtering rules and ensure their proper display with the .

    Open the developer console and apply the following script.

    Delpha Upgrade

    Access Delpha’s release notes to upgrade versions using a package ID and virtual install URL. Quickly apply updates in Salesforce by selecting your desired version from the official documentation.

    Step 1: Check what's new

    Step 2: Apply the upgrade

    Add this segment to your org url.

    /packaging/installPackage.apexp?p0=VersionId

    Step 3:

    From a side release update package

    If some scripts must be applied for compatibility topics between versions of Delpha, a side release package and a 'how to' will be provided in the release notes of the target build.

    From Delpha Setup app

    • Open the Delpha Setup app and select the tab Delpha Configuration

    • In the section First Steps, consider the Review Configuration block You will find here all the items that needs a manual update with enough information for a quick application.

    • Once the updates are done, refresh your page. The section should only display green ticks.

    Build 3.58.x

    What to do when you upgrade to a 3.58.x build

    Upgrade Steps from any version previous 3.58.0

    • Apply the package

    • After the main Delpha package is installed, add the DelphaUpgrade258 package (unmanaged) to your org. It will facilitate the migration process.

      • Package Id: 04tRl000001LuppIAC

      • Package URL : /packaging/installPackage.apexp?p0=04tRl000001LuppIAC

    Once the upgrade package is installed, open a developer console and run the script below.

    Perform Upgrade tasks

    Build 3.56

    New Score Meter: Review & Fix Everything in One Place

    The Score Meter has been redesigned to simplify your workflow and make issue resolution faster and more intuitive:

    • Before: You had to switch between the Score Meter and the Bot to review and apply corrections.

    • Now: Everything happens directly in the Score Meter — review, select, and apply corrections all in one place.

    • New interface: Cleaner, clearer, and optimized for batch actions. You can now apply changes to 1 / some / or all suggestions with just a few clicks.

    No more back and forth. Just smarter data review in a single streamlined experience.

    Try it out now and speed up your remediation process!

    Build 3.60.7

    • Add missing permission set for duplicate merge editor.

    Build 3.56

    New Data Steward View – Improved Usability & Customization

    We’ve redesigned the Data Quality Steward View and the Duplicate Steward View interface to align with Salesforce’s native List View experience:

    • Familiar Navigation: Use the standard cog and filter icons to create, filter, and manage your views—just like any Salesforce list.

    • View Sharing: Create custom views and share them with your team for easier collaboration.

    • Field Flexibility: Choose any fields to display—making data analysis faster and more intuitive.

    This update simplifies navigation, improves usability, and gives you more control over your quality review workflows.

    Build 3.60.6

    Fix some display issued on Cross Merge Field Rules.

    Build 3.58.2

    Legal Id types

    2 new Legal Ids types are supported by Delpha : Australia and New Zealand

    LinkedIn enrichment cleanup

    If you remove the D LinkedIn URL from your record (Account or Contact), all related information is deleted from Delpha fields, now including the logo / picture profile.

    Validation Rules

    Validation rules can act as a blocker for Data Quality.

    When a record is updated by Delpha in the Data Quality process (assessment or recommendation phases) it must follow the validation rules or the update will be blocked.

    • When it happens in a mass assessment process (Automation, Campaign, Data Steward mass update...) the record is detected and blacklisted in the Delpha Setup > Tab: Locked Records until a Delpha Admin deletes the entry (and takes proper actions to avoid the validation breach again).

    • When it happens in a single enrichment phase, using the Score Meter, a warning message is displayed to the user so he knows that his record cannot be updated and why.

    Build 3.60.7

    • Score Meter

      • Fix tooltips not displaying for bullets

      • Yellow bullet for Status = Unknown is now a triangle

      • Display LinkedIn title instead of LinkedIn name

    Build 3.58.6

    This build introduces some enhancement in the display of the Duplicate Data Steward pairs. Loading time is divided by 2.

    Build 3.70.0

    Negative view for tiles

    Add "Last Modified Date" column to the steward

    Implement filtering for data steward views (Data Quality and Duplicate)

    Data Steward Views

    Delpha’s updated Data Steward View offers a fully customizable, Salesforce-native experience. Easily filter records, choose the fields you want to see, and create or share your own views.

    Build 3.60.6

    Bug Fix: incomplete Legal ID

    Legal address was missing the street part. This is fixed.

    Build 3.60.4 (04tRl000001IyUzIAK)

    Apply the package

    Delpha Setup

    Explore all the latest updates to the Delpha Setup app here.

    Duplicate

    Explore all the latest updates to the Delpha Duplicate use case here.

    Build 3.58.8

    Bug Fix: Filtering with Select All

    Previously, when applying a text filter in the Data Quality or Duplicate Data Steward views, the Select All action was incorrectly applied to all records instead of only the filtered results. This issue has been resolved in this release.

    Build 3.60.6 (04tRl000001K4lFIAS)

    Add this segment to your org url.

    /packaging/installPackage.apexp?p0=04tRl000001K4lFIAS

    Build 3.60.7 (04tRl000001LB7xIAG)

    Add this segment to your org url.

    /packaging/installPackage.apexp?p0=04tRl000001LB7xIAG

    conversations have been integrated to the Score Meter
    Set the automatic merge schedule for Auto Yes and Steward Yes
    new Duplicate Settings layout
    delpha.DDQ_DuplicateSettingsMigration.quickMigration();
    List<delpha__DDQ_DuplicateObject__c> dupObjs = [SELECT Id, Name, delpha__Expression__c FROM delpha__DDQ_DuplicateObject__c];
    for(delpha__DDQ_DuplicateObject__c dupObj : dupObjs) {
        String expRuleStr = dupObj.delpha__Expression__c;
        System.debug('Current Rule: ' + expRuleStr);
        
        if(String.isBlank(expRuleStr) || !(expRuleStr.startsWith('[[') && expRuleStr.endsWith(']]'))) { //check here if expRule is in old format (field is not filterable in query)
            continue; //skip if already in new format
        }
        
        List<Object> expRuleList = (List<Object>) JSON.deserializeUntyped(expRuleStr);
        List<Map<String, Object>> newExpRules = new List<Map<String, Object>>();
    	Integer i = 1;    
    	for(Object rule : expRuleList) {
            Map<String,Object> newRule = new Map<String, Object> {
                'name' => 'Rule ' + i, 
                'rules' => rule
            };
            newExpRules.add(newRule);
            i++;
        }
        System.debug('New Rule: ' + JSON.serialize(newExpRules));
        dupObj.delpha__Expression__c = JSON.serialize(newExpRules);
    }
    Database.update(dupObjs);

    (Optional) Activate Delpha Licenses purchased via Heroku Marketplace

    Follow these steps to activate Delpha licenses purchased through the Heroku Marketplace and set them up on your Heroku account.

    If you purchased Delpha through the Heroku Marketplace, follow these steps to activate your licenses. If you’re a direct customer, you can skip this section.

    Set up a Heroku app with the Delpha Data Quality add-on to activate the licences.

    Prerequisites

    • You have access to an Enterprise Account, directly setup with the Heroku Team.

    This Enterprise Account is set at Heroku contract signature. The Tenant Owner receives an email from Heroku to activate the account. If you think that you did not receive this email, liaise with your Heroku account manager.

    • If you are activating Delpha Licenses on a Personal Account, the process is the same. Make sure that billing information is set up (required for paid add-on).

    Step-by-step

    1 - Log in your Heroku Account

    • Go to and sign in.

    • Switch to your Enterprise Account If the top-left account switcher, displays Personal, click on it and select a Team within your Enterprise Account

    If it is the first time you log in your Heroku Enterprise Account, you may have no team created under your Enterprise Account. You should create one for easier access management to the Delpha resources on Heroku.

    2 - Create a new app

    • Go to the tab Apps and click Create new app.

      • App name: use something meaningful, e.g. your-companyname-delpha-heroku-licence (must be globally unique).

      • App Owner: select your Team.

    3 - Add the Delpha add-on to the newly created App

    Case 1: you are on a Custom Plan

    • Using Heroku CLI, copy paste the command from your Custom Plan email. It will add Delpha Data Quality add-on to the app you just created and associate it with the Custom Plan.

    If Delpha has created a Custom plan for your company, you received an email titled Heroku - You have been invited to install delpha-data-quality:NameOfTheCustomPlan sent by [email protected] with this command line.

    If you did not receive this email or if you do not know what to do with it... add Delpha Support with email address [email protected] to your Heroku Team so we can manage the Custom plan activation for you.

    To add a Team Member on Heroku, just follow these steps: in your Heroku account: Select your Team / go to the Access tab / click 'Invite User'.

    Case 2: you are on the Standard plans

    • Open your new app and go to the Resources tab.

    • In Add-on Services section, search Delpha Data Quality and select it.

      • Plan Name: choose Pro.

    Final check

    You should now see the Service Delpha Data Quality under Add-on Services section with a Plan selected.

    Licences are now active for this Heroku app. You can start using Delpha.

    Build 3.70.0 (04tRl000001NAirIAG)

    Add this segment to your org url.

    /packaging/installPackage.apexp?p0=04tRl000001NAirIAG

    Check What's New section

    • Delpha Setup

    Build 3.58.2

    Direct access to filters

    Based on the users feedback, we improved the Data Steward view by having the most common filters back on the main data steward screen area.

    Data Quality

    You can directly select the Object and the field from the main screen. To access the extra filtering capabilities, click on the filter logo.

    Duplicate

    You can select the Object and the processing state (True or False). To access the extra filtering capabilities, click on the filter logo.

    Use Cases Setup

    Use Delpha’s Use Cases Setup to configure data quality and duplicate detection rules in Salesforce. Tailor each use case to meet your business needs and maintain clean, reliable CRM data.

    Use Cases Setup Menu in Delpha

    The Use Cases Setup menu allows administrators to configure key operational workflows in Delpha:

    • Duplicate – Set up rules and automation to detect and manage duplicate records across Salesforce objects.

    • Data Quality – .

    These options ensure your Salesforce org is equipped to handle both duplicate management and ongoing data health monitoring.

    Delpha Data Quality

    Use Delpha’s Data Quality and Duplicate Steward views in Salesforce to monitor record quality, apply intelligent recommendations, and resolve duplicates efficiently.

    Delpha Data Quality Menu Overview

    The Delpha Data Quality section provides dedicated views for data stewards to monitor and improve the quality of records in Salesforce:

    • Data Quality Steward View – Review, validate, and apply field-level recommendations across Accounts and Contacts

    • Duplicate Data Steward View –

    These views help ensure data accuracy, unicity, and consistency across your CRM.

    Access to the app is granted only to users with the Delpha DataSteward Permission Groupr

    Build 3.60.1

    You can assess selected records directly from the Data quality Steward view.

    If you click on the Assess button, all selected records will be Data Quality assessed. This feature is compatible with the Select All, allowing mass reassessment from the Data Quality Steward View.

    Build 3.58.5

    Account - Main Entity Address

    When enriching an Account, you retrieve the Main Entity address in the tab Delpha > Address. You can reuse this information in a regular address (billing, shipping...).

    Note that this address can be different from the Legal Address.

    Account Industry

    .

    Duplicate Merge

    Use Delpha’s Duplicate Remediation settings to automate and control duplicate merges. Configure object-level rules and field-level logic to ensure clean, reliable data consolidation.

    Duplicate Merge Menu in Delpha

    The Duplicate Merge section helps define how merges are executed after duplicate records are detected. It includes:

    • Merge Object Rules Section – Configure global merge logic and thresholds for specific objects (e.g., Account, Contact).

    • Merge Field Rules Section – , such as which value to keep (e.g., master, most recent, highest score).

    These settings allow you to control both which records get merged and how field values are resolved post-merge.

    Duplicate Cases - Email to Case

    Email-to-Case Duplicate Management keeps Salesforce clean by detecting and merging duplicate cases from emails.

    Email-to-Case Duplicate Management helps avoid clutter when multiple emails create duplicate cases for the same issue. It detects and merges duplicates, consolidates information, and keeps case handling efficient and consistent.

    • Duplicate Detection – Configures how the system identifies potential duplicate cases (e.g., rules, filters, and thresholds).

    • Duplicate Merge – Defines how duplicates are resolved, including merge strategies, parent assignment, and field inheritance.

    • Run the initial assessment – .

    Initialize the default settings

    Initialize default duplicate settings in Delpha to enable record deduplication in Salesforce. Quick setup with customizable rules for accurate and scalable duplicate detection.

    How to Initialize Default Duplicate Settings in Delpha

    To prepare Delpha for duplicate detection, follow these steps:

    1. Open the Delpha Setup App in Salesforce

    2. Go to the Delpha Configuration tab

    3. Scroll down to the Duplicates section

    4. Click the Initialize button to load default settings

    Once initialized, you can review and customize these settings from the within the Delpha Setup menu.

    Check my org settings

    Ensure your Salesforce org settings are properly set to get the best of Delpha

    (Mandatory)

    Starting in early September 2025, Salesforce blocks end users from authorizing or using uninstalled Connected Apps. Only apps that are explicitly installed (or users with special permissions) will work. ()

    Build 3.70.x

    Upgrade Steps from any version previous 3.63.0

    • Apply the package

    • After the main Delpha package is installed, add the DelphaUpgrade363 package (unmanaged) to your org. It will facilitate the migration process.

    Build 3.56

    More Logical Sidebar Organization

    in the App Delpha Setup, the left-hand menu is now grouped by functional categories (e.g., Data Quality, Duplicates, Conversations), making navigation more intuitive and setup tasks easier to locate.

    Build 3.56

    Single stop for Duplicate setup

    All the settings are now available in one single place, in the Duplicates section of the Delpha Setup app.

    Visual Rule Builder for Duplicate Management

    Delpha Setup

    Configure and customize your Delpha experience in Salesforce with tools for Use Case setup, conversation management, and flow building.

    Delpha Setup Overview

    The Delpha Setup sectionb gives you access to key configuration tools:

    • Delpha Configuration –

    What's New

    This section helps users quickly access the latest improvements across the platform.

    The "What's New" section is organized by key feature areas, making it easy to browse recent updates and improvements. Each item links to a dedicated page summarizing the latest changes and enhancements for that component:

    • Delpha Setup – .

    • Duplicate – .

    • Data Quality

    Delpha configuration

    Customize Delpha for Salesforce with configuration tools for data quality, deduplication, normalization, and default values—accessible via the Delpha Setup app.

    Delpha Configuration Overview

    The Delpha Configuration section centralizes all key setup options to tailor the platform to your org’s needs:

    • First Steps –

    Token Usage

    Monitor Delpha token and duplicate credit usage in real time. Track consumption, reset dates, and usage limits to optimize your subscription and avoid overages.

    Delpha Token Usage Overview

    The Token Usage screen in Delpha gives you full visibility into your current usage of tokens and duplicate credits. It helps you track consumption and manage your subscription resources effectively.

    Build 3.71.0

    UI - UX

    Sections on Duplicate Setup (App Delpha Setup > Duplicates > Detection Settings) have been reorganized.

    Properties section

    Delpha’s Duplicate Detection Properties section lets you configure AI thresholds, filtering rules, screening fields, and auto-merge logic for accurate deduplication.

    Duplicate Detection – Properties Section in Delpha

    The Properties section of the Duplicate Detection setup allows you to fine-tune how Delpha identifies and processes duplicate records. Each setting plays a critical role in the logic and accuracy of detection.

    Build 3.71.0 (04tRl000001NF4DIAW)

    Add this segment to your org url.

    /packaging/installPackage.apexp?p0=04tRl000001NF4DIAW

    Check

    Job Tracker

    Configure Delpha’s Job Tracker to monitor job changes and manage contact movements. Match accounts by ID or name, auto-create missing accounts and automate contact updates when job shifts are detected

    Job Tracker Configuration in Delpha

    The Job Tracker allows Delpha to track job changes for Contacts and enrich your Salesforce data by identifying movements across companies. It includes flexible automation settings for account matching, new account creation, and contact movement management.

    Build 3.70.0

    [Ultimate]

    • App Delpha Setup > Data Quality > Account

    Once the Ultimate toggle is activated, you can manually trigger a reassessment of the Ultimate analysis.

    Default Values

    Set default field values in Delpha for Account, Contact, and Lead creation. Ensure required fields are always filled to prevent Salesforce validation errors and streamline automated record creation.

    Default Values Configuration in Delpha

    The Default Values screen allows you to predefine field values for Accounts, Contacts, and Leads. This ensures smooth record creation and compliance with Salesforce validation rules by automatically filling in required fields.

    Master Record Selection

    Delpha’s Master Record Rule helps you define which duplicate to keep during merges. Choose from built-in rules -oldest, latest, or most-filled...- to ensure accurate and complete Salesforce data.

    Master Record Rule in Delpha

    To define which record survives during a merge, Delpha uses Master Record Selection Rules.

    Run your first duplicate detection

    Start your first Salesforce duplicate detection in Delpha by clicking "Evaluate." Review results in the Duplicate Steward View to manage and clean duplicate records efficiently.

    Run Your First Duplicate Detection in Delpha

    To launch your first duplicate analysis:

    1. Click the "Evaluate" button to initiate the detection process.

    Build 3.58.2

    Suggested Discard Value

    Form now on, Delpha performs an analysis on your targeted duplicate population and proposes you to discard in one click all values that may trigger too much pairs. Thsi information is displayed in the app Delpha Setup > Duplicate > Object Settings, in the Properties section of each object.

    You can

    Setup

    Set up Delpha’s duplicate management by initializing default settings and activating auto merge. Automate the detection and resolution of duplicate Salesforce records with confidence-based logic.

    Duplicate Setup Options in Delpha

    The Setup section for duplicate management includes:

    • Initialize the Default Settings – Prepares Delpha’s , including merge rules and scoring thresholds

    Duplicate detection

    Configure duplicate detection in Delpha by adjusting properties and field-level match logic. Ensure smart, accurate duplicate identification using customizable rules.

    Duplicate Detection Setup in Delpha

    The Duplicate Detection menu lets you fine-tune how duplicates are identified in your Salesforce org. It includes two configuration areas:

    • Properties Section – Define the core settings for including object type, thresholds, and merge logic.

    Delpha Apps

    Access key Delpha apps in Salesforce, including Setup, Data Quality, and Score Meter, to streamline configuration, monitor data health, and optimize data-driven decisions.

    Delpha Apps Overview

    The Delpha Apps section in Salesforce gives you access to the core components of the Delpha platform:

    • Delpha Setup –

    Run the initial assessment

    To run your first check for existing duplicate cases, simply click the Launch Assessment button at the top of the Email-to-Case settings.

    • If the button is not visible, it means the initial assessment has already been executed.

    Build 3.60.1

    Manage Duplicate from the Score Meter

    The Score Meter now includes the Duplicate information for Accounts and Contacts. By clicking on the link you start the

    Improved “Connect to Delpha” Mechanism

    Previously, Delpha asynchronous operations were executed either:

    • on behalf of the user who connected the org to Delpha, or

    • via the Salesforce Automated Process user, which introduced several limitations:

      • No clear audit trail for changes made by Delpha

      • Inability to assign Permission Set Groups to the Automated Process user

      • Reduced visibility and control for admins

    ✅ Now, a dedicated named user is explicitly selected during the setup. All actions performed by Delpha will consistently appear under that user’s name, providing:

    • Clear traceability of changes

    • Full permission customization and access control

    • Alignment with Salesforce best practices for automated systems

    When upgrading to version 3.53.x or later from 3.50.x or earlier, you will need to reconnect Delpha as part of the setup process.

    Faster Setup

    • No email activation required: You no longer need to Activate Delpha sending an email to activate core features, simplifying the onboarding process.

    • Conversations are now automatically imported once Delpha is connected, eliminating the need for manual setup steps.

    Locked Records tab

    Salesforce Validation Rules set on a record can fire an error and prevent Delpha from updating it. When this happens in a batched process, the whole batch is rejected. The system now more reliably handles these situations to minimize disruption in workflows by catching the error and logging the record ans the error message in the Locked Records table so you can take care of it later. This allows the other members of the batch to be properly updated.

    A locked record is ignored by Delpha Data Quality as long as it is listed. You must delete the entry from the Locked Record table to let Delpha process the records.

    Key Sections:
    • Usage Reset Date Shows the next reset date for your token and credit usage (e.g., 2025-02-15), marking the start of a new billing or allocation cycle.

    • Tokens

      • Progress Bar: Visual indicator of how many tokens have been used

      • Current Usage: Displays used vs. total tokens (e.g., 22,030 / 1,000, or 2,203% usage)

    • Duplicate Credits

      • Progress Bar: Visual progress on duplicate credit consumption

      • Current Usage: Shows used vs. available credits (e.g., 4,528 / 10,000, or 45% usage)

    This page helps you stay in control of your consumption and avoid overages.


    Key Takeaways for Users:

    • Regularly monitor this screen to avoid exceeding your plan’s limits.

    • If your token or credit usage is consistently high, consider upgrading your plan using the "Change Plan" button.

    • Keep track of the usage reset date to plan resource-intensive tasks effectively.

    Key Configuration Sections
    • Account Default Values

      • Action: Use Add New Field to define defaults (e.g., Industry, Account Type, Region)

      • Purpose: Prevent errors during Account creation due to missing required fields

    • Contact Default Values

      • Action: Add defaults for fields like Email, Phone, or Job Title

      • Purpose: Ensure Contact records are created with all mandatory info

    • Lead Default Values

      • Action: Set fields such as Lead Source, Status, or Company Name

      • Purpose: Avoid issues during Lead creation where validation rules apply

    These settings are critical for the Job History use case as you can be proposed to create a new account or a new contact.

    How it works:
    1. Open the Delpha Setup App and go to the Duplicate Settings tab.

    2. By default, Delpha selects the oldest record as the master and fills any empty fields with values from the duplicate. This ensures completeness and consistency in the final, merged record.

    Built-in Master Record Selection Rules

    Rule

    Description

    Oldest created date

    Selects the record with the earliest creation date

    Latest created date

    Selects the most recently created record

    Oldest modified date

    Selects the record with the earliest last update

    Latest modified date

    Selects the record with the most recent update

    Most Filled

    Selects the record that has the most populated fields

    These rules help you tailor your merge logic to preserve the most reliable or relevant data.

    Once the analysis is complete, you can view the identified potential duplicates in the Delpha Data Quality App, under the Duplicate Steward View tab.

    This view lets you review, validate, and take action on the suggested duplicate records.

    Duplicate
    Data Quality
    Data Steward View
    Define and customize how Delpha evaluates field-level data quality based on business needs
    Identify, review, and merge duplicate records with Delpha's smart deduplication assistant
    From now on, Delpha provides the Account Industry. It is retrieved in a Delpha field, in the Account Profile tab
    Customize field-level merge behavior
    Executes a first pass of the duplicate detection process to evaluate existing cases against the configured rules
    Duplicate section
    Why Delpha is impacted

    Delpha’s Connected App (DelphaAssistantV2) is not installed with the Delpha Assistant package. That makes it an uninstalled application. New users attempting to connect LinkedIn through Delpha will fail until the app is installed (or the user has a bypass permission). (Salesforce)

    Case 1 — The user doing the Delpha connection has the System Administrator profile

    1. In Setup, open Connected Apps OAuth Usage (Quick Find → “Connected Apps OAuth Usage”). (Salesforce)

    2. Locate DelphaAssistantV2.

    3. In Actions, click Install (you’ll typically also see Block beside it).

    4. Confirm installation. After this, end users can authorize via Delpha normally.

    Tip: In this list, an app showing “Install” is not yet installed; one showing “Uninstall” is already installed.

    If you are using a Delpha version below 3.62, you will have to apply the same remediation to the connected app DelphaApp

    Case 2 — The user doing the Delpha connection isn’t a System Administrator

    1. Create a temporary Permission Set that grants the system permission: Approve Uninstalled Connected Apps. (Salesforce Admins)

    2. Assign this Permission Set to the user who will perform the install.

    3. Have that user repeat Case 1 to click Install on DelphaAssistantV2.

    4. Remove the temporary Permission Set after installation.

    If you are using a Delpha version below 3.62, you will have to apply the same remediation to the connected app DelphaApp

    Notes & validation

    • Existing users who previously authorized an uninstalled app may continue working in some cases, but new authorizations are blocked unless the app is installed or the user has the new permission.

    • If “Install” isn’t visible, you may already have the app installed (you’ll see “Uninstall” instead), or you’re not viewing from an account with rights to install.

    • To double-check, open Connected Apps OAuth Usage, select the app, and review Manage App Policies. (Salesforce)

    Lightning Web Security: activated (Mandatory)

    To activate the Lightning Web Security feature in Salesforce:

    1. Access Setup: Click on the gear icon and select "Setup."

    2. Locate Session Settings: Enter "Session Settings" in the Quick Find box.

    3. Enable Lightning Web Security: Scroll to find the "Enable Lightning Web Security" option and check the box.

    4. Save Your Configuration: Click "Save" to ensure the settings are applied.

    In newly created Salesforce orgs, the LWS feature is activated by default.

    If you do not activate it, the display of the all the LWC components in the org will be too slow to allow a good user experience.

    Delpha's data steward views are LWC components.

    Adopt updated CSP directives: unchecked (Mandatory)

    To deactivate the Adopt updated CSP Directives setting in Salesforce:

    1. Access Setup: Click on the gear icon and select "Setup."

    2. Locate Session Settings: Enter "Session Settings" in the Quick Find box.

    3. Adopt updated CSP directives: Scroll to find the "Adopt updated CSP directives" option and uncheck the box.

    4. Save Your Configuration: Click "Save" to ensure the settings are applied.

    If this option remain selected, some links provided by Delpha (such as Company logo) will not display properly and will appear as broken links.

    Make sure all Delpha users can access User External Credentials Object (Mandatory)

    Delpha relies on OAuth for secure authentication that's why, to use Delpha features, the users must be able to access the User External Credentials Object.

    To activate this access:

    • Option 1: For a permission set, under Apps, click Object Settings, and then click User External Credentials.

    • Option 2: For a profile, scroll to Standard Object Permissions and then select User External Credentials.

    (Salesforce)

    If this is not done, users will experience a direct failure when requesting a Data Quality Assessment from the Delpha Score Meter.

    Accounts as Campaign Members: enabled (Recommended)

    1. Access Setup: Click on the gear icon and select "Setup."

    2. Locate Accounts As Campaign Members: Enter "Accounts As Campaign Members" in the Quick Find box.

    3. Enable Accounts As Campaign Members: Select the option "Enable"

    4. Save Your Configuration: Click "Save" to ensure the settings are applied.

    This setting is mandatory if you want to deal with Account Enrichment through Delpha Campaigns.

    Contacts to Multiple Accounts: enabled (Recommended)

    To activate the feature allowing users to relate a contact to multiple accounts in Salesforce:

    1. Navigate to Setup: Click the gear icon and select "Setup."

    2. Search for Account Settings: Use the Quick Find box to locate "Account Settings."

    3. Enable the Feature: Find the "Contacts to Multiple Accounts" option and check the box to enable it.

    4. Save Changes: Click "Save" to apply the changes.

    This setting is recommended when dealing with contacts belonging to different accounts.

    Install the Delpha Connected Apps
    Salesforce

    Token Usage – Track API token consumption

  • Data Quality - Account / Contact – Configure field rules and quality scoring

  • Duplicates – Manage deduplication logic and thresholds

  • Job Tracker – Define rules to apply when a job change is detected

  • Default Values – Set fallback values when a record is created by Delpha

  • Initial connection
    What's New section
    Duplicate
    accept the recommendation by clicking on the Discard Value button. That will add the string to the Discard Values section.
  • ignore the recommendation

  • With Delpha, you can chose to discard and ignore some labels which values are not accurate and can lead to useless extra processing or false positives.

    Activate Auto Merge – Enables automatic merging of duplicate records based on confidence scores and predefined rules

    These initial steps are essential for enabling Delpha’s smart deduplication workflows in Salesforce.

    default configuration for duplicate detection

    Fields Section – Select and configure which fields (e.g., Name, Website, LinkedIn) are compared to evaluate potential duplicates.

    These settings give you precise control over the logic used for deduplication, enabling more accurate and tailored detection strategies.

    how Delpha detects duplicate records,

    Delpha Data Quality – Monitor and resolve data issues like duplicates, missing fields, or invalid values

  • Delpha Score Meter – View and track data quality scores across your org for better decision-making

  • These apps work together to ensure powerful data governance and enrichment within Salesforce.

    Configure your org, connect to Delpha, and manage permissions
    If you change any setting that affects the analysis scope (such as Assessment Period or Case Filters), you’ll be prompted to reassess the cases when saving (Save & re-assess Cases).
    Duplicate Merge process.

    Conversation Builder

    Build smart, no-code conversational workflows with Delpha’s Conversation Builder in Salesforce. Guide users with interactive Q&A and automate business logic all within a visual decision-tree interface

    All the conversations available in your org are listed here.

    From here, you can edit existing conversation or create new conversations.

    Build 3.60.4

    Fix some limitations related to the Auto Number fields when used in Expression or Filtering rules.

    Activate Auto Merge

    Delpha merges Salesforce duplicates via AI score, steward validation, or bot confirmation. Set up a daily Apex job to automate approved merges and streamline CRM cleanup.

    How Duplicate Pairs Are Merged in Delpha

    Delpha offers three ways to merge duplicate record pairs automatically or manually:

    1. Auto Merge via Score

      • If the pair score exceeds the Auto Merge Threshold, the status is set to Auto Yes and merged automatically.

    2. Merge Confirmed by Data Steward

      • If a data steward validates the pair from the Duplicate Data Steward View, the status becomes Steward Yes, triggering an automatic merge.

    3. Merge via Conversation Bot

      • When the duplicate is confirmed by the user through a Delpha conversation, the status changes to Bot Yes, and the merge is performed immediately after clicking the Merge button.

    Enable Scheduled Merge Job

    In the Duplicate Initialization section of the Delpha Setup app, select at what time you want the Auto Yes and Steward Yes pairs to be processed daily.

    In the Auto Merge Scheduler:

    • You can select multiple times in the day

    • The time display in the picklist is your Salesforce Local Time.

    You can set as many Merge scheduled jobs as you want to match your needs.

    First Steps

    Connect your Salesforce org to Delpha, review configuration health, and optimize batch size settings for the Ultimate Account use case. Ensure smooth setup and maximum performance.

    First Steps section

    Connect to Delpha

    Establish a secure connection between your Salesforce org and Delpha's backend. This may require authentication and enabling API access. If not connected, follow the prompts to complete the setup.

    Review Configuration

    Check for any missing or incorrect settings. If issues are detected, Delpha provides step-by-step instructions for remediation to ensure proper functionality.

    Ultimate Account Batch Size

    Defines how many accounts are processed per batch in the Ultimate Account use case. A green check indicates the correct setting. If not, follow the recommended adjustments to optimize batch processing.

    Data Quality

    Explore all the latest updates to the Delpha Data Quality use case here.

    Beta Features

    Build 3.70.0

    First draft of the new create account / create contact use cases

    –
    .
  • Data Steward Views – Changes in how data stewards can manage, filter, and act on data.

  • This structure helps users quickly find what’s relevant to their role or workflow.

    Note that if a version does not impact one of the Delpha components it will not be listed in the corresponding section.

    Updates related to initial configuration and global settings
    Enhancements to duplicate detection and resolution workflows
    Improvements in data assessment and cleaning functionalities

    Location: choose the closest (e.g., Europe or United States).

  • Leave “Pipeline” inactive.

  • Click Create app.

  • Make sure that the Delpha Support team member has add-on provisioning rights.
    Click Submit Order Form to provision the add-on.
    https://dashboard.heroku.com/
    • Package Id: 04tRl000001JK45IAG

    • Package URL : /packaging/installPackage.apexp?p0=04tRl000001JK45IAG

    Once the upgrade package is installed, open a developer console and run the script below.

    • If you use a boolean field (e.g., Do Not Assess) to exclude certain records from duplicate detection, make sure to update your detection scope in App Delpha Setup > Duplicate > Detection Settings, under the Record Filter section.

    If you skip this configuration, the duplicate analysis will run on all records, which may consume more credits than intended.

    delpha.DDQ_MultiDuplicateSettingsMigration.executeMigration();
    heroku addons:create delpha-data-quality:CUSTOM_PLAN_NAME --app YOUR_APP_NAME_HERE
    We’ve redesigned the Duplicate Settings interface to make it more intuitive and user-friendly.

    Before: Managing duplicate filtering and matching logic required editing complex JSON structures manually.

    Now:

    Filtering rule editor
    • Filtering rules are applied from Top to Bottom. Once a rule is applied the filtering processing stops.

    • You can reorder the rules by drag / drop. We recommend packing the 'Keep' rules at the end of the list, after all the 'Discard' rules.

    Direct Match rule Editor (Expression)

    With the new visual rule builder, you can:

    • Define Filtering Rules and Matching Expressions using clear, editable blocks.

    • Instantly see and adjust logic with intuitive field comparisons (e.g., “if BillingCity is not the same…”).

    • Remove the risk of syntax errors—no more editing raw JSON!

    • Enjoy a more organized layout for thresholds, filters, and expressions.

    Existing rules have been migrated automatically—just open the new interface to start using it right away.

    Conversations – View and manage imported conversation components

  • Conversation Builder – Customize and create new conversation flows

  • This section is essential for Delpha Administrators managing Delpha integration and workflows.

    Access to the app is granted only to users with the Delpha Admin Permission Group

    Manage connection, data quality and Duplicate setup
  • Define the filtering rules to apply on top of the duplicate detection (exact match, discard, comment)

  • Define advanced optional settings.

  • Define the scope for these duplicate settings
    Define the fields involved in the duplicate detection process
    Key Configuration Fields
    • AI Threshold Minimum confidence score for a pair to be flagged as a potential duplicate.

    • Auto Merge Threshold Score from which records will be automatically merged without user review.

    • Expression - Direct Match rules The initial condition to detect potential duplicates. Think of it as a formula requiring exact matches between specific fields (e.g., Name + Website).

    • Active Toggle Quickly enable or disable duplicate detection for the object.

    • Post-detection logic that allows you to add comments or discard certain pairs based on specific field-level differences. Example: Discard if cities differ.

    • Filtering rules are applied from Top to Bottom. Once a rule is applied the filtering processing stops.

    • You can reorder the rules by drag / drop. We recommend packing the 'Keep' rules at the end of the list, after all the 'Discard' rules.

    • Screening Fields These are the primary fields (e.g., Name) used to determine if a pair is even worth comparing. If values differ too much, Delpha skips the pair.

    • Discard Values If any key field contains a listed value (e.g., "test", "dummy"), Delpha will ignore it during duplicate scoring. Syntax: comma-separated list with no spaces or quotes — e.g., text1,text2,text3

    By default, the duplicate analysis will apply on all the records of the database. However, you can limit the scope using the Do Not Compare field that as been added to your org, on the targeted objects.

    Duplicate Properties
    Key Configuration Options
    • Match By

      • Description: Defines how Delpha matches accounts between Salesforce and LinkedIn

      • Options:

        • By ID then by Name (default)

        • By ID

        • By Name

      • Purpose: Ensures accurate enrichment by prioritizing LinkedIn ID with fallback to name matching

    • Create New Active Accounts

      • Description: Determines what to do if a contact’s job points to an account not in Salesforce

      • Options:

        • Do Nothing

    • Manage Contact Has Moved

      • Description: Handles how Delpha reacts when a contact has changed companies

      • Options:

        • Do Nothing


    Key Takeaways for Users:

    • Use Match By to determine how Salesforce accounts should be matched with LinkedIn data. The recommended option is "By ID then by Name."

    • Configure Create New Active Accounts to define the level of automation for handling new accounts, from manual prompts to full automation.

    • Adjust Manage Contact Has Moved to decide how contact movements should be handled, with options ranging from no action to automatic updates or contact creation.

    [LinkedIn]
    • App Delpha Setup > Data Quality > Contact > LinkedIn

    If Active, the system will proceed to replace the existing contact title with the new one from LinkedIn, based on the prioritization logic below.

    • None, do not update the title: The system fetches the data but does not push any update to the title field.

    • Only update with the latest Job Title: The system applies the most recent title from the contact's job history.

    • Only update with the Profile Title: The system applies the title listed on the main LinkedIn profile (often the headline).

    • Prioritize latest Job Title, else use Profile Title: The system attempts to apply the latest Job Title first. If it's missing or invalid, it defaults to the Profile Title.

    • Prioritize Profile Title, else use latest Job Title: The system attempts to apply the Profile Title first. If it's missing or invalid, it defaults to the latest Job Title.

    [Duplicate]

    • App Delpha Setup > Data Quality > Duplicate Duplicate settings have been separated into two distinct categories: Detection Settings and Merge Settings.

    • App Delpha Setup > Data Quality > Duplicate > Detection Settings

    All duplicate detection settings are now consolidated within this new section, with parameters grouped by topic into sub-sections.

    Conversations

    Import conversation modules in Delpha to enable automated handling of duplicates, enrichment and data quality via Delpha Bot. Easily manage records and boost data health through guided conversations

    Importing Conversation Modules for Delpha Bot

    To enable conversational features in Delpha, import the relevant modules via the Import Data section and click Import Data. These modules power Delpha Bot’s interactions for handling data quality, duplicates, and enrichment.

    Conversation Modules Overview

    • All imported conversations will appear in the Conversation Builder.

    • To Remove all conversations from a Conversation Module from your org, just select the module and hit Remove Data

    Duplicate

    Delpha’s Duplicate menu helps you set up, detect, and clean duplicate Salesforce records with configurable rules and step-by-step remediation workflows.

    Duplicate Use Case

    The Duplicate section under Use Cases Setup helps you manage the full lifecycle of duplicate detection and remediation:

    • Setup – Configure matching rules, thresholds, and field-level behaviors for duplicate detection

    • Duplicate Detection – (e.g., Account, Contact)

    • Run Your First Duplicate Detection – in Salesforce

    • Duplicate Merge – Define , user actions, and review workflows

    This menu guides you from setup to execution, ensuring a structured and scalable approach to duplicate management.

    We assume that the technical setup of Duplicate has been already done during the

    Duplicates

    Configure Delpha to detect duplicates in Salesforce with scheduled assessments. Enable continuous scans and initialize the detection engine to maintain clean and duplicate-free records.

    Duplicates Management Configuration in Delpha

    The Duplicates section allows you to set up and control how Delpha detects and manages duplicate records in Salesforce. This helps ensure cleaner, more consistent data across your org.

    Key Configuration Options

    • Initialize

      • Purpose: Sets up the duplicate detection engine with default settings

      • Action: Must be clicked to enable duplicate use case

      • Result: Import the standard detection and merge settings.

    Key Takeaways for Users:

    • Start by clicking Initialize to configure the duplicate detection system before enabling specific processes.

    Merge Object Rules section

    Configure Delpha’s master record selection rules and predefined values to automate duplicate merges. Ensure clean, consistent data with flexible merge object logic.

    Merge Object Rules Section in Delpha

    The Merge Object Rules Section lets you define how the master record is selected and how field values are handled when merging duplicates:

    • Master Record Selection – Set the default rule for picking the surviving record (e.g., most recently updated, highest score).

    • Custom Rule for Master Record Selection – using advanced conditions.

    • Default rules for field selection – , ensuring compliance with business rules.

    These rules help automate and standardize merge behavior across all duplicate resolution workflows.

    Default rules for field selection

    Delpha merge field rules ensure high-quality Salesforce data by selecting values based on creation/modification date or data completeness. Choose the best default rule for your duplicate resolution.

    Merge Field Value Rules in Delpha

    Once the master record is selected during a merge, Delpha needs to determine how to choose the final field values. By default, it uses the Master and Not Empty rule.

    Master and Not Empty: The value from the Master record is used unless it's empty—then Delpha uses values from the other record(s) in the duplicate pair.

    Available Field Value Selection Rules

    These rules help ensure Delpha always retains the most complete and relevant data in the merged

    Custom rule for Master Record selection

    Customize duplicate merges with Delpha’s Custom Master Record Rule. Use formula-based scoring to prioritize records and define fall back to creation date for tie-breaking.

    Custom Master Record Rule in Delpha

    If your merge logic needs to follow more advanced or business-specific rules, Delpha allows you to define a Custom Master Record Rule. This approach lets you assign a score to each record in a duplicate pair based on a custom formula and select the one with the highest score as the master.

    How to Create a Custom Rule

    1. Define a Custom Scoring Field Create a formula field (e.g., DC_MasterScoring__c) to assign points based on your business rules.

    2. Example Use Case:

      • If Account Type = Customer → +10 points

    This setup allows your master record selection process to reflect your business priorities precisely.

    More examples about Custom Master selection rules

    Build 3.70.0

    LinkedIn

    Since version 3.70.0, the “Connect to LinkedIn” conversation is no longer used to link your LinkedIn account to Delpha. Connection is now handled through a dedicated UI, which automatically collects the required information from the Delpha Connector Chrome extension.

    Build 3.60.1

    Process Duplicates from the Score Meter & Merge process New UI

    For Accounts and Contacts, processing of Duplicates at record level is now part of the Score Meter. It is no longer done in a conversation but in a dedicated layout.

    Format Delpha Conversation messages

    Formatting rules

    The Delpha messages can contain more than simple texts. By inserting special tags, you can display dynamic and formatted messages. Tags can be used to modify text style, add icons, add images, add hyperlinks, or insert a variable value. The tags can be used on any message displayed to the user such as:

    1. In the builder, via the message/question/answer display text field.

    Create a “Hello” Conversation on Delpha Home Page

    Step-by-step guide to create a “Hello” conversation in Delpha: use Conversation Builder, set display rule, add welcome message, question/answers, and activate.

    Step by step procedure

    Use Case: Recommend a simple "Hello" conversation on the home page. To build this conversation, follow the below steps.

    • From the Delpha Setup app, search Conversation Builder and select it.

    Fields section

    Delpha’s Fields section defines how specific fields are compared to detect Salesforce duplicates. Adjust weights, match types, and rules to improve AI-driven duplicate detection accuracy.

    Duplicate Detection – Fields Section in Delpha

    When no Expression match is found, Delpha relies on the Fields section to evaluate potential duplicates using AI-powered logic. Here, you define how each field contributes to the duplicate scoring process.

    Duplicate Detection

    Email-to-Case Duplicate Detection maps email data to Salesforce fields, applies look-back limits and uses filters to target relevant records—ensuring faster, cleaner, and more accurate case management

    Field Mapping

    When an email is converted into a Salesforce Case, Delpha (and Email-to-Case) map each part of the email to the right Salesforce field.

  • Ask to Create a New Account (default)

  • Create Automatically New Active Accounts

  • Create Automatically and Link Contact to Account

  • Ask to Move (default)

  • Move Automatically When Possible

  • Move Automatically and Update Title

  • Ask to Create a New Contact

  • Create New Contact Automatically When Possible

  • Clean Settings

    • Purpose: delete all existing duplicate settings and revert

  • Continuous Assessment

    • Purpose: Automatically scans for duplicates every 12 hours

    • Frequency Setting: Adjustable (e.g., Twice a day, Never.) via dropdown

  • Configure Continuous Assessments for accounts, contacts, leads, or cross-object duplicates as needed.

  • Use the dropdown menus to adjust how often duplicate assessments run (e.g., daily, weekly, or never).

  • Regularly enabling these processes helps ensure Salesforce data remains accurate and free of duplicates.

  • Filtering Rule
    Customize detection models and criteria per object
    Launch your initial scan to identify potential duplicates
    how Delpha should handle merges
    initial setup.
    If Account Type = Prospect → +5 points
  • If Account Type = Target → +1 point

  • Otherwise → 0 points

  • Set the Custom Rule Expression Use: DC_MasterScoring__c Desc, CreatedDate

    This tells Delpha to:

    • First, select the record with the highest custom score

    • Then use the oldest created date as a fallback if scores are equal

  • Use Case Logic Covered:

    • Customer > Prospect > Target > Oldest

  • simple Master Record selection rule
    advanced Master Record selection rule
    Build custom logic for selecting the master
    Use predefined rules to select fields post-merge
    Key Concepts in the Fields Section
    • Duplicate Field Name The API name of the field being used for comparison (e.g., Name, Website).

    • Weight Determines the importance of the field in the overall match score. Higher weight = greater influence on the duplicate score.

    • Type Specifies the type of matching used:

      • Exact Matching – Compares identical values

      • Fuzzy Matching – Allows for slight variations (e.g., typos, casing) Tip: Click the help link in-app to explore matching algorithm types.

    More info on the matching algorithms.

    • Mandatory When checked, empty values reduce the confidence score for that field. Ensures stronger matches only when relevant data is present.

    • Active Toggle to include or exclude a field from the duplicate detection process.

    More info on the Delpha duplicate scoring

    Address general data quality issues

    /

    Module

    Description

    Comment

    DuplicateAccount

    DuplicateContact

    DuplicateLead

    DuplicatePersonAccount

    LeadVsContact

    Handle duplicates

    WD: The only option is to merge with all related items Information: Merge not allowed with this conversation

    Account Enrichment

    Manage account pipeline enrichment

    /

    LinkedInEnrichment

    Perform standard LinkedIn enrichment

    /

    LinkedInEnrichmentAdvanced

    Advanced LinkedIn enrichment

    /

    Data Quality

    Uses field from earliest update, but skips if value is empty

    Latest modified date & not empty

    Uses field from latest update, but skips if value is empty

    Rule

    Description

    Oldest created date

    Uses the field from the earliest created record

    Latest created date

    Uses the field from the most recently created record

    Oldest modified date

    Uses the field from the earliest updated record

    Latest modified date

    Uses the field from the most recently updated record

    Oldest created date & not empty

    Uses field from oldest record, but skips if value is empty

    Latest created date & not empty

    Uses field from latest record, but skips if value is empty

    Oldest modified date & not empty

    Build 3.58.7

    This version provides a fix on the mass process from the Duplicate Data Steward view: some duplicate records pairs could be deleted before or after being processed

    This issue is only impacting the display of the duplicate pairs. No record is wrongly deleted because of it.

    New LinkedIn connection process

    Dedicated UI: App Delpha Data Quality > Tab Delpha User Settings

    This UI can only be used if the Delpha Connector Chrome extension is installed in your browser.

    If the extension is not installed, or if you prefer to manually set a cookie for a user profile, go to Delpha Setup → User Settings. Then edit the user settings you want to update.

    How to manually retrieve a linkedIn cookie.

    The cookie you enter will be encrypted after saving and cannot be retrieved afterward.

    Notification on score meter when LinkedIn cookie needs to be set

    You can access this page directly, or simply click the alert shown in the Delpha Score component when a configuration issue is detected. Click the red-dot icon to open the Delpha User Settings page instantly.

    Score Meter

    Add address recommendations in score meter

    When an address recommendation is available, it is displayed to the end user in the Score Meter. The user can accept or reject it directly from the Score Meter, based on the data quality analysis and the recommendation’s confidence score.

    Add uniqueness modal to score meter

    For any monitored field, if the unicity value is not equal to 1, you can click the message shown in the score meter to display all records involved in the unicity issue.

    From that window, you can open and review each record.

    Add message/indicator on score meter when record is locked

    Ultimate

    • The comments now explain how the Ultimate Parent was determined and provide the justification for mapping it to an existing account.

    • If the Ultimate Parent does not already exist in your org, the resolution process will automatically create it (score meter or data steward view).

    More info on Ultimate fields and Ultimate Parent analysis.

    The Duplicate standard conversations for Account and Contact are now deprecated. You should remove them from your org.

    3 step process:

    Click on the link and enter the Duplicate process.

    Select the potential duplicate candidate or discard the candidates

    Select the Master record, review and select the data you want to keep and merge

    All the pre-selected values come from the rules set in the Duplicate Merge section of the Duplicate Setup.

    Formatted message displayed on Delpha
    1. In the apex code, while creating dynamic answers.

    Supported Tags

    Insert Variables / Record Links

    Add Variable

    Default or custom variable defined in the builder can be displayed in the bot using the following tags: Tag: {!VariableName} Example: {!CurrentRecordId}

    Display fields associated with a record variable

    Tag: {!VariableName.FieldName} Example: {!CurrentRecordId.Email}

    Display fields associated with the related record

    Tag: {!VariableName.RelatedObject.FieldName} Example : {!CurrentRecordId.Contact.Name}

    The associated records can be accessed by chaining them as shown above, and you can go on like {!CurrentRecordId.Contact.Account.Name}.

    Add Record Link

    Tag: [record Id= value]display text[/record] The value can either be hard-coded or a variable, as shown below: Example:[record id=0031D00000aIxZtQAK]Andy Young[/record] Example:[record id={!targetRecordId}]Andy Young[/record]

    Format text

    Bold Text

    Tag: [b]Bold Text[/b] Example: Discover [b]California[/b]

    Line Break

    Tag: [br/] Example: Discover [br/]London

    Italic Text

    Tag: [i]Italic Text[/i] Example: Discover [i]Prague[/i]

    Underline Text

    Tag: [u]Underlined Text[/u] Example: Discover [u]Paris[/u]

    Add Color

    Tag: [color=value]Colored Text[/color] The value can either be color name or hexadecimal code as shown below: Example: [color=green]Hello World![/color] Example: [color=#FF0000]Hello World[/color]

    Insert Resources / Links

    Add Icon

    Tag: [icon]IconType:IconName[/icon] Example: [icon]standard:announcement[/icon]

    Delpha currently supports Salesforce-Lightning design icons.

    Add Image

    Tag: [img]Image Link[/img] Example: [img]https://delphaimage.png[/img]

    Add Image and adjust width

    Tag: [img]https://img.png[/img][img width=50] Note: Currently, Salesforce doesn't consider the image height attribute added in the tags. However, the image scaling is respected during rendering.

    Add External Link

    Tag: [url]external link[/url] Example: [url]https://delpha.io[/url]

    Add external link to a display text

    Tag: [url=external link]display text[/url] Example: [url=https://delpha.io]AI for Productivity[/url]

    Add an external link to an image

    Tag: [url=external link][img width=50]Image link[/img][/url] Example: [url=https://delpha.io][img width=50]https://img.png[/img][/url]

    For security reasons and to avoid vulnerabilities such as XSS, we only support our tags.

    Click New Conversation on the conversation builder page and enter a name. Append your organization’s name on the trial environment for reference.

    Create a New Conversation
    Name the conversation
    • To start your conversation, click on the grey ‘ + ’ button. Once you click on the first ‘+’ button, a new node for conversation initialization is created.

    • Click on Initialization, select previously created display rule (Hello on Home Page) under Display Rule and Save.

    Conversation Initialization
    • Create a Message, add “Hello” as the welcome message and Save.

    Message
    • Create a question, add “How are you doing?” as the display text and Save.

    Question
    • Create two Answers “Good” and “Okay” and Save.

    Answer 1
    Answer 2
    • The conversation at this point should look something like this.

    Conversation flow
    • Create New nodes under Good and Okay. Add relevant Message to each node

    New Node 1
    New Node 2
    • The completed conversation should look like this. Activate the conversation and test the Hello conversation on the Home Page.

    Final flow

    You must activate the conversation to make it visible to the Delpha Users. Click on the Activate Button

    The email address of the person who sent the email. This is used to identify the Contact or create a new one if needed.

    Case CC List

    D CC Address

    All recipients in the CC of the email are stored here. They can be used to track stakeholders copied on the case. D CC Address is a Delpha custom field.

    Case Subject

    Subject

    The email subject line becomes the case subject. This helps categorize and search cases quickly.

    Case Body

    Description

    The email body (message content) is inserted into the case description so that agents see the original customer message.

    These fields are used for duplicate detection.

    Assessment Period (Days)

    When searching for potential duplicate cases, the system needs to compare each newly created case with past cases. Since both open and closed cases are considered, the number of possible matches is restricted by defining a maximum look-back period based on the case creation date.

    Case Filters

    Case Filters let you define conditions that limit which cases are considered during duplicate detection. You can select any case field or any field in a related object, choose an operator (equals / not equals), and combine multiple filters with AND logic to focus only on the cases that matter.

    Example:

    To only compare cases where Case Origin = Email and where Account.Billing Country = United States.

    This ensures the assessment process runs only on the subset of cases created through the Email to Case process and associated to US Accounts.

    Case Field (Salesforce)

    Email Field (Source)

    Explanation

    Case Sender

    Email Address

    Data Quality - Account

    Customize how Delpha scores and enriches Salesforce Account data. Set automated rules, reassessment schedules, and quality thresholds. Maintain accurate and up-to-date Account records effortlessly.

    Data Quality – Account Configuration in Delpha

    The Data Quality – Account section lets you define how Delpha evaluates, scores, and improves your Salesforce Account records. It helps ensure data remains complete, consistent, and ready for decision-making.

    Key Configuration Areas

    • Account Assessment Criteria Field Use a Boolean field to filter which Accounts should be assessed. By default, Delpha uses the Account.D Do Not Assess field, but you can define your own formula-based field for dynamic control.

    • Account Assessment Enable this to assess all existing and new Accounts once.

    • Account Continuous Assessment Automatically reassess Accounts whenever a monitored field is updated.

    These settings activate Data Quality automation that will consume tokens to ensure optimal data quality in your org.

    If you want to control the token consumption we recommend you

    • to not activate:

    Field-Level Automation Settings

    Fields monitored for quality scoring:

    • Website

    • Billing Address

    • Shipping Address

    • Phone

    For each field, you can:

    • Enable or disable its inclusion in the quality score

    • Set automatic recommendation rules (trigger + score threshold)

    Example – Website

    • Trigger: When value is Incomplete

    Triggering conditions are:

    • Never

    • When value is Incomplete

    • When value is Invalid

    • Score Threshold: 100

    Example – Billing Address

    • Trigger: Disabled

    • Score Threshold: (none set)

    Ultimate Account Assessment

    Evaluates and maintains relationships with ultimate accounts to clarify ownership hierarchies.

    Account Global Scoring

    Calculates a global quality score across all Accounts daily, giving you a snapshot of overall data health.


    Key Takeaways for Users:

    • Use the Criteria Field to fine-tune which accounts should or should not be assessed.

    Delpha Score Meter

    The Delpha Score Meter provides a clear 0–100 quality score based on six dimensions, helping you assess, prioritize, and improve Salesforce data accuracy and reliability at a glance.

    What You Can Do in the Score Meter

    The Score Meter is your all-in-one command center for data quality. It helps you understand, review, and apply improvements — all in a single, intuitive interface.

    1. Understand Your Data Quality at a Glance

    • See your overall quality score for the selected object (e.g. Accounts, Contacts).

    • The score is visually represented with a color-coded gauge for quick assessment.

    • The number of available recommendations is clearly listed.

    2. Review Suggestions Inline

    • View AI-generated recommendations directly from the Score Meter.

    • Each recommendation includes:

      • A confidence score based on the data quality dimensions

      • Extra information to help the decision

    You access this view clicking on the number of recommendations link or navigating in the Score Meter component using the 'next page' sign (>).

    3. Apply Changes — Your Way

    • Choose how to apply recommendations:

      • One by one

      • Bulk select multiple items

      • Accept all suggestions in one click

    What the Score Represents

    The score is based on six key data quality dimensions, evaluated field by field:

    Dimension
    Meaning

    Each field within the record is evaluated and color-coded:

    • Red – Poor

    • Orange – Warning

    • Green – Good

    • Grey – Not applicable / no data

    Why It Matters

    The score helps you:

    • Quickly assess trustworthiness of a record

    • Decide whether to clean, enrich, or reject the data

    Duplicate Merge

    How to automatically handles duplicates with configurable thresholds, merge or parent options, child status rules, and attachment cleanup—keeping Salesforce cases clean and efficient.

    Auto Remediation Threshold

    Define the score threshold above which duplicate cases are automatically processed.

    Auto Remediation

    Defines how duplicate cases are automatically handled once they reach the configured Auto Remediation threshold score. You can choose between several modes:

    • None – No automatic action is taken. Duplicates are only flagged.

    • Auto – The system decides the most appropriate action (merge or assign parent) based on your configuration.

    • Merge – Duplicates are automatically merged.

    Delpha applies the merge behavior defined on Salesforce Setup.

    Service Setup > Process Automation > Case Merge

    • Assign Parent – The duplicate is automatically linked to an existing parent case.

    The Master case is always the oldest case, which may be either Open (still in progress) or Closed.

    • If the Master case is Open, you can choose to either merge the two cases or assign the Master as the parent of the new case.

    Child Case Status

    Child Case Status lets you define what status the duplicate (child) case should take after a merge or parent assignment.

    • Possible values include New, Working, Escalate, or Closed.

    • This ensures that all child cases follow a consistent lifecycle once they are processed, avoiding conflicting or outdated statuses.

    In short: it standardizes the post-processing state of duplicate cases, keeping your case management clean and predictable.

    Assign Parent / Merge Options

    Assign Parent / Merge Options let you control which fields are copied from the Master case to the Child case after a merge or parent assignment.

    • You can select up to 5 fields.

    • This ensures important information (e.g., OwnerId, priority, category) is consistently inherited by the Child case.

    • It helps maintain data quality and consistency across merged or linked cases.

    In short: this option defines which Master case details should overwrite or update the Child case after remediation.

    Duplicate attachments

    This option automatically removes duplicate attachments when using the email-to-case functionality. It prevents the same file from being stored multiple times across redundant cases, reducing clutter and saving storage space while keeping case records clean.

    In short: it ensures only unique attachments are retained in cases created from emails.

    The analysis is based on both the attachment’s name and its size, and only exact matches are considered duplicates.

    Duplicate Data Steward view

    Use Delpha’s Duplicate Data Steward View to detect and merge Salesforce duplicates at scale. Compare fields side by side, trust AI-powered scores, and clean your data with precision and confidence.

    Duplicate Data Steward View in Delpha

    The Duplicate Data Steward View is designed to help you efficiently identify and merge duplicate records in Salesforce. Using side-by-side comparisons, smart scores, and visual cues, you can quickly take action with confidence.

    Main View Overview

    The navigation in the Duplicate Steward view is aligned with Salesforce’s native List View experience:

    • Cog icon: Use the standard cog to manage your views (create, clone, rename, share, select fields to display, delete)

    • Filter Icon: Create custom views filtering on a Campaign, an Object, a Field and the score.

    • Pinned and Favorite Lists: Find the best view when you need it

    By default, you’ll see the “Recently Viewed” records. To unlock the full power of the Data Steward views, we recommend creating your own custom views—tailored filters, field selection, and sharing options give you complete control over your data review

    At the top of the screen, a summary dashboard provides a snapshot of duplicate detection:

    • Total Potential: Total duplicate groups detected (e.g., 806)

    • Match Categories:

      • Exact Match, Likely Match, Possible Match, Unlikely Match

    Each row shows:

    • Account name variations

    • Field-level identifiers (e.g., Website, LinkedIn)

    • Match Status (e.g., Potential, Auto Yes)

    • Score (0–100 confidence)

    Side-by-Side Comparison

    When you select a row, Delpha displays a detailed comparison view:

    • Fields from both records are shown side by side

    • Green dots = selected master value

    • Red highlights = mismatched fields This layout helps you quickly decide what data should be kept post-merge.

    Available Actions

    When rows are selected, the following actions appear at the top:

    • Accept

      • Merge using recommended values

      • Finalize the merge and mark as processed

    • Reject

    How to Use

    1. Filter by object (e.g., Account)

    2. Review suggested matches

    3. Click to open detailed comparisons

    4. Select records

    Merge operation is not applied instantly. Duplicate that are validated by the Data Steward are processed by batch following a .

    Data Quality Steward view

    The Delpha Data Steward Quality View offers an intuitive interface to monitor, clean, and optimize Salesforce data. Filter by field and object, apply smart recommendations to meet high data quality

    Data Steward Quality View in Delpha

    The Data Steward Quality View is your command center for reviewing and improving the quality of Account and Contact data in Salesforce. It offers field-level diagnostics and smart recommendations to keep your data clean and campaign-ready.

    High-level overview of the conversation builder

    Build smart, no-code conversational workflows with Delpha’s Conversation Builder in Salesforce. Guide users with interactive Q&A and automate business logic all within a visual decision-tree interface

    The article provides a high-level description of the processes and components involved in building a conversation using the Delpha conversation builder. The Delpha Author can be defined as the user of Salesforce who has access to the Delpha conversation builder.

    The author playground mainly comprises:

    1. Delpha Conversation Builder

      The conversation builder is a no-code interface used to build new conversations and review existing templates, whereas, the configuration is used to install and uninstall templates.

    2. Salesforce flow module

    Data Quality - Contact

    Configure how Delpha assesses, cleans, and enriches Salesforce Contact data. Set automatic rules for fields update and track global quality scores to maintain clean, reliable contact records.

    Data Quality – Contact Configuration in Delpha

    The Data Quality – Contact section in Delpha allows you to configure how contact records are evaluated, cleaned, and scored to maintain high-quality, actionable data.

    Merge Field Rules section

    Use Delpha’s Merge Field Rules to control which values are kept during Salesforce merges. Apply control specific automated logic,different from the default one.

    Merge Field Rules – Field-Level Control for Smarter Merges

    The Merge Field Rules screen lets you override the default behavior set in the . This powerful interface allows you to define exactly which value should be kept for each field during a merge—ensuring consistent, automated decisions that align with your data governance policies.

    Column
    Account Reassessment Schedule recurring quality checks, even if no changes occur. Options include: Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.

    Account Continuous Assessment: if you do a mass update impacting a monitored field, the records are supposed to be reassessed.

  • Account Reassessment: if a record has not been assessed for more than x months, it will be automatically reassessed, according the setting.

  • To rely on Campaigns to control the scope and the frequency of Data Quality assessments.

  • LinkedIn
  • Legal ID

  • When value is inconsistent

  • Use Account Assessment and Account Continuous Assessment to ensure all accounts are reviewed and updated whenever changes occur.

  • Configure Account Reassessment to address potential data decay by selecting a reassessment schedule.

  • Select the fields involved in Quality Score definition by toggling them on or off.

  • Define the automation rules for automatic data quality remediation

  • For hierarchical relationships, activate Ultimate Account Assessment when needed.

  • Enable Global Scoring for a daily, holistic view of account quality.

  • You can expand or collapse details for quick scanning or deep inspection.

    Track data quality improvements over time

    Completeness

    Is the value present or missing?

    Validity

    Does the data follow the correct format or rules?

    Uniqueness

    Is this value duplicated elsewhere in the system?

    Consistency

    Is the data coherent across fields or systems?

    Accuracy

    Is the value correct (factually or logically)?

    Timeliness

    Is the information still relevant and up-to-date?

    Delpha Quality Score
    Score Meter - Review and Apply
    Sorted by AI-generated confidence scores
  • Total to Be Merged: Duplicates awaiting confirmation

  • Processed status (True/False)

    Dismiss the suggestion

  • Keeps records unchanged

  • Delete

    • Permanently remove selected records (⚠️ use with caution)

  • Click Accept to merge or Reject to skip
    scheduled task
    Duplicate Data Steward View
    If the Master case is Closed, Salesforce only allows the Assign Parent option.

    When Auto is selected, Delpha automatically merges the new case if the Master is Open, and re-parents it when the Master is Closed.

    Main Screen Overview
    Quality Dashboard with Scores and Recommendations

    The navigation in the Data Steward view is aligned with Salesforce’s native List View experience:

    • Cog icon: Use the standard cog to manage your views (create, clone, rename, share, select fields to display, delete)

    • Filter Icon: Create custom views filtering on a Campaign, an Object, a Field and the score.

    • Pinned and Favorite Lists: Find the best view when you need it

    By default, you’ll see the “Recently Viewed” records. To unlock the full power of the Data Steward views, we recommend creating your own custom views—tailored filters, field selection, and sharing options give you complete control over your data review

    Key Metrics at a Glance

    • Total records reviewed

    • Average data quality score

    • Breakdown of quality indicators: Complete, Valid, Consistent, Accurate

    Interactive Tiles

    • Click once: Filter for records that pass a dimension (tile turns green)

    • Click again: Show records that need fixing

    • Click Recommended: Show only records Delpha has suggested improvements for

    Row-by-Row Insights

    Each record shows:

    • Current values

    • Field-level quality indicators

    • Recommended corrections

    • Score & status:

      • Auto Yes – Your value already matches the recommendation

      • Potential – A new recommended value is available

      • Not Found – No suggestion available

      • Failed – Error in analysis

    Core Features

    Filter by Object & Field

    • Choose the object: Contact or Account

    • Select the field: Email, Phone, LinkedIn, etc.

    6 Data Quality Dimensions

    • Completeness, Validity, Uniqueness, Consistency, Accuracy, Timeliness

    • Color indicators:

      • Green = Good

      • Yellow = Warning

      • Red = Issue

      • Gray = Not Applicable

    Quality Dimensions

    Each field is analyzed based on 6 data quality dimensions:

    Dimension
    Description

    Completeness

    Is the field filled in?

    Validity

    Does it follow the expected format or rules?

    Uniqueness

    Is it duplicated across the dataset?

    Consistency

    Is it aligned across systems or related records?

    Accuracy

    Is it factually correct?

    Timeliness

    Is it up-to-date?

    Actions

    • Apply: Accept Delpha’s recommendation

    • Reject: Ignore and keep the current value

    • Delete: Remove the selected record(s) entirely (use with caution)


    Summary

    The Data Steward Quality View gives you:

    • A field-by-field diagnosis of your data

    • Clear recommendations to fix issues

    • Control to apply or reject changes

    • Confidence that your data is clean and campaign-ready

    The flows help in building business automation used in the conversation builder.

    The Conversation

    The conversation is used to describe a use case. It facilitates interactive communication with Delpha assistant & end-user. Every conversation relies on 3 fundamental steps :

    1. Recommendation These are based on contextual rules. The author can define when and where a particular conversation (use case) is proposed.

    2. Engagement Guide the end-user through predefined & Interactive questions & answers.

    3. Execution Take necessary actions to deal with the corresponding use case efficiently.

    Conversation Builder layout

    Conversation Builder

    The Builder consists of 3 main components:

    1. Toolbox: The toolbox appears on the extreme left and comprises all the author's text and variables while building a conversation. The messages, questions, and answers are filled automatically while variables used in the conversation need to be defined by the author.

    2. Tree Canvas: The canvas appears in the center. It is the working area and gives a high-level description of the conversation or the use case defined in a decision tree. The author can initialize and create nodes here.

    3. Properties: The Properties tab appears on the extreme right and allows the author to define properties, including messages, questions, and answers associated with each component of the decision tree.

    Building a Conversation

    Initialization

    Initialization

    In the Initialization window, you can define:

    • Display Rule: Defines the page(s) on which the author wants the recommendation from the assistant.

    • Conditions: Define rule-based evaluation criteria on string fields to display the recommendation.

    • Action Type: Defines evaluation criteria for contextual rules which cannot be defined using conditions. This can be achieved using a Flow, an Apex.

    Once the initialization criteria are valid, you can start the conversation The conversation is made up of nodes that are organized as a decision tree.

    Node

    Conversation Node

    A conversation is made up of nodes. It is the key part of the decision tree and can act either as a redistribution point or endpoint of the conversation. Node consists of:

    • Unique node name

    • Message(s)

    • A question and answer(s) to engage the user and take action.

    1. Answer

    The Answer is the key component of the node which lets the author define the type of answer and the action to be taken upon the selection of an answer.

    Question
    1. The answer can be Static or Dynamic

    Answer - Static vs Dynamic
    • Static answers display fixed answers.

    Static Answer
    • Dynamic answers display a list of dynamic values to select. The values are passed and stored using variables (discussed later).

    Dynamic Answer
    1. The Answer can be Single select or Multi-select

    Answer - Single or Multiselect
    • The Selection view enables checkboxes, whereas, comparison view enables radio buttons.

    Answer - Single or Multiselect
    1. The Answer can lead to an action or not lead to an action

    Action

    The toggle switch can activate new action. The new action can be flow, quick action, apex, conversation, or open in a new tab

    1. Variables

    Variables are placeholders. They are used for storing and retrieving values in the conversation flow (actions or messages).

    Variables in the Toolbox

    Variables can be created on the toolbox and can have multiple formats such as string, number, list, object, Id. The action type requires a set of input and output variables. Example: Input variables such as account Id passed to Flow, which processes the information and provides an output(s) used in the conversation. Variables can be classified into two types:

    • Global variables Read-only built-in variables to reference common information throughout the conversation. Currently, there are 2 global variables CurrentPage and CurrentRecordId

    • Conversation variables User-created variables. They are used to transfer information/data from an action (Flow, Apex) to a conversation or between 2 conversations.

    Key Setup Options
    • Contact Assessment Criteria Field Filter which Contacts should be assessed using a Boolean field (default: Contact.D Do Not Assess). You can use a formula field for more dynamic control.

    • Contact Assessment Enable this to assess all existing and newly created Contacts once.

    • Contact Continuous Assessment Automatically reassess Contact records when a monitored fields change.

    • Contact Reassessment Schedule regular reviews even if the record hasn't changed. Options: Never, Once a Month, Once per Quarter, Twice a Year, Once a Year.

    These settings activate Data Quality automation that will consume tokens to ensure optimal data quality in your org.

    If you want to control the token consumption we recommend you

    • to not activate:

      • Contact Continuous Assessment: if you do a mass update impacting a monitored field, the records are supposed to be reassessed.

      • Contact Reassessment: if a record has not been assessed for more than x months, it will be automatically reassessed, according the setting.

    Name Field Normalization

    Configure how Delpha standardizes and corrects first and last names:

    • Apply Recommendation Automatically Set conditions (e.g., inconsistent value) and minimum score threshold for auto-correction.

    • First/Last Name Rules Control letter case, allowed characters, spacing, and removal of unwanted text blocks.

    Setting
    Description

    Letter case

    Controls capitalization. typical: Capitalize All or ALL UPPERCASE

    Characters

    Specifies accepted alphabets.

    Spacing

    Handles white spaces.

    Text Blocks

    Handles titles or text in parentheses.

    Field-Level Automation Settings

    Monitored Contact fields:

    • Name

    • Email

    • Phone

    • Mobile Phone

    • LinkedIn

    • Mailing Address

    For each field, you can:

    • Include/exclude it from quality scoring

    • Define when recommendations are applied

    • Set a score threshold (default: none)

    Examples:

    Email

    • Trigger: When value is Incomplete

    Triggering conditions are:

    • Never

    • When value is Incomplete

    • When value is Invalid

    • When value is inconsistent

    • Score Threshold: 100 → Only perfect recommendations are applied automatically

    Phone

    • Trigger: When value is Inconsistent

    • Normalization enabled (no score threshold needed)

    Contact Global Scoring

    Automatically computes a daily quality score for all Contact records—giving you a clear view of your data health at a glance.

    Key Takeaways for Users:

    • Adjust the Criteria Field to include or exclude specific contacts from assessments based on your organizational needs.

    • Enable Contact Assessment and Continuous Assessment to ensure all contacts are reviewed and updated whenever changes occur.

    • Configure Contact Reassessment to prevent data decay by setting a reassessment schedule.

    • Select the fields involved in Quality Score definition by toggling them on or off.

    • Define the automation rules for automatic data quality remediation

    • Use Global Scoring to monitor the overall quality of contacts daily.

    Description

    Rule Name

    The label for your merge rule (can be customized).

    Action

    Indicates whether the field is grouped or individually customized.

    Field

    The API name or label of the field the rule applies to.

    Override Rule

    Specifies what value to keep: e.g., Master and Not Empty, Highest Value, or Empty.

    Operation

    Special logic applied (e.g., ConcatenateUnicity to merge unique values).

    Visible

    Whether this field is shown in the bot deduplication conversation.

    Active

    Whether the rule is currently being used during merge operations.

    How It Works

    Each row in the panel defines a rule for a specific field, guiding how the final merged value is selected.

    Common Rule Types:

    • Master and Not Empty: Keep the master record’s value—unless it’s empty.

    • Highest Value: Ideal for dates or numeric fields (e.g., latest activity).

    • Empty: Clears the field value post-merge.

    • ConcatenateUnicity: Combines unique values (perfect for multi-entry fields like tags or IDs).

    Impact on Merge Operations

    These rules are applied when you Accept a merge from the Duplicate Steward View. As a result:

    • The best value is selected automatically

    • Manual review is minimized

    • Merges stay clean, reliable, and aligned with business rules

    ➕ Adding a New Rule

    Click New (top right) to define a custom merge behavior for any additional field.

    The Merge Field Rules section empowers admins and data stewards to:

    • Automate field-level decisions during merges

    • Improve merge precision and consistency

    • Reduce errors and cleanup effort

    Some practical applications:

    • Group fields to ensure data consistency when merging 2 records

    • Hide fields to avoid errors

    Merge Object Rules
    Keep track of values after the merge
    To rely on Campaigns to control the scope and the frequency of Data Quality assessments.

    Build 3.70.0

    Multiple settings for each handled object

    Duplicate Settings now support multiple configurations. You can define a dedicated scope for each configuration using advanced rules in the Record Filter section.

    Each configuration runs its own full duplicate assessment, and the results appear separately in the Duplicate Data Steward View.

    To create a new Duplicate Setting, click Add New, choose the target object, and decide whether to start from the Delpha default template for detection and merge settings. You can also duplicate an existing configuration using the Clone option.

    Detection Settings

    General Settings

    Record Filter

    The goal of the Record Filter is to limit the scope of the duplicate scan, ensuring the system only checks records that meet specific criteria you define.

    1. Filter Logic

    • Filter Logic: This area allows you to combine multiple individual conditions using boolean operators (AND, OR, NOT) to create complex filtering rules.

    • e.g., 1 AND (2 OR 3): This example illustrates how the logic works. It means:

      • Condition 1 must be true, AND

    2. Adding Conditions

    • Search Input Field: You use this to find and select a field name from your database (e.g., Status, Creation Date, Region).

    • Add Condition Button: Once you select a field, you click this button to add a new condition row.

    • Condition Rows (implied below the image): Each row will typically let you:

    Example Use Case:

    You might set up a filter to only check records where:

    1. Status Equals Customer

    2. AND Last Modified Date Is Greater Than 90 days ago

    This filter ensures the duplicate detection process only runs on active customer records that have been modified recently, saving processing time.

    If you use a boolean field (e.g., Do Not Assess) to exclude certain records from duplicate detection, make sure to update your detection scope in App Delpha Setup > Duplicate > Detection Settings, under the Record Filter section. If you skip this configuration, the duplicate analysis will run on all records, which may consume more credits than intended.

    You will have to set up a filter to only check records where:

    Filtering Rules

    The purpose is to apply specific rules before potential duplicates are reviewed and merged.

    The rules are divided into different Rule Types that trigger specific actions:

    Matching Fields

    The Matching Fields configuration, is the core mechanism used by the application to calculate the numerical Duplicate Score for any pair of records. This section defines what fields matter and how much they matter when determining if two records are duplicates.

    Advanced Settings

    This screen shows the Advanced Settings for duplicate detection. This section provides granular control over how the system initially screens for duplicates, cleans data for scoring, and manages duplicate creation in real-time.

    1. Screening Fields

    Purpose is to quickly filter the large pool of records down to a smaller, more relevant subset before the full, weighted matching score calculation (from the "Matching Fields" section) is performed. This significantly improves performance. The system performs a fast initial match (relying on Name). If the name match is inconclusive, it uses these Screening Fields (e.g., ZIP Code, First Letter of Company Name) to narrow down which records should proceed to the full scoring calculation.

    2. Discard Placeholder Values

    Purpose is to prevent "dummy" or default values in your records from artificially inflating or skewing the duplicate match score.

    You can enter common placeholders that should be ignored into the input field or directly select them from the proposed values.

    3. Duplicates at Creation

    Define the system's immediate response when a user attempts to create a new record that matches an existing record. This is a crucial real-time defense against data decay.

    You choose an option from the dropdown menu to determine what action the system takes:

    Either Condition 2 OR Condition 3 must be true.

  • The numbers (1, 2, 3) refer to the individual conditions defined below.

  • Select a Field (e.g., Record Status).

  • Select an Operator (e.g., Equals, Is Not Null, Is Greater Than).

  • Enter a Value (e.g., Active).

  • Do Not Assess Equals False

    Setting

    Status/Value

    Explanation

    Activate Duplicate Detection

    Active (Toggle On)

    This is the master switch. Duplicate detection is currently enabled and running based on the configured rules.

    Run Evaluation

    Evaluate (Button)

    This is the action button used to manually trigger the duplicate detection process. When clicked, the system scans the records and flags potential duplicates according to the rules and threshold.

    Detection Threshold

    50

    This sets the minimum match score for a pair of records to be flagged as potential duplicates. Pairs must have a score $\ge 50$ (on a likely 0-100 scale) to be surfaced for review. A lower number flags more potential duplicates.

    Rule Type

    General Purpose

    Action Taken

    EXACT MATCH

    Used to automatically flag a pair as a certain duplicate if they have an exact match on high-certainty identifiers.

    If the specified conditions are met, the system automatically considers them as perfect duplicates. The score is set to the maximum (100), the Status is set to Auto Yes and a specified comment is added. This can prepare them for automatic or priority merging.

    DISCARD

    Used to prevent a pair of records from being considered duplicates if they match a specific rule.

    If the values in the specified field(s) match, the system discards the pair. The Status is set to Auto No. The pair is not proposed to the Delpha User and can only be processed (accepted or rejected) by the Data Steward.

    KEEP

    Used to automatically flag a a pair by adding a comment if they match a specific rule.

    When a pair of records meets the criteria of a KEEP rule, the system retains the pair in the set of potential duplicates and add a specific comment.

    Option

    System Action

    Outcome

    Allow (Async Detection)

    (Default/Least Restrictive) The record is created immediately.

    The duplicate check runs after creation, and the record is flagged for later review.

    Block (Prevent Creation)

    (Most Restrictive) The system performs a real-time check. If an exact match is found, it stops the creation process and forces the user to resolve the conflict (e.g., update the existing record).

    Creation is prevented, ensuring no new duplicates enter the system.

    These fields are involved in the score calculation.
    3.png
    3.jpg
    image.png
    image.png
    image.png
    1.jpg
    1.png
    3.png
    image.png
    image.png
    image.png
    image.png
    image.png
    Picture34.png
    Picture35.png
    Picture1.png
    Picture32.png
    Picture33.png