Feature Announcement - Blacklist Alliance Scrubbing

Feature Announcement - Blacklist Alliance Scrubbing

Feature Announcement

Blacklist Alliance Scrubbing

The Blacklist Alliance is an organization that provides a compliance and risk management solution for leads used in marketing campaigns, in order to avoid TCPA Predators. This is done through their Litigation Firewall via an API. The ChaseData solution allows you to configure your Blacklist Alliance API key in the system, so it can check numbers against their TCPA plaintiff database when performing relevant outbound calls on specific Campaigns.

In order to make use of your Blacklist Alliance account to check your numbers against their list, you need the following:

  1. An appropriate account with Blacklist Alliance, which includes a corresponding API Key for integration
  2. Configuring your Blacklist Alliance API Key in the ChaseData system (for your ChaseData account)
  3. Enabling Blacklist Alliance lookup for each Campaign for which you want the ChaseData system to check your numbers.

API Key

After you have set up your Blacklist Alliance account and obtained your API key from them, the first thing you need to do is to setup integration access in the ChaseData system by configuring your API Key.

To access these integration settings, click on the 3-dot icon on the right side of the top area of the Admin GUI, above the Search field, which will open a menu; click on Settings, and on the expanded menu click on Integration.  Refer to the following picture.


Click in the Blacklist Alliance tab to display the corresponding setup window, then enter your API KEY and save.  Refer to the following picture.


Campaign Enabling

The next thing that you need to do is to enable the Blacklist Alliance scrub function for each appropriate Campaign. You do this in the Campaign Settings.

Go the main menu area on the left of the Admin GUI, click to expand the Campaigns menu, and select Create & ManageThen select your Campaign. This will cause a new window panel to open on the right side; here’s where you configure the Campaign.  Refer to the following picture.


The Campaign Settings configuration area is divided in four major groups, and for this case you need to expand and access Outbound Settings. and scroll down to, and expand, Advanced Dialing Rules & Strategies to access the Blacklist Alliance Settings. Refer to the following picture.



The corresponding Blacklist Alliance options are described in the following table.

Blacklist Alliance Settings

Make use of customer’s Blacklist Alliance account to scrub flagged numbers. This section will be greyed out if the corresponding API KEY hasn’t been previously configured.

Enable Blacklist Alliance Scrub

Enable scrubbing numbers through the use of Blacklist Alliance’s API

Scrub During Cache Loading

Switch to indicate, when selected, that Blacklist Alliance scrubbing should be done by the system during call cache loading, in bulk, rather than individually just before each call; this option allows for a more efficient process

Scrub During Import

Switch to indicate, when selected, that Blacklist Alliance scrubbing should be done by the system during lead import, in bulk, rather than individually just before each call; this option allows for a more efficient process


Notice that this area will be greyed out if you have not previously configured a corresponding Blacklist Alliance API KEY.


Scrubbing

When the ChaseData CCaaS system is properly integrated with the Blacklist Alliance, and a number check against it comes back positive, the number is scrubbed accordingly.

If the corresponding telephone number is scrubbed through this process, the ChaseData CCaaS system updates the corresponding Contact record with a disposition that conforms to the following format:

FTC DNC (<code>)

The following tables list the possible values for <code>, which the ChaseData CCaaS system determines based on the information obtained from Blacklist Alliance.


C

Callable

W

Wireless number

D

Do Not Call database match; Details field in Call History provides additional details, if available

L

Wireless number in a US state that does not allow telemarketing to wireless numbers even if manually dialed; Details field in Call History provides additional details, if available

B

Blocked


    • Related Articles

    • DNC Integration, Import and Scrubbing

      DNC.com Integration, Import & Scrubbing DNC.com Integration The ChaseData CCaaS system provides a rich set of integration possibilities, and that includes communicating with the Do-Not-Call system (DNC.com), allowing you to set yourself to comply ...
    • Feature Update-Campaign Settings

      Feature Update Campaign Settings & Default Settings The Campaign Settings scope has grown over time, and we have reached a point where we find the need to reorganize/regroup these settings, including some renaming, to make sure it stays intuitive and ...
    • Feature Discussion - Outbound Dialing Summary

      Feature Discussion Outbound Dialing Summary In this document we present a snapshot, or a high level summary, of key capabilities of the ChaseData CaaS for making outbound calls. For more detailed descriptions, capabilities, and configuration ...
    • Setting up a Campaign

      Setting up a campaign in ChaseData’s Cloud Contact Center Software is quite simple. The challenging part is knowing you own personal dialing strategy you want to pursue. Whether it be Outbound, Inbound or Blended dialing ChaseData’s campaigns have ...
    • Feature Announcement - Bucket Dialing Mode

      Feature Announcement Bucket Dialing Mode We have added additional flexibility to the ChaseData solution to provide the option to allow certain agents to be assigned outbound calls (dial out) from multiple Campaigns at a time. This can be done by ...