send-gateway

Enforce centralized outbound messaging rules across email, DMs, and phone logs.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/CC90210/CMO-Agent --skill send-gateway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send-gateway
Source: https://github.com/CC90210/CMO-Agent/tree/main/skills/send-gateway
Command: npx skills add https://github.com/CC90210/CMO-Agent --skill send-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of fragmented, uncoordinated outbound communication by providing a single, architecturally enforced chokepoint for all emails, DMs, and messages, preventing duplicate contacts and ensuring compliance.

Core Features & Use Cases

  • Centralized Compliance: Automatically enforces CASL compliance, suppression lists, and cooldown windows across all communication channels.
  • Idempotency Enforcement: Prevents duplicate messaging by maintaining a unified interaction ledger that tracks lead contact history across multiple engines.
  • Use Case: When an outreach engine attempts to contact a lead, the gateway checks the 72-hour cooldown and daily volume caps before authorizing the send, ensuring the agent never violates communication policies.

Quick Start

Use the send-gateway to route an outbound email to the specified lead while enforcing all active cooldown and compliance rules.

Frequently Asked Questions about send-gateway

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

FAQPage Schema
How do I prevent duplicate outbound messaging from autonomous agents across multiple channels?

Preventing duplicate outbound messaging requires a centralized interaction ledger that tracks contact history across all engines. This gateway enforces idempotency by checking this unified ledger, ensuring autonomous agents never send redundant emails or social DMs to the same lead.

How does automated outbound communication enforce CASL compliance and cooldown windows?

Automated outbound communication enforces CASL compliance by validating suppression lists and applying mandatory cooldown periods before authorizing any send. The gateway checks a 72-hour cooldown window against the interaction ledger, blocking messages that violate regulatory communication policies.

What's the best way to manage daily volume caps for multi-channel messaging workflows?

Managing daily volume caps for multi-channel messaging is best handled by routing all emails and phone logs through a single architectural chokepoint. This gateway validates daily send limits against a centralized ledger, preventing autonomous agents from exceeding volume caps.

Do I need an existing database schema to use a centralized messaging gateway?

Yes, an existing database schema is required to integrate with the centralized messaging gateway. The system relies on the core send_gateway.py script to maintain architectural integrity, querying your database's interaction ledger to validate cooldowns and compliance rules.

Why does my outreach engine still send emails when a lead is on a suppression list?

Outreach engines send emails to suppressed leads when they bypass a centralized compliance chokepoint. Routing all outbound engines through this gateway enforces suppression lists and CASL rules globally, preventing individual agents from authorizing non-compliant messages.

Can I route phone logs and social DMs through the same compliance chokepoint as email?

Yes, you can route phone logs and social DMs through the same compliance chokepoint as email. The gateway manages multi-channel messaging by validating cooldown periods and daily volume caps across all channels against a unified interaction ledger.