playbooks

home / skills / gtmagents / gtm-agents / suppression-logic

suppression-logic skill

/plugins/intent-signal-orchestration/skills/suppression-logic

This skill helps you enforce global suppression rules across marketing, sales, and success workflows, reducing risky outreach and ensuring compliant timing.

npx playbooks add skill gtmagents/gtm-agents --skill suppression-logic

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: suppression-logic
description: Use to define guardrails that pause signal-driven plays when accounts
  are risky, saturated, or in-flight elsewhere.
---

# 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
1. **Reason Taxonomy** – categorize suppression triggers (legal/compliance, commercial conflicts, lifecycle constraints, technical issues).
2. **Detection Methods** – outline data sources and queries that flag each trigger (support tickets, security incidents, open opps, payment status).
3. **Routing & Ownership** – assign who can override or expire each suppression (CSM, legal, exec sponsor).
4. **Duration Logic** – define cooling periods, review cadences, and auto-expiration rules.
5. **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-scoring` adjustments so suppressed accounts stop draining rep capacity.

---

Overview

This skill defines guardrails that pause signal-driven plays when accounts are risky, saturated, or currently engaged elsewhere. It provides a pragmatic framework, templates, and detection guidance to enforce global do-not-touch rules across marketing, sales, and customer success. Use it to prevent wasted outreach, ensure compliance, and centralize suppression ownership and auditability.

How this skill works

The skill codifies a reason taxonomy and detection methods that map data sources to suppression triggers (e.g., open opportunities, payment failures, security incidents). It defines routing and ownership for overrides, duration logic for cooling periods and auto-expiration, and an audit trail for approvals and change history. Templates and alerts make it straightforward to operationalize suppressions across systems.

When to use it

  • Create global do-not-touch rules shared across sales, marketing, and CS
  • Investigate accounts with high intent that never enter outreach workflows
  • Coordinate outreach pauses with legal, finance, or product review windows
  • Prevent reps from wasting capacity on saturated or conflicted accounts
  • Automate temporary suppression during security, billing, or compliance incidents

Best practices

  • Start with a concise reason taxonomy (legal, commercial conflict, lifecycle, technical)
  • Map each trigger to concrete data sources and queries (CRM fields, support tickets, billing status)
  • Assign explicit owners and override paths for each suppression reason
  • Define durations and review cadences; prefer auto-expiry with human review for long pauses
  • Log every suppression change and tie entries to automation/orchestrator commands
  • Align CRM/MAP suppression lists to avoid channel drift and duplicate work

Example use cases

  • Pause marketing cadences for accounts flagged with active security incidents until cleared by security
  • Suppress outreach for accounts with an open contract negotiation owned by sales to avoid contact conflicts
  • Automatically block plays for customers in billing delinquency until payment resolves or a finance owner approves outreach
  • Temporarily stop campaigns targeting customers in regulated industries during compliance reviews
  • Create heartbeat alerts when suppression counts spike, triggering a forensic review

FAQ

How long should a suppression last?

Use reason-based durations: short cooling periods (days) for tactical issues, longer auto-expiry with review (weeks) for legal or commercial conflicts.

Who can override a suppression?

Assign overrides to role-based owners (CSM, legal, executive sponsor) and require an auditable approval in the system before lifting.