opt-out-handling

Automate unsubscribe and DNC request suppression with provenance logging.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/aura-farming/escc --skill opt-out-handling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opt-out-handling
Source: https://github.com/aura-farming/escc/tree/main/skills/opt-out-handling
Command: npx skills add https://github.com/aura-farming/escc --skill opt-out-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of handling unsubscribe and DNC requests, ensuring compliance with legal requirements and streamlining the workflow.

Core Features & Use Cases

  • End-to-End Processing: Detect, suppress, record, and confirm unsubscribe/DNC requests.
  • Trigger Handling: Automatically triggered by specific signals in messages or verbal requests.
  • Compliance Workflow: Ensures suppression across all sequences and lists, with provenance recording and deadline confirmation.
  • Use Case: When a contact requests to be removed from communications, this Skill automatically suppresses them and logs the necessary information for compliance.

Quick Start

Invoke the opt-out-handling skill when a contact requests to unsubscribe or be removed from communications.

Frequently Asked Questions about opt-out-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate unsubscribe and DNC request processing for compliance?

Automate unsubscribe and DNC request processing by detecting opt-out signals, suppressing contacts across all sequences, and logging provenance for compliance records. This ensures legal suppression requirements are met automatically when contacts request removal.

What is legal suppression and how does it work with DNC requests?

Legal suppression for DNC requests involves detecting opt-out signals from messages or verbal requests, then suppressing the contact across all sequences and lists. Provenance is logged to maintain compliance records required by legal jurisdictions.

Do I need CRM integration to handle unsubscribe suppression across sequences?

Yes, CRM integration is required for suppression and logging. The skill needs jurisdiction-specific rules and CRM connectivity to automatically suppress contacts across all sequences and record provenance for compliance tracking.

How do I ensure compliance workflow records provenance when contacts opt out?

Compliance workflow records provenance by automatically logging the opt-out signal source, suppressing the contact across all active sequences, and confirming the suppression deadline. This creates auditable records tied to jurisdiction-specific rules.

Can I use compliance automation for DNC processing across different legal jurisdictions?

Yes, DNC processing supports different legal jurisdictions when jurisdiction-specific rules are provided. The skill applies the appropriate suppression and deadline confirmation logic based on the applicable compliance requirements for each region.

What triggers the automatic suppression of contacts in an unsubscribe workflow?

Automatic suppression is triggered by specific opt-out signals detected in messages or verbal requests. Once triggered, the contact is suppressed across all sequences and lists, with provenance recorded for compliance.