TCPA Compliance

SkyNet365 is built for regulated outbound contact. Every lead carries the metadata buyers need to evaluate their own Telephone Consumer Protection Act (TCPA) obligations before dialing or texting.

What the platform records

• Vendor-supplied consent context per lead, including the originating source and timestamp of capture, retained immutably on the lead record.
• Per-source identity: every lead is traceable to a registered vendor and a named lead source with rotatable signing credentials.
• A full disposition history — buyers mark Do Not Call dispositions, which propagate to the lead record and inform source quality scoring.

What vendors agree to

• Leads must originate from forms or flows where the consumer provided express consent to be contacted, captured at the time and place stated in the lead payload.
• Vendors warrant the accuracy of consent metadata; misrepresentation is grounds for source suspension and network removal.

What buyers remain responsible for

• Compliance with TCPA, state mini-TCPA statutes, and Do-Not-Call registries in their outreach. The platform supplies traceability; it does not replace buyer-side legal review.
• Honoring consumer opt-outs received during their own outreach.

Questions about a specific lead's consent trail can be raised through the dispute flow on the lead record or by contacting the network operator.