Back to Integrations

PureCallerID

The PureCallerID integration gives LeadExec real-time phone-number validation, DNC screening, and TCPA risk checks so only high-quality, compliant leads enter your sales pipeline.

Source Type:
Data Validation

Delivery Format:
API

Integration Type:
Real-Time Phone Screening

Website:
PureCallerID Website

Overview

The PureCallerID Single Lead Loading integration gives LeadExec real-time phone-number validation and compliance screening. By checking every new lead against PureCallerID’s service for inactivity, Do-Not-Call (DNC), TCPA litigation risk, and other flags, the integration ensures only high-quality, compliant leads enter downstream workflows.

How It Works

When a lead is posted to LeadExec, the platform:

  1. Checks campaign settings. If the PureCallerID toggle is enabled, processing continues.
  2. Maps lead fields (phone, zip, name, address, etc.) to the API payload using campaign-level mapping UI.
  3. Sends a POST request to the Single Lead Loading API, including campaignId, listName, and an apiToken in the JSON body.
  4. Parses the response—status (Accepted / Rejected), reason (INACTIVE, DNC, etc.), and message—and stores it with the lead record.
  5. Applies criteria rules. Leads may be automatically rejected, flagged, or sent to QA based on the returned values.

Admins may choose to run multiple integrations in parallel or sequentially and set an Integration Sort order—once a lead is rejected, subsequent sequential integrations are skipped.

Benefits
  • Higher Lead Quality: Instantly filters out inactive or invalid phone numbers and DNC hits.
  • Regulatory Compliance: Screens for TCPA-related risks such as litigator numbers to avoid costly fines.
  • Automated Workflows: Criteria-based rejection and flagging reduce manual QA time.
  • Flexible Execution: Parallel/sequential settings keep overall lead-processing time low even when multiple integrations run together.
  • Future-proofing: The design allows adding fields like activity_score, knownLitigatorCheck, and carrier in later phases without re-work.
Auth and Settings
Setting Description
API Token Secret token provided by PureCallerID; included as apiToken in the request body
campaignId PureCallerID campaign identifier
listName Dialer/list name inside PureCallerID

All three values are stored per campaign in LeadExec’s integration settings UI.

Data Exchange
Inbound (PureCallerID → LeadExec)

None – PureCallerID returns a synchronous JSON response to LeadExec; no webhooks are sent back.

Outbound (LeadExec → PureCallerID)

Action / Endpoint

Action / Endpoint Description
POST /singleLeadLoading (REST JSON) Validates one lead against PureCallerID.

The exact host URL is provided with your PureCallerID credentials; parameters include campaignId, listName, apiToken, plus mapped lead fields.

Integration Fields (LeadExec → PureCallerID Payload)

Integration Field JSON Key Required Notes
Phone phone Yes Primary phone number
Zip zip Yes¹ ¹Often required for location-based checks
First Name firstName No
Last Name lastName No
Address address No Street, city, state
… … No Any extra mapped field (email, etc.)
Campaign ID campaignId Yes Credential-style parameter
List Name listName Yes Credential-style parameter
API Token apiToken Yes In header or body for authentication

(Field requirements come from the Discovery doc’s Capture & Mapping section.)

PureCallerID Response Fields (JSON → LeadExec)
Key Example Values Purpose
status Accepted, Rejected Overall validation result
reason INACTIVE, DNC, TCPA_FLAG, INVALID Explains rejection / risk type
message “Inactive phone number” Human-readable detail

These three drive criteria rules in LeadExec.

Example Criteria Rules
  • Reject if status = Rejected and reason in (INACTIVE, DNC, TCPA_FLAG).
  • Send to QC when status = Accepted but reason = SUPPRESSED.
Important Notes
  • The integration is delivered behind a feature flag; enable it per campaign once credentials are set.
  • Development keys may have low daily quota—coordinate with PureCallerID for production capacity.
  • Future enhancement requests (e.g., activity_score, carrier) are tracked under Jira LEAD-3069 and scoped for a later phase.

Amazing support is at the heart of everything we do.

ClickPoint provides 24 hour chat support, extensive product documentation, and weekly training sessions.