Multichannel Enrollment Rules

    1

    One enrollment and one exit gate across email and LinkedIn, so channels never collide.

    Secure checkout via Stripe

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+17 more

    See it in action

    You say

    We're using Apollo for email and Haystack for LinkedIn. We need rules so prospects don't get slammed on both at once and to make sure a LinkedIn reply stops the email thread.

    Your agent does

    1. Enrollment Object: Keyed on email_hash.
    2. Exit Gate: Shared Boolean 'active_engagement'. Both Apollo and Haystack webhooks update this to FALSE on reply.
    3. Order: LinkedIn Connect -> 2 Day Gap -> Email 1.
    4. Race Rule: Email executes check 5ms before send; LinkedIn holds if Email status is 'pending'.

    What you get

    Prevent prospects from receiving duplicate messages across different platforms.Synchronize sequence exit gates so one reply stops all outreach channels.Establish logical delays and touchpoint ordering between social and email.Fix attribution errors where one reply is counted twice in reporting.

    About this skill

    The problem

    Running multi-channel outreach often leads to prospects getting double-messaged or receiving follow-ups after they have already replied. Disconnected data streams cause inflated conversion metrics and damaged brand reputation due to colliding sequences.

    What it does

    • Models enrollment as a single entity per person rather than separate per-channel rows.
    • Establishes a centralized exit gate that halts all activity across all channels upon a single reply.
    • Defines logical channel ordering and minimum time gaps to ensure messages reinforce each other.
    • Creates explicit race condition rules to prevent simultaneous sends from different platforms.
    • Standardizes attribution so one conversion is counted once, mapped to the specific source channel.

    Why this beats prompting it yourself

    Generic prompts often forget the technical friction of race conditions and shared identifiers. This skill enforces a data-first architecture that treats LinkedIn and email as attributes of a single prospect lifecycle, preventing the common "double-tap" error that occurs when AI is asked to just "write a sequence."

    Use cases

    • Adding LinkedIn touchpoints to an existing cold email infrastructure.
    • Synchronizing outreach for teams using both automated and manual social touches.
    • Consolidating fragmented prospect data into a single source of truth for attribution.
    • Designing complex sequences where social proof must precede direct inbox outreach.

    Most premium skills are on a weekly review cycle. Fixes and improvements ship as updates, and buyers receive release notes by email. Part of the Mambabuilt catalog. Packs and the full bundle are available at mambabuilt.com.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • One-time purchase, yours forever

    Listedtoday

    Frequently Asked Questions