# Suppression logic Human Guide

## What This Is For
When to Use Building global do-not-touch rules shared across marketing, sales, and success workflows. It gives the agent a clearer input/output frame for suppression logic: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Suppression logic agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for suppression logic.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Suppression logic guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- 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.
- **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.
- Suppression matrix (reason, trigger condition, owner, duration, override path).
- Compliance checklist for regulated industries (financial services, healthcare).
- Alert + reporting format for surfaced conflicts.
- Mirror CRM/MAP suppression lists to prevent channel drift.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Investigating why an account never triggers despite strong intent scores.

## Copy-And-Paste Prompt
```text
Use the Suppression logic human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `suppression-logic`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 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.

---