outbound-send-orchestrator

Name: outbound-send-orchestrator
Availability: InStock
Author: titta

Create Gmail drafts and schedule Slack reminders for outbound campaigns.

29|12|Updated Mar 30, 2026

Search Tags:#sales #orchestration #gmail #slack #prospecting #outbound

Ready to run

npx skills add https://github.com/matteotitta/genesys-skills --skill outbound-send-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: outbound-send-orchestrator
Source: https://github.com/matteotitta/genesys-skills/tree/main/skills/primitives/outbound/execution/outbound-send-orchestrator
Command: npx skills add https://github.com/matteotitta/genesys-skills --skill outbound-send-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the operational gap between drafting outbound emails and executing the multi-touch follow-up sequence, ensuring no lead is left uncontacted while maintaining a human-centric, non-automated appearance.

Core Features & Use Cases

Draft Orchestration: Automatically creates Gmail drafts from a validated send sheet, ensuring the operator has a ready-to-send email before any reminders fire.
Intelligent Scheduling: Schedules Slack reminders for email sends and LinkedIn follow-ups with built-in deliverability spacing and weekday-only logic.
Use Case: Use this to manage a high-touch outbound campaign where you want to manually click send on emails to maintain deliverability, while relying on the AI to handle the complex timing of follow-up tasks.

Quick Start

Run the outbound-send-orchestrator skill to process the current SEND_SHEET.md and schedule all pending Gmail drafts and Slack reminders.

Frequently Asked Questions about outbound-send-orchestrator

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

FAQPage Schema

How do I orchestrate outbound email sends with human review using Gmail and Slack?▼

You can orchestrate outbound sends by creating Gmail drafts from a validated send sheet and scheduling Slack reminders for manual follow-ups, ensuring human review of email content before sending. This approach enforces strict per-contact ordering and deliverability-focused timing constraints.

What is human-in-the-loop outbound campaign orchestration for B2B sales?▼

Human-in-the-loop outbound orchestration is a B2B sales process where an operator manually clicks send on drafted emails to maintain deliverability, while AI handles the complex timing of multi-touch follow-up tasks across Gmail and Slack. This ensures no lead is left uncontacted while maintaining a non-automated appearance.

Does this outbound send orchestration require Google Workspace and Slack integrations?▼

Yes, this outbound send orchestration requires Google Workspace and Slack MCP integrations to function. Google Workspace enables Gmail draft creation, while Slack delivers the scheduled follow-up reminders for email sends and LinkedIn engagement tasks.

How do I schedule Slack reminders for outbound prospecting follow-ups?▼

You schedule Slack reminders for outbound prospecting by running the orchestrator on your send sheet, which applies built-in deliverability spacing and weekday-only logic. It automatically schedules reminders for email sends and LinkedIn follow-ups to maintain strict per-contact ordering.

Can I maintain email deliverability while running a high-touch outbound campaign?▼

Yes, you can maintain email deliverability during high-touch outbound campaigns by using this orchestrator to generate Gmail drafts requiring a manual click to send. The system applies deliverability-focused spacing and weekday-only logic to all scheduled Slack follow-up reminders.

What is the best way to manage multi-touch follow-up sequences without full automation?▼

The best way to manage multi-touch follow-up sequences without full automation is using a draft orchestration workflow that separates email drafting from sending. This synchronizes Gmail draft creation with Slack-based reminders, allowing manual review while AI handles complex timing constraints.