Professional review status
No professional domain review recorded
This bundle covers regulatory subject matter. It is a source-aware research aid, not professional advice, and should not be the sole basis for consequential decisions.
Review before reliance: A qualified legal, compliance, or other domain professional appropriate to the question and jurisdiction.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A marketing team wants to text a purchased U.S. lead list tomorrow using an SMS platform. It says the vendor represented that the leads are "opted in." The team provides the draft text but not the lead source records, consent disclosure, seller identity on the form, timestamped consent logs, revocation logs, STOP handling, National or internal DNC screening.
Without the bundle
If the vendor says the leads opted in, you may be able to send the text as long as you include opt-out language like "Reply STOP to unsubscribe." Check that your SMS platform has unsubscribe handling enabled and keep records. This answer is intentionally weak: it treats a vendor assurance as enough, omits official source categories, does not separate evidence from assumptions, and does not block the risky action.
Using the bundle
Based on the evidence provided, this campaign is not ready for a TCPA compliance conclusion or send approval. A vendor statement that leads are "opted in" does not by itself verify consent scope, seller identity, revocation status, DNC screening, platform suppression behavior, or related telemarketing obligations. Source note: This draft would require current FCC TCPA/robotext guidance, current eCFR 47 CFR 64.1200, current statutory text if statutory language matters, FTC TSR and National Do Not Call sources if telemarketing is involved, and the team's lead-source, consent, revocation, DNC, vendor, platform, and message evidence. Those user records were not provided.
Why this is better: Using the TCPA Source-Awareness Check, the baseline answer would fail because it relies on vendor assurance, omits source categories, does not ask for consent or revocation records, and does not block the send. The bundle-assisted answer is stronger because it gives a bounded direct answer, includes a source note, separates provided and missing evidence, asks for official source inspection, and requires professional.
Inspect this example in the repositoryOverview
TCPA Overview
Defines the source scope, applicability framing, and safety boundaries for TCPA compliance work.
Read the fileWorkflow
TCPA Outreach Triage
Triage a call, text, robocall, robotext, or fax scenario with source discipline before any compliance conclusion.
Read the fileTemplate
Source-Aware TCPA Compliance Brief
Output format for TCPA-sensitive outreach questions that separates official sources, user evidence, assumptions, and missing verification.
Read the fileQuality rubric
TCPA Source-Awareness Check
Rubric for evaluating whether an answer handles TCPA-sensitive outreach questions with source discipline and safety.
Read the fileIs this bundle right for your task?
Who it is for
- Compliance, legal, risk, security, operations, and product teams assessing TCPA (Telephone Consumer Protection Act)
- Teams working in cross-industry, sales, marketing
When to use it
- A TCPA (Telephone Consumer Protection Act) question needs to be scoped to the correct rule, guidance, regulator, date, and affected entity.
- A draft conclusion needs its stated facts, missing evidence, source citations, and professional-review handoff checked.
What you need to provide
- The jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer.
- Current official sources plus the policies, contracts, records, system evidence, and missing facts relevant to the situation.
Tasks and expected outputs
Questions it helps answer
- Triage U.S. call, text, robocall, robotext, and fax outreach questions without inventing legal conclusions.
- Separate official FCC, FTC, eCFR, statutory, and user-provided evidence before compliance conclusions.
- Produce source-aware TCPA compliance briefs for professional review.
What it helps produce
- source-aware TCPA compliance brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the jurisdiction, entity and relationship facts, applicable dates, exact question, and accountable professional reviewer. Ask the agent to assess TCPA (Telephone Consumer Protection Act) and draft source-aware TCPA compliance brief that separates stated facts, assumptions, missing evidence, relevant source sections, and actions requiring professional approval. Begin with fcc.gov — General / Telemarketing And Robocalls, then confirm that the reference is current and applicable. Inspect TCPA Overview before drafting.
Context path: bundles/compliance/tcpa
What the bundle includes
Frameworks
- source-evidence matrix
- outreach-channel triage
- consent and revocation evidence review
- do-not-call and suppression alignment
Evaluations
- TCPA source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Final legal or compliance conclusions, filings, notices, or operational changes without current source review and accountable professional approval.
Known limitations
- This bundle is a compliance hub, not legal advice or a full section-by-section TCPA treatise.
- Scenario-specific answers require current official source inspection, user-provided outreach evidence, and qualified legal or compliance review.
- State mini-TCPA, sector-specific, privacy, platform, carrier, contractual, and international communications requirements must be inspected separately when relevant.
Safety notes
- Require qualified legal or compliance professional review before relying on outputs for campaign, calling, texting, faxing, enforcement, contractual, or regulatory decisions.
- Do not use this bundle for spam, spoofing, deceptive lead generation, phishing, evasion, consent laundering, list abuse, or ignoring opt-outs.
- Require explicit confirmation before placing calls, sending texts, sending faxes, uploading lists, exporting contacts, changing consent capture, changing DNC or suppression logic, contacting regulators, or sending legal communications.