Sending
Delivering the sequence without burning the domain.
Workflow
Step 1Emails Ready
No playbook note for this step yet — the workflow stands on its own.
Why it matters
- Great copy on a bad sending infra = spam folder. Deliverability is a compounding asset: a clean domain earns higher inbox rates; a burned one is expensive to recover.
Best practices
- Warm up and rotate inboxes — no single inbox blasts.
- Throttle per domain and per day to protect reputation.
- Track bounces, opens, replies, and spam complaints separately.
- Stop sequences on hard bounces and bad replies immediately.
Common mistakes
- Sending 500/day from one inbox — fast death.
- Ignoring bounces → reputation tanks silently.
- No SPF/DKIM/DMARC setup before launch.
Key questions
- Is deliverability protected while we scale volume?
- What is the reply rate, not just the open rate?
- When do we stop a sequence?
Agents that drive this
SniperHygiene
Tools we use · alternates in [ ]
Smartlead[ Instantly, Lemlist, Woodpecker ]Instantly[ Smartlead, Lemlist ]n8n[ Zapier, Make, Airflow ]