TCPA Compliance

We give you the infrastructure. You own the policy.

TCPA compliance is an operational discipline, not a carrier feature. SIPNEX provides the carrier-layer tools — attestation, recording, CDRs, traffic monitoring — that make your compliance program defensible. Consent, DNC, calling hours, and abandon rates are your responsibility. We make sure the infrastructure supports it.

A-Level STIR/SHAKEN Attestation

Every call signed with our own SP-KI certificate. Verified caller identity reduces spam labeling and supports your compliance posture — calls that reach recipients are calls that comply with consent.

Call Recording Infrastructure

Carrier-level recording on all trunks. Linked to CDRs with timestamps. Use for consent documentation, quality assurance, training, and dispute resolution. Two-party consent state workflows supported.

Real-Time CDR Access

Call detail records with timestamps, durations, calling/called numbers, and dispositions. Feed your compliance auditing — verify calling hours, track DNC hits, document abandon rates.

Carrier Traffic Monitoring

SIPNEX monitors originating traffic for patterns associated with illegal robocalling. Anomaly detection protects the network and alerts operators to potential issues before they become regulatory problems.

Robocall Mitigation Database

SIPNEX maintains an active RMD filing with complete STIR/SHAKEN implementation. Your calls originate from a carrier that meets all FCC compliance requirements. Downstream carriers accept our traffic without blocking.

Acceptable Use Policy

Our AUP prohibits illegal calling practices — spoofing, DNC violations, illegal robocalling. The AUP is a contractual compliance layer that protects our network reputation and all customers on it.

Carrier responsibility vs operator responsibility.

SIPNEX PROVIDESYOU OWN
Caller ID verificationA-level STIR/SHAKEN attestationNumber authority documentation
Call recordingCarrier-level recording infrastructureRecording consent & disclosure
Call dataReal-time CDRs with timestampsCompliance auditing & reporting
DNC complianceCDR data for audit verificationList scrubbing & suppression
Calling hoursTrunk available 24/7Time zone enforcement in dialer
Abandon rateUnlimited channels (no throttling)Adaptive pacing configuration
ConsentCapture, storage, revocation handling
Network complianceRMD filing, AUP enforcementCampaign-level policy

Frequently asked questions.

What is TCPA?
The Telephone Consumer Protection Act (47 U.S.C. § 227) is the federal law governing autodialed calls, prerecorded messages, and text messages to consumers. It establishes consent requirements (prior express consent for informational calls, prior express written consent for telemarketing), Do Not Call obligations, calling hour restrictions (8am–9pm recipient local time), and abandon rate limits (3% for predictive dialers). Penalties are $500 per negligent violation and $1,500 per willful violation with no cap.
What does the carrier provide for TCPA compliance?
SIPNEX provides carrier-layer infrastructure that supports your TCPA compliance program: A-level STIR/SHAKEN attestation (verified caller identity on every call), call recording infrastructure (for consent documentation and quality assurance), real-time CDR access (timestamps, durations, and dispositions for compliance auditing), and carrier-level traffic monitoring (anomaly detection for calling pattern issues). These are the tools. Your compliance policy determines how you use them.
What is the operator's responsibility?
Consent capture and storage (obtaining and documenting valid consent for every number you dial). DNC scrubbing (National Registry every 31 days, company-specific lists, state lists). Calling hour enforcement (8am–9pm in the recipient's local time zone, with state-specific restrictions). Abandon rate management (under 3% for predictive dialing, measured per campaign over 30 days). Campaign content compliance (required disclosures, opt-out instructions). Record keeping sufficient to defend against litigation.
Does STIR/SHAKEN replace TCPA compliance?
No. They operate at completely different layers. STIR/SHAKEN verifies caller identity at the carrier level — it determines whether your call displays as verified or gets flagged as spam. TCPA is a consumer protection law governing consent, DNC, and calling practices. You can have perfect A-level attestation and still face massive TCPA liability if you call without consent. You need both: the right carrier for attestation and your own compliance program for everything else.
How does SIPNEX help with call recording compliance?
SIPNEX provides carrier-level call recording on all trunks. Recordings are linked to CDRs with timestamps. For two-party consent states (15 states require all parties to consent to recording), you must play a disclosure before recording — SIPNEX's recording infrastructure supports this workflow. We provide the recording capability. You configure the disclosure, manage consent, and comply with state-specific recording laws.
Can SIPNEX help with DNC scrubbing?
DNC scrubbing is the operator's responsibility. SIPNEX does not perform DNC scrubbing on your behalf — we do not have access to your lead lists and we cannot determine your consent status for individual numbers. We provide CDR data that supports compliance auditing (verifying that no calls were placed to DNC numbers), but the scrubbing itself must happen in your CRM or dialer before leads enter the hopper.
What happens if I violate TCPA on a SIPNEX trunk?
TCPA liability falls on the caller (the entity that placed the call), not the carrier. However, SIPNEX monitors for traffic patterns associated with illegal robocalling and may investigate accounts that generate unusual complaint volumes or calling patterns. Our Acceptable Use Policy prohibits illegal calling practices. We provide the infrastructure for compliant operations — abuse of that infrastructure violates the AUP and can result in service suspension.
Is VICIdial an ATDS under TCPA?
After the Supreme Court's 2021 Facebook v. Duguid decision, VICIdial (which dials from uploaded lists, not random/sequential number generation) likely does not qualify as an ATDS under the federal TCPA. However, some state laws define ATDS more broadly (notably Florida), and the FCC's ongoing interpretive guidance continues to evolve. The safest approach: treat your dialer as an ATDS and obtain prior express written consent for all telemarketing calls. See our TCPA compliance checklist blog post for the full analysis.

Compliance infrastructure from the carrier.

We give you the tools. You own the policy. Together it works.