Pure CallerID is a phone intelligence service that analyzes phone numbers to determine factors such as number validity, activity level, carrier details, and line type.

By integrating Pure CallerID with LeadExec, you can automatically evaluate phone numbers during lead submission and take action based on the response. This helps improve lead quality and prevents invalid or inactive numbers from entering your workflows.

The Pure CallerID integration in LeadExec provides several tools to help validate phone numbers and automate lead quality and compliance checks.

1. Phone Number Validation

Analyze phone numbers to determine whether they are valid and active.

This helps identify numbers that may be invalid, inactive, or low-quality, preventing bad contact data from entering your system.

3. Do Not Call and Compliance Checks

Pure CallerID can evaluate phone numbers against Do Not Call registries and compliance databases.

This includes identifying numbers that may appear on national or state Do Not Call lists, helping organizations maintain regulatory compliance.

4. Known Litigator Detection

The integration can identify numbers associated with known TCPA litigators.

If a number has a history of litigation or complaints, this information can be returned in the response so appropriate actions can be taken before outreach occurs.

5. Automated Lead Filtering

Create criteria rules based on returned validation data.

These rules allow LeadExec to automatically reject leads, route them for review, or flag them for compliance checks based on the results returned by Pure CallerID.

Before configuring the Pure CallerID integration in LeadExec, ensure the following requirements are completed.

API Key

Obtain an active API Key from Pure CallerID. This allows LeadExec to authenticate and submit validation requests.

Pure CallerID Configuration Details

Have the following information from your Pure CallerID account:

These values determine where leads will be loaded within Pure CallerID.

Create Lead Type Fields

Create any response fields you want to store in your Lead Type configuration so LeadExec can capture the validation data returned by Pure CallerID (for example: ValidationResult.IsValid, ValidationResult.ActivityScore, ValidationResult.LineType, ValidationResult.Carrier, ValidationResult.IsActive, DoNotCallResult.IsBlocked, StateDoNotCallResult.IsBlocked, knownLitigatorCheck.IsFound).

Creating these fields ensures that the returned validation data can be stored and viewed within LeadExec.

Before configuring the integration, ensure you have the required Pure CallerID campaign and dialer list information.

To enable the integration:

Once saved, the integration will be available for configuration.

After enabling the integration, click Details to open the system-wide settings.

These settings are configured per Lead Type.

To add a configuration:

Once the Lead Type is added, you will be prompted to configure the Request Fields, Data Fields, and Response Fields.

Request fields determine the information that LeadExec sends to Pure CallerID when submitting a lead.

Campaign ID (Required)

The Pure CallerID Campaign ID where the lead will be submitted.

Example
​611111111111111111111

Dialer List ID (Required)

The Dialer List ID where the lead will be loaded.

Example
​DL00001

List Name (Required)

The name of the list within the dialer where the lead will be stored.

Example
​CP1234

These fields ensure that leads submitted from LeadExec are properly routed into the correct campaign and dialing list within Pure CallerID.

Data fields allow you to map additional lead information that will be sent to Pure CallerID during the validation request.

These fields provide context about the lead and allow the service to perform more accurate validation and compliance checks.

Common data fields include:

Phone
The phone number being submitted for validation.

Zip
The ZIP code associated with the lead.

City
The city associated with the lead.

State
The state associated with the lead.

VeriskLeadId
A unique identifier used for Verisk lead tracking and verification.

TrustedForm Cert URL
The TrustedForm certificate URL, which provides proof of consent and lead capture details for compliance purposes.

Mapping these fields ensures Pure CallerID receives the necessary lead data to perform validation and compliance checks.

Response fields store the data returned by Pure CallerID after a phone number has been evaluated.

To use these values in LeadExec, you must first create corresponding fields within your Lead Type configuration so the returned data can be stored and referenced.

Common response fields include:

Validation Results

Do Not Call Results

State Do Not Call Results

Known Litigator Check

These fields allow LeadExec to capture detailed validation and compliance information for each phone number.

Once request and response fields are configured, you can define criteria rules that determine how LeadExec should handle leads based on Pure CallerID results.

To create a rule:

Example:

Reason = Equals - Invalid

This rule could automatically reject leads containing invalid phone numbers.

You can also configure actions such as:

This allows LeadExec to automatically filter or route leads based on the validation results.

After configuring the integration settings, it must also be enabled within the campaign.

To enable it:

Once enabled, the integration will run automatically whenever leads are submitted through that campaign.

Note: Campaign-level integration settings are optional and are intended to override the global integration settings when configured. This allows each campaign to apply different validation rules, fraud thresholds, or data requirements depending on its specific needs, providing greater control over how leads are evaluated and routed through that particular campaign.

Once the integration is set up, and lead start flowing into the system, you can filter results within the main Leads list view by adding the relevant columns and filters to your screen.

You can also review the integration results by opening the lead and navigating to the Integrations tab. From this window, you’ll be able to see the result and status of the integration for that specific lead.

If the integration is not returning results as expected, you can test the connection directly from the campaign where the integration is enabled.

To test the integration:

A prompt will display the JSON request payload. You can enter sample values such as a phone number and submit the request.

When reviewing the results, verify the following:

Testing allows you to confirm that the API request structure, field mapping, and response handling are functioning correctly before processing live leads.

When configuring the Pure CallerID integration, consider the following recommendations.

Ensure response fields exist in your Lead Type

Create fields for important response values such as:

This allows LeadExec to properly store and use the returned data.

Use compliance checks when creating criteria rules

Consider creating rules that evaluate:

This helps prevent outreach to numbers that may present legal or compliance risks.

Test the integration before enabling it on live campaigns.

Use the Test feature in the Integration Manager to verify request values, field mappings, and criteria rules before processing real leads.