Location: Campaign Page → TCPA Compliance
Last Updated: 10/16/2025
📝 Overview
Campaigns can be configured to use a customer’s own third-party TCPA compliance provider instead of Moja’s built-in default.
This allows organizations with legal, contractual, or operational requirements to screen calls using their preferred compliance vendor (such as Blacklist Alliance), while still supporting Moja’s default TCPA scrubbing where applicable.
⚙️ Provider Selection
The TCPA Compliance panel includes a provider selector that determines how inbound calls are screened for a campaign.
Available options include:
🟦 Default (Whitelist Data)
Uses Moja’s built-in TCPA scrubbing logic.⛔ Blacklist Alliance
Connects the campaign to a customer-owned Blacklist Alliance account.🚫 Disabled
Disables TCPA scrubbing for the campaign.
🟨 Note: Provider selection applies at the campaign level and affects all inbound calls for that campaign.
🔧 Provider Configuration
When a third-party provider is selected, additional configuration fields become available:
🔑 API Key
Enter the credential provided by the compliance vendor.🧩 API Version
Select the supported version (v1,v2, orv3).
These settings enable real-time verification of inbound calls against the selected TCPA provider.
🧪 Test Connection
A Test Connection button is available to validate provider credentials before saving.
Performs a live API check using a safe test number (
222-333-4444)Displays success or error feedback directly in the UI
🟩 Best Practice: Always test credentials during onboarding to confirm connectivity before activating traffic.
📊 Logging & Runtime Behavior
TCPA enforcement and provider behavior are handled consistently at runtime:
Calls that match a provider’s TCPA list are terminated before routing
Matches and enforcement actions are logged for audit and review
If a provider API fails or times out, calls continue (fail-open)
Errors, timeouts, and provider responses are captured in logs and metrics
All TCPA actions are tagged by provider for visibility
🎯 Why This Matters
Many enterprise customers are required to use a specific third-party TCPA provider due to compliance policies or contractual obligations.
This configuration:
Enables provider choice without engineering involvement
Preserves Moja’s default TCPA protection for other campaigns
Establishes a consistent model for supporting additional providers
Improves auditability through provider-tagged enforcement logs
💡 Example Use Cases
Supporting an enterprise client that must use Blacklist Alliance
Verifying third-party API credentials during customer onboarding
Comparing enforcement results between Moja’s default scrubbing and a customer-selected provider
Reviewing provider-tagged logs to confirm external TCPA checks are functioning correctly
🚀 Getting Started
Open a Campaign
Scroll to the TCPA Compliance section
In Provider, select Blacklist Alliance
Enter the API Key and choose an API Version
Click Test Connection to validate credentials
Save the campaign
✅ Calls for this campaign will now be screened using the selected provider.
🧭 Roadmap
Planned enhancements include:
➕ Support for additional TCPA providers using the same configuration model
📊 Provider-based TCPA metrics in Analytics dashboards for monitoring and audits