Overview
The Litigator Scrub integration, powered by Contact Center Compliance (DNC.com), provides a specialized compliance check that identifies phone numbers associated with known Telephone Consumer Protection Act (TCPA) litigators. These are individuals who frequently sue telemarketers and lead sellers. By integrating this check directly into LeadExec, every lead is automatically screened the moment it arrives. If the phone number matches a known litigator, the lead can be instantly rejected or flagged for review, significantly reducing the risk of costly lawsuits.
This is not a full Do Not Call (DNC) scrub, but a targeted layer of protection against high-risk leads.
Key Functionality
Real-Time Litigator Screening: Every lead is checked against the Contact Center Compliance litigator database the moment it enters the system.
Binary Outcome: The API returns a simple
IsLitigator: true/falseresponse, making configuration straightforward.Configurable Actions: Choose what happens when a litigator is detected—Reject the lead (default and recommended) or Flag it for manual review.
Campaign-Level Control: Enable the integration on specific campaigns and define the exact phone field to scrub.
Audit Logging: All scrub attempts and results are logged for compliance and reporting purposes.
Test Mode: Safely test the integration with known litigator numbers without affecting live lead flow.
How It Works
When a lead is ingested into a campaign with the Litigator Scrub integration enabled:
Trigger: Immediately after the lead passes basic validation, LeadExec sends the lead's phone number to the Contact Center Compliance Litigator Scrub API.
API Request: A simple HTTPS request containing the phone number (e.g.,
{ "Phone": "5039367187" }) is sent. Authentication is handled via an API key stored in global settings.API Response: The API returns a JSON response:
{ "Phone": "5039367187", "IsLitigator": true/false }.LeadExec Handling:
If
IsLitigator: false, the lead passes this check and continues through the workflow.If
IsLitigator: true, LeadExec performs the user-configured action (Reject or Flag).
Post-Processing: If the lead is rejected, it is marked as "Rejected (Litigator Scrub)" and will not be routed to any buyers. If "Skip remaining integrations on reject" is enabled, no further integrations are called for that lead. If the lead is flagged, it is moved to a review queue for manual inspection.
How to Configure the Litigator Scrub Integration
Prerequisites
You must have an active Contact Center Compliance (DNC.com) account and a valid API key for the Litigator Scrub service.
The integration must be enabled system-wide for your account (if you do not see the option in your Integrations screen, please contact your LeadExec administrator).
Step 1: Global Configuration (One-Time Setup)
Navigate to Settings > Integrations.
Locate the DNC.com Litigator Scrub integration, and click Details.
Toggle the Enabled option in the top-right corner.
Navigate to the Connection Settings section and enter your API Key provided by Contact Center Compliance in the designated field.
Click Save API Key. The key will be stored securely (encrypted).
Note: Without a valid API key, the integration will fail to authenticate and will not scrub leads.
Step 2: Configure Lead Type Field Mapping and Actions
From the Lead Type Configurations section, click New to add your desired lead type.
Request and Response Field Mapping:
Request Fields: Select the lead field that contains the phone number to be scrubbed (typically your primary phone field). This is the only required field mapping.
Response Fields: Select a lead field that reflects the results of the scrubbings.
Criteria Configuration: Define the rule for when a litigator is detected:
Example: If Is Litigator Equals True, then [Select Action]
Reject: (Recommended) The lead is immediately rejected and will not be delivered.
Quality Control: The lead is flagged for manual review but is not automatically rejected. It will not be sent to buyers unless manually approved.
(Optional) Continue on Match: If you want to stop processing further integrations (e.g., fraud scores, other scrubs) when a litigator is found, disable this option. This saves time and API costs.
Step 3: Enable the Integration on a Campaign
Go to the specific Campaign where you want to enable litigator scrubbing.
Navigate to the campaign's Integrations > Manage tab.
Find the DNC.com icon in the list of available integrations.
Click Add to enable the integration.
Set Integration Order (Optional):
If you have multiple integrations enabled on this campaign, you can drag the Litigator Scrub to your desired position in the execution order.
Running this integration early can prevent wasted processing on high-risk leads; running it later ensures other validations (like required fields) are complete first.
The API is very fast (sub-second), so either approach is viable and depends on your preferences and needs.
From the Integration Criteria section, you can add an override criterion (similar to the system-wide setup we did on Step 2) specific to this campaign.
Step 4: Test the Integration
Ingest a lead into LeadExec using a known litigator test number (if provided by DNC.com) or a real number to verify the integration is working correctly.
Check the lead's logs to confirm the scrub result was recorded.
Best Practices
Always use Reject for litigator leads: Flagging litigator leads still exposes you to risk if a user accidentally calls them. Rejecting is the safest course of action.
Place the integration early in your chain: While it is fast, putting it early ensures you don't waste money on other API calls (e.g., Trestle, IPQS) for leads that will be rejected anyway.
Disable "Continue on Match" for Litigator Is True: Reject: This maximizes cost savings and efficiency.
Test thoroughly before going live: Use Test Mode to validate your configuration and confirm that the phone field is mapped correctly.
Monitor your logs: Regularly check for any integration errors (e.g., authentication failures) to ensure continuous protection.
Understand the scope: This integration only checks for known litigators. It does not scrub against National or State Do Not Call lists, wireless lists, or reassigned numbers. Those must be handled through other means.
Troubleshooting
Integration option is not visible in campaign settings:
The feature may not be enabled for your account. Contact your LeadExec administrator or support.
Verify the integration was enabled globally in Settings > Integrations.
Leads are not being scrubbed (no logs, no rejections):
Check that the integration is enabled for the specific campaign.
Verify the API Key is entered correctly in global settings. An invalid key will cause authentication failures logged as errors.
Ensure the correct phone field is mapped. If the mapped field is empty for a lead, the scrub will not run.
Ensure you add a Response Field to capture the results of the scrubbings.
Leads are being rejected incorrectly (false positives):
False positives are rare but can occur if a phone number has been reassigned from a former litigator to a new consumer. Confirm the number with Contact Center Compliance if necessary.
If you suspect an error, you can temporarily switch the action to Flag and manually review affected leads while investigating.
API errors appearing in logs:
401 Unauthorized: Your API key is invalid, expired, or not authorized for the Litigator Scrub service. Contact Contact Center Compliance.
Timeout/Network Errors: The API may be temporarily unavailable. The integration will allow leads to pass (fail open) to avoid disrupting your business. Monitor the situation and contact support if the issue persists.
Leads are still being delivered even when IsLitigator = true:
Confirm the action rule is set to Reject, not Flag.
Need to know if a specific number was flagged:
All scrub results are logged in the lead's history. You can search the lead's logs for entries containing "Litigator Scrub" or the result status.