Skip to main content
The CCC DNCScrub app for Salesforce brings TCPA and Do Not Call compliance checking natively into your CRM. It checks phone numbers against federal and state DNC registries, wireless lists, litigator databases, and your own Internal Do Not Call list — directly on Lead, Contact, Account, and Campaign Member records, before your team dials. The app is a native Lightning application built with Lightning Web Components. Scrub results are stored in custom fields on your records, so they work with standard Salesforce reports, list views, flows, and validation rules.
This is the modern Lightning app. A legacy Visualforce package is still available for older orgs, but new installations should use the Lightning app described here.

​
Prerequisites

  • A Salesforce org on Lightning Experience (Developer, Professional with API access, Enterprise, or Unlimited edition)
  • Permission to install apps and edit Lightning record pages (System Administrator or equivalent)
  • A DNCScrub account with API access — your Login ID (API key) and, optionally, a Campaign ID

​
Step 1: Install the App

Install the CCC DNCScrub managed package using the link that matches your org. You must be logged in to the target org before opening the link. Production:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04thm000000qKgzAAE Sandbox:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04thm000000qKgzAAE Specific Org: replace <theirdomain> with your org’s My Domain.
https://<theirdomain>.sandbox.my.salesforce.com/packaging/installPackage.apexp?p0=04thm000000qKgzAAE
1

Open the install URL

Copy the install URL for your org type above and open it in your browser. Salesforce will confirm the components being added.
2

Choose who to install for

Select Install for All Users (or the scope that fits your rollout).
3

Approve access

During install, Salesforce shows a “Yes, grant access to these third-party web sites” checkbox listing the DNCScrub API endpoints. Check it to approve. You do not need to add these URLs manually — the package includes them as active Remote Site Settings and creates them for you on install.
Each org is configured separately — including sandboxes. Installing the package does not carry over configuration between environments. In every org you install into, repeat Step 2 to enter your Login ID / Campaign ID and Step 3 to assign the permission sets. If you’re testing against a sandbox, confirm the Login ID you enter is valid for the environment you’re pointing at.

​
Step 2: Connect Your DNCScrub Account

After installing, open the CCC DNCScrub app from the App Launcher and go to the Settings tab to enter your DNCScrub credentials. These settings apply org-wide to every scrub operation.
The CCC DNCScrub Settings tab before any credentials are entered, with empty API credentials, scrub options, and notifications sections
1

Enter your credentials

Under API credentials, enter:
  • Login ID (API Key) — your DNCScrub API key
  • Campaign ID — the DNCScrub campaign used to scrub (optional)
2

Test the connection

Select Test Connection to verify your Login ID works against the DNCScrub API.
3

Set scrub behavior

Configure the Scrub Options:
  • Scrub Against — which lists to screen numbers against
  • Rescrub Interval (0–23 hours) — how long a cached result stays “fresh” before a new API call is made. 0 re-checks on every page load; 23 re-checks at most once per day.
Optionally enable Notifications to send an email after a bulk scrub completes.
4

Save

Select Save Settings.
CCC DNCScrub Settings tab showing API credentials with a verified connection, scrub options, and notifications

​
Dashboard

Once connected, the Dashboard tab is your home base — an at-a-glance view of scrubbing activity (Do Not Call scrubs today and this week, Do Not Call numbers identified today, and reassigned checks today), along with an embedded Quick Scrub and a Recent Activity log.
CCC DNCScrub Dashboard with activity statistics, quick scrub, and a recent activity table

​
Step 3: Assign Permission Sets

The app ships with two permission sets. Assign them to your users from Setup → Permission Sets.
User seeing an “invalid access” error, or a Standard user can’t scrub? They’re almost always missing a permission-set assignment. Standard users have no access to the scrub fields or actions until you assign them CCC User (or CCC Admin) — assigning the permission set resolves it. This must be done in each org, including sandboxes.

​
Step 4: Add the Scrub Panel to Record Pages

The CCC DNC Scrub Panel is a Lightning component you place on Lead, Contact, Account, or Campaign Member record pages.
1

Edit the record page

On a record, select the gear icon → Edit Page to open Lightning App Builder.
2

Drag in the Scrub Panel

Drag the CCC DNC Scrub Panel component onto the page (the sidebar works well).
3

Configure the phone fields

Set the Phone Fields to Scrub property to a comma-separated list of field API names — for example Phone,MobilePhone,HomePhone. Each field is scrubbed and displayed independently.
4

Activate the page

Save and Activate the page for the relevant app, record type, or profile.
Lightning App Builder editing a Lead Record Page, with the CCC DNC Scrub Panel and other CCC components listed under Custom in the components palette

The CCC components appear under Custom in the Lightning App Builder palette.

Lightning App Builder showing the CCC DNC Scrub panel added to the Lead Record Page canvas

The CCC DNC Scrub Panel placed on the record page in App Builder.

​
Scrub Panel properties

