← ClaudeAtlas

revenueos-sales-follow-uplisted

RevenueOS Sales Follow-up — draft first-touch cold emails for newly discovered prospects from the business's own canon, and process inbound replies, bounces and STOP requests. Use when the user says "draft follow-up emails", "write outreach for these leads", "check for replies", "who unsubscribed", or asks RevenueOS to send a cold email — sending always requires an explicit approval step from the human.
unempyd/revenueos · ★ 7 · AI & Automation · score 76
Install: claude install-skill unempyd/revenueos
# RevenueOS Sales Follow-up RevenueOS Sales Follow-up drafts deterministic, personalised first-touch emails for prospects found by RevenueOS Lead Discovery, and reads the inbox to classify replies, bounces and unsubscribe requests. **Every send requires a human approval step — this capability never sends on its own initiative.** ## When to use this - New prospects exist (from RevenueOS Lead Discovery) and need a first-touch draft. - The user wants to check for replies, bounces, or STOP requests on a sending mailbox. - The user explicitly asks to send an approved draft. ## How to run it CLI: ```bash revenueos run outreach # draft follow_up actions for undrafted prospects revenueos run inbox # classify replies / bounces / STOPs against sent mail revenueos today # review drafts awaiting approval revenueos approve <id> # approve one draft revenueos execute <id> # send it (only after approve) ``` MCP tool: - `revenueos_draft_followups()` — drafts first-touch emails for qualified prospects; never sends. Each draft becomes a `follow_up` action. - `revenueos_approve(action_id)` then `revenueos_execute(action_id)` — the only path that sends an email, and only for an action already approved. - `revenueos_today()` / `revenueos_results()` — review drafts / delivery and reply outcomes. ## Inputs No file upload — drafts are built from the business's own canon (offer, differentiators, pain points, tone) plus each lead's qu