Domain & Inbox Setup
Cold email should never run from your main domain. This skill builds the disposable infrastructure that protects it: short branded domain variations, availability checks and purchase on Dynadot, nameserver handoff to Zapmail, two inboxes per domain, and the warmup period that actually earns inbox placement. It ends with senders verified and connected inside EmailBison, ready for a campaign to use.
Pipeline Playbooks · Open Source, MIT Licensed
Takes you from zero to warmed, connected sending infrastructure: generate domains, buy them, route through Zapmail, provision inboxes, and sit through the 2 to 3 week warmup no one should skip.
When to use this
- Starting cold email from zero, no infrastructure yet
- Adding volume and need more domains and inboxes
- A domain got burned and needs replacing
- Someone says set up my domains or I need more senders
What it covers
- The full flow: generate, purchase, nameservers, connect, provision, warmup, connect to EmailBison
- Generating short domain variations in two tiers (prefix+brand, brand+suffix)
- How many domains to buy: 10 domains gets roughly 60 sends/day at safe volume
- Dynadot bulk availability check and purchase, confirming total cost before spending
- Zapmail nameserver switch and the 15-20 minute DNS propagation wait
- Provisioning 2 inboxes per domain and the 4-6 hour ACTIVE wait
- Why warmup takes 2-3 weeks and never fully turns off
- Connecting senders into EmailBison via Zapmail export or credentials import
Install just this skill
Every skill folder is self-contained. Run this from your project root to pull just this one into .claude/skills/domain-inbox-setup/:
npx degit joelwylie7/cold-email-playbooks/.claude/skills/domain-inbox-setup .claude/skills/domain-inbox-setup
Want the whole system, not just one skill?
Related skills
Sender Scaling
The volume discipline for cold email senders: 1 a day until engagement proves the campaign, then 3, with further growth always coming from more senders, never higher limits.
EmailBison Campaign Launch
Assembles a complete EmailBison campaign end to end, copy, leads, senders, schedule, then deliberately stops at draft so nothing can go live without the QA gate.
EmailBison API
The EmailBison API reference built from getting it wrong first: auth failures that look like success, pagination that silently truncates at 15, and one PATCH that can flip live campaign settings.