LEADCONDUIT ADD-ON
Blacklist Alliance | Litigation Firewall
Block professional TCPA plaintiffs and attorneys by scrubbing high-risk numbers from your outbound campaigns and inbound calls.
SPECIFICATION
Fields & configuration
The exact fields this add-on uses, appends, and the configuration options available in LeadConduit.
Appended Fields
Blacklist Alliance will append the following data to your lead.
| Appended Field | Description |
|---|---|
Outcome | Was the phone number lookup successful? |
Reason | Error reason |
Billable | Whether or not this was a billable event |
Status | This is the status of your request. |
Message | 'Blacklisted' if the number is blacklisted; otherwise 'Good' |
Code | For blacklisted numbers, a comma-separated list of data feeds it was found on |
Code Level | A numeric representation of the data feed code: 0 = no code, 5 = screamers, 10 = prelitigation1/prelitigation2, 15 = attorney-secondary, 20 = plaintiff-secondary, 25 = attorney-primary, and 30 = plaintiff-primary |
Wireless | Is this number wireless or a landline? 1 if wireless or 0 if landline. |
Carrier Type | Type of the carrier (for example: WIRELESS, PCS) |
Carrier Name | Name of the carrier (for example: AT&T, T-Mobile) |
Carrier State | U.S. state of the carrier |
Fields
The following fields are used by this integration and automatically added to your flow when missing.
| Field | Description |
|---|---|
Phone 1 Required fieldBlacklist Alliance needs this data to function. | Phone number to query blacklist for |
Custom Input Variables
The following are configuration options (typically not collected with lead data).
| Variable | Description |
|---|---|
| Api Key | Optional API Key; standard transactional pricing will be applied if you use your own key |
| Timeout Seconds | Produce an "error" outcome if the server fails to respond within this number of seconds (default: 360) |
GETTING STARTED
Add Blacklist Alliance in three steps
Add the add-on
In your LeadConduit flow, add a new Add-On step and select Blacklist Alliance.
Provide required data
Map the lead data the service needs. Required fields and configuration options are shown above.
Use the result
Run the flow and use the add-on result for real-time routing, validation, enrichment, or downstream decisions.
KEEP EXPLORING
More add-ons
Catch fraudulent leads before they move downstream
Add trusted services to your LeadConduit flow in minutes, or talk with our team about the right add-on for your workflow.