suppression-logic
Use to define guardrails that pause signal-driven plays when accounts are risky, saturated, or in-flight elsewhere.
When & Why to Use This Skill
The Suppression Logic skill provides a robust framework for defining and managing guardrails within automated sales and marketing workflows. It ensures brand integrity and operational efficiency by intelligently pausing signal-driven plays when accounts are identified as high-risk, over-saturated, or already engaged in conflicting outreach cycles. By centralizing suppression triggers, it prevents redundant communication and aligns cross-functional teams on account engagement boundaries.
Use Cases
- Global Do-Not-Touch Rules: Implement centralized suppression logic to prevent marketing, sales, and customer success teams from overlapping or sending conflicting messages to the same account.
- Compliance and Risk Mitigation: Automatically halt automated outreach for accounts flagged for legal sensitivities, financial delinquency, or ongoing security incidents to protect the company's reputation.
- Workflow Conflict Resolution: Coordinate complex multi-channel plays by suppressing accounts that are already 'in-flight' in other high-priority sequences, ensuring a streamlined customer experience.
- Intent Signal Auditing: Use the framework to investigate and resolve why high-intent accounts are failing to trigger automation, identifying hidden data conflicts or outdated suppression rules.
| name | suppression-logic |
|---|---|
| description | Use to define guardrails that pause signal-driven plays when accounts |
Suppression Logic Playbook Skill
When to Use
- Building global do-not-touch rules shared across marketing, sales, and success workflows.
- Investigating why an account never triggers despite strong intent scores.
- Coordinating with legal, finance, or product teams on sensitive outreach windows.
Framework
- Reason Taxonomy – categorize suppression triggers (legal/compliance, commercial conflicts, lifecycle constraints, technical issues).
- Detection Methods – outline data sources and queries that flag each trigger (support tickets, security incidents, open opps, payment status).
- Routing & Ownership – assign who can override or expire each suppression (CSM, legal, exec sponsor).
- Duration Logic – define cooling periods, review cadences, and auto-expiration rules.
- Audit Trail – log change history, approvals, and tie-ins to automation or orchestrator commands.
Templates
- Suppression matrix (reason, trigger condition, owner, duration, override path).
- Compliance checklist for regulated industries (financial services, healthcare).
- Alert + reporting format for surfaced conflicts.
Tips
- Mirror CRM/MAP suppression lists to prevent channel drift.
- Create heartbeat alerts when suppression counts spike unexpectedly.
- Pair with
signal-scoringadjustments so suppressed accounts stop draining rep capacity.