FCC & Compliance
Regulatory protection from liability for providers that block or mitigate calls in good faith using reasonable analytics and documented processes.
Existing safe harbors protect providers that block calls based on reasonable analytics incorporating STIR/SHAKEN data, and that block traffic from bad-actor upstream providers after notification, provided a redress mechanism exists for erroneous blocking.
The FCC has separately sought comment on whether providers deploying effective AI-based KYC and fraud detection should receive protection from liability for illegal calls that nonetheless get through.
Safe harbor protection depends on documented, reasonable process. The blocking you do is only defensible if you can show how the decision was made and how a customer can appeal it.
The FCC registry where every voice service provider must file a certification describing its robocall mitigation program.
The process of verifying who a voice customer really is, what traffic they intend to send, and whether they are authorized to use the numbers they present.
Analytics-driven tags such as 'Scam Likely' or 'Spam Risk' that terminating carriers and handsets apply to inbound calls.
The FCC authorization a carrier needs to provide interstate or international telecommunications service — and which the FCC can revoke.
SipShield scores live SIP traffic with patented AI so the controls behind this term run automatically — and leave the audit trail regulators expect.