You can place more than one panel on the same record page with different settings — for example, one panel that auto-scrubs the business Phone and a second panel for MobilePhone that only scrubs on demand.

​
Scrubbing a Record

When the Scrub Panel loads, it automatically checks every configured phone field (unless auto-scrub is disabled). If a number was scrubbed within the rescrub interval, the cached result is shown without a new API call; otherwise a fresh check runs. Each phone field renders as its own card with a status badge, line type, carrier, region, and a Re-Scrub button. Click Re-Scrub at any time to force a fresh check.
A Lead record page with the CCC DNC Scrub panel in the sidebar showing an Internal DNC result, line type, scrub time, and a Re-Scrub button
The record’s summary fields always reflect the worst result across all phone fields. If Phone is Clean but MobilePhone is Do Not Call, the record shows Do Not Call.

​
Reading the result codes

Each phone number receives a result code. Codes marked Callable: Yes are considered safe to call.

​
Quick Scrub

The Quick Scrub tab (also embedded in the Dashboard) is for ad-hoc checks. Paste one or more phone numbers — comma or newline separated — and get immediate results split into callable and non-callable groups. Quick Scrub does not require a Salesforce record and does not save results to any record.
Quick Scrub tab with a list of phone numbers and callable versus non-callable results

​
Internal DNC (IDNC) Management

Your Internal DNC list is your organization’s private do-not-call list, separate from the national registry. Use it when a customer requests not to be called, you receive a written opt-out, or you need to block numbers beyond federal/state lists. Manage it from the IDNC Manager tab — or the IDNC panel on a record page. Enter one or more numbers and use Check Status, Add to IDNC, or Remove from IDNC. Numbers on the IDNC return result code P (Internal DNC) and are marked non-callable in all future scrubs.
Internal DNC Manager tab with phone number input, Check Status, Add to IDNC, and Remove from IDNC buttons, and a status results table

​
EBR Management

An Existing Business Relationship (EBR) is a legal exemption that can let you call a DNC-listed number. From the EBR Manager tab, use Add EBR to record a relationship for a number (EBR type, date, optional reference and brand), and Check EBR to see which numbers already have one on file.
EBR Management tab with an Add EBR form (phone number, EBR type, date, reference, brand) and a Check EBR panel
When an EBR is active, the scrub returns codes E, F, G, H, or O instead of D, indicating the number is callable under the exemption.

​
Reassignment Check (Authority+)

Under the TCPA, calling a number that was reassigned to a new subscriber after you obtained consent can create legal liability. The Reassignment Check tab (Authority+) verifies whether a number still belongs to the original subscriber.
1

Enter the number and consent date

Provide the Phone Number and the Consent Date — when the customer originally agreed to be contacted.
2

Check reassignment

Select Check Reassignment. The system checks whether the number changed hands after the consent date.
3

Review Safe Harbor

If Safe Harbor is Yes, you have TCPA safe harbor protection — the reassignment database confirms the number had not been reassigned at the time of the call.
Reassigned Number Check tab with a phone number, consent date, and Safe Harbor result

​
Bulk Scrub and Scheduling

The Bulk Scrub tab scrubs records in batches and can run on a schedule.
1

Create a schedule

Select New Schedule and choose the object — Lead, Contact, Account, or Campaign Member — and the phone fields to scrub.
2

Set the frequency

Choose how often it runs:
  • One Time — runs once on a specific date
  • Daily — runs every day at a set time
  • Weekly — runs on selected days of the week
  • Monthly — runs on a specific day of the month
3

Optionally filter records

Add filters to target specific records (for example, only Leads with Status = Hot). The record-count preview shows how many records will be processed before you save.
Records are processed in batches of 200, with one API call per batch. Records scrubbed within the rescrub interval are skipped.
Bulk Scrub tab showing a new schedule with object, phone fields, frequency, and record-count preview

​
Where Scrub Data Is Stored

Aggregate (worst-case) results are stored in custom fields on Lead, Contact, Account, and Campaign Member: When multiple phone fields are configured, each gets its own Scrub Detail (CCC_Scrub_Detail__c) child record tracking that field’s result code, status, line type, carrier, region, and last-scrubbed time. Every operation is also written to the immutable Scrub Log (CCC_Scrub_Log__c) audit object.

​
Using scrub data in Salesforce

Because the CCC fields are standard custom fields, they work everywhere:
  • Reports & dashboards — group or filter on CCC_Scrub_Status__c to report compliance across your database.
  • List views — filter to see all Do Not Call or Clean records at a glance.
  • Flow / Process Builder — trigger actions when CCC_Scrub_Status__c changes (e.g. notify a manager when a lead is flagged as a litigator).
  • Validation rules — block lead conversion or activity creation when the status is Do Not Call or Litigator.

​
Administration Notes

  • Rescrub interval — set on the Settings tab (0–23 hours); applies org-wide to panels and bulk operations.
  • Remote Site Settings — three sites must be active for all features. They are included in the package; verify them under Setup → Remote Site Settings:

​
Support