Search

Blacklist Alliance Add-Ons

Leandro
Leandro
  • Updated

Feature Snapshot

Summary:
The Blacklist Alliance Add‑Ons are integrations that screens incoming leads against multiple litigation risk feeds provided by Blacklist Alliance, automatically determining if a lead is high‑risk based on prioritized risk outcomes.

Key Benefits:

  • Provides real‑time detection and identification of risky phone numbers by checking against several litigation risk feeds
  • Automates lead rejection by utilizing risk codes and numeric risk levels to determine if a lead should be blocked
  • Enables fine‑tuning of lead acceptance through configurable parameters (code and code_level)

Typical Use Cases:

  • Rejecting leads whose phone numbers appear on high‑risk litigation feeds such as Primary Plaintiff or Primary Attorney
  • Configuring flows to only allow leads below a certain risk threshold, thereby improving lead quality
  • Ensuring compliance and legal protection by automatically screening and filtering leads that have potential litigation history

How the Blacklist Alliance Add‑Ons work?

The Blacklist Alliance Add‑On operates by querying a series of prioritized risk feeds (such as Primary Plaintiff, Primary Attorney, and others) provided by Blacklist Alliance. The integration checks the incoming lead’s phone number against these feeds in descending order of risk. When a match is found, it returns a specific risk code (code) and an associated numeric value (code_level) on a 0–30 scale. Leads that meet or exceed a predefined risk threshold can be automatically rejected, giving users the flexibility to tailor their lead flow based on litigation risk.

Step‑by‑Step Instructions

  1. Log in to LeadConduit:
    Access your LeadConduit account and open the relevant flow where you wish to include litigation risk filtering.

  2. Add the Blacklist Alliance Add‑On:
    In the flow editor, click “Add to Flow > Add-Ons” and select the Blacklist Alliance Add‑On from the list of available services.
    Expected Result: The Blacklist Alliance Add‑On step appears in your flow.

  3. Configure the Filters settings (optional):
    If you want to filter leads based on specific risk feed, customize the rejection threshold in your Filter by setting the code_level variable and review the returned code for more granular response handling.
    Expected Result: The settings reflect your chosen risk thresholds and mapping variables.

  4. Save and Deploy:
    Click “Save” to update your flow and then deploy the changes for active lead screening.
    Expected Result: The Blacklist Alliance Add‑On is live and monitoring incoming leads for litigation risk, rejecting those that exceed your defined threshold.

blacklist alliance add-on steps in a flow

Validation & Monitoring (optional)

  • Test the Setup: Submit a test lead using a phone number known to appear on one of the Blacklist Alliance risk feeds and verify that the lead is rejected according to the configured risk threshold.
  • Where to Monitor?: Review the LeadConduit event logs and dashboard, specifically checking the outcome, code, and code_level fields to ensure correct risk classification and rejection behavior.

Best Practices

  • Regularly review and update risk feed mappings and risk thresholds in collaboration with your compliance and legal teams to reflect current litigation trends.
  • Test configuration changes using controlled test leads before deploying updates into production.
  • Document your risk thresholds and mapping logic so that team members understand how the system determines lead acceptance or rejection.

Troubleshooting

Symptom / Error Likely Cause Resolution
Unexpected lead rejection The lead’s phone number is matching a low‑risk feed (e.g., Screamers) with a low threshold value Review the returned code and code_level; adjust the risk threshold to prevent inadvertent rejection
Lead not rejected despite a high‑risk match Misconfiguration in the Add‑On settings or an incorrect threshold configuration Verify that the Blacklist Alliance Add‑On settings are correctly configured and that the code_level variable is properly set
Multiple risk codes returned The lead matches more than one risk feed; risk feeds are prioritized but may cause confusion Use the code variable to identify the highest risk feed match and adjust filtering logic accordingly
Valid leads being filtered out The rejection threshold (code_level) is set too low, capturing even low‑risk leads Revisit and raise the code_level threshold to allow qualified leads to pass through

Frequently Asked Questions (FAQ)

Q: What are the Blacklist Alliance Add‑Ons?
A: They are integrations that query multiple litigation risk feeds provided by Blacklist Alliance to assess the risk associated with a lead’s phone number, returning a risk code and a numeric risk level (code_level).

Q: Why are the Blacklist Alliance Add‑Ons important?
A: They help protect your organization by automatically filtering out leads that are associated with high litigation risks, thus ensuring compliance and reducing potential legal exposure.

Q: How do I use the Blacklist Alliance Add‑Ons?
A: Log into your LeadConduit account, add the Blacklist Alliance Add‑On to your flow, configure the settings including risk thresholds using the code and code_level variables, and then deploy your flow. This setup ensures that leads matching high‑risk criteria are automatically rejected.

Q: How does the Blacklist Alliance risk of litigation system work?
A: To find known litigators, the Blacklist Alliance API looks for the phone number in each risk of litigation feed, starting from the riskier feed; if the phone number is found in one of the feeds, the feed’s name is provided in response.

Blacklist Alliance’s risk feeds are the following:

Risk Feed Name Response Code Description
Primary Plaintiff plaintiff-primary This data feed comprises phone numbers that we have certainly received the call or text that sparked the lawsuit. Approximately 20% of TCPA complaints specify the number called or texted in its entirety, and the remainder lists a partial number for the plaintiff (i.e., 629-281-XXXX). If the full number is listed in the Complaint, or the researcher is able to locate a definite match for a partial number through research, the number is added to the Primary Plaintiff data feed.
Primary Attorney attorney-primary Like Plaintiff Primary, these are numbers we know for certain belong to the attorney representing Plaintiff because they are listed in the Complaint or are otherwise positively identified.
Secondary Plaintiff plaintiff-secondary This data feed is for numbers that are likely associated with a Plaintiff, but we cannot say so with 100% certainty. If a Plaintiff has a common name and resides in a large metropolitan area, we may locate several people from the same area with the same name. We then attempt to narrow down the results by matching the partial phone number and other data points included in a Complaint. Even when a single individual is identified, we often uncover multiple numbers for that person and the number that received the call or text that triggered the litigation. These may be additional landlines or cell phone numbers currently assigned to that person or to another member of their household, and sometimes, they may be old numbers that have since been reassigned to other people.
Secondary Attorney attorney-secondary These numbers are associated with other attorneys in the same law firm as the Plaintiff’s attorney or which may be associated with the Plaintiff’s attorney, but we cannot say so with 100% certainty.
Prelitigation prelitigation2 prelitigation1 This feed is comprised of numbers belonging to thousands of consumers who have threatened litigation, but their claim was settled out of court.
Screamers screamers All numbers in this feed were reported as belonging to consumers who verbally threatened litigation or were otherwise abusive but never filed suit or submitted a written TCPA demand letter.
Anti-Telemarketing Groups anti-telemarketing This feed is comprised of numbers belonging to members of various anti-telemarketing groups on Facebook and other platforms that our researchers have infiltrated.

Notice that the feeds above are ordered from higher to lower risk; according to Blacklist Alliance, the remaining feeds will be skipped if a phone number is found on a feed with higher risk.

By default, if Blacklist Alliance provides any of the risk feeds above, LeadConduit will mark the lead as Rejected.

If a customer wants to fine-tune which consumers are filtered by the Blacklist Alliance outcome in their Flow, they should use the following two variables within a Filter to decide how the Blacklist Alliance response will be evaluated:

  • code - The actual risk code value as is exactly returned by Blacklist Alliance.

  • code_level - A numeric, scaled value with the range 0-30 that specifies the risk level.

    The value uses increments of 5 (Screamers = 5, Primary Plaintiffs = 30) to give us a shot at sneaking in other numbers if BLA changes their feed names:

If, in the filter configuration, the customer decides to stop the lead flow when the phone number has a certain risk level, they will have to use the code_level variable to decide the Lead rejection threshold they want to use with the Blacklist Alliance add-on response.

The variable value will allow them to set the Lead rejection threshold, which will correspond to a Risk of litigation feed (Primary Plaintiff, Primary Attorney, etc.), and when configured, it will include all the higher Risks of litigation feeds.

For instance, if they create a Filter with code_level set to 10, any phone number found in Prelitigation or riskier feeds (Secondary Attorney, Secondary Plaintiff, Primary Attorney, and Primary Plaintiff) will be filtered.

blacklist alliance filter steps in a flow

Glossary

Term Definition
Blacklist Alliance A data provider that aggregates litigation risk information from various sources to identify phone numbers associated with legal actions.
Risk Feed A specific collection of phone numbers flagged for potential litigation risk, such as Primary Plaintiff or Primary Attorney.
code The actual risk code value as is exactly returned by Blacklist Alliance.
code_level A numeric, scaled value with the range 0-30 that specifies the risk level.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.