Skip to content

notque/vexjoy-agent / skills/content/content

content

Unverified

Content operations: editorial calendar, marketing, publishing, social media management.

FileKindSize
SKILL.mdskill md11.5 KB
references/at-protocol-api.mdmarkdown7.6 KB
references/at-protocol-preferred-patterns.mdmarkdown8.5 KB
references/batch-edit-examples.mdmarkdown6.9 KB
references/batch-edit-operation-types.mdmarkdown7.0 KB
references/batch-edit-regex-patterns.mdmarkdown5.4 KB
references/batch-edit-safety-checklist.mdmarkdown6.0 KB
references/batch-edit.mdmarkdown9.9 KB
references/calendar-format.mdmarkdown3.5 KB
references/campaign-planning.mdmarkdown17.5 KB
references/classification-prompt.mdmarkdown5.9 KB
references/content-engine.mdmarkdown8.7 KB
references/content-engine/error-handling.mdmarkdown7.8 KB
references/content-engine/phase-playbook.mdmarkdown8.3 KB
references/content-engine/platform-specs.mdmarkdown10.9 KB
references/content-strategy.mdmarkdown14.5 KB
references/email-sequences.mdmarkdown15.8 KB
references/error-handling.mdmarkdown8.2 KB
references/headlines.mdmarkdown5.9 KB
references/image-audit-alt-text-examples.mdmarkdown6.8 KB
references/image-audit-format-selection.mdmarkdown5.8 KB
references/image-audit-report-templates.mdmarkdown3.8 KB
references/image-audit-size-guidelines.mdmarkdown4.2 KB
references/image-audit.mdmarkdown10.4 KB
references/link-audit-false-positives.mdmarkdown4.1 KB
references/link-audit-fix-strategies.mdmarkdown7.1 KB
references/link-audit-graph-metrics.mdmarkdown5.0 KB
references/link-audit.mdmarkdown7.8 KB
references/llm-marketing-failure-modes.mdmarkdown18.7 KB
references/marketing.mdmarkdown20.4 KB
references/metrics.mdmarkdown7.4 KB
references/news-collection.mdmarkdown5.2 KB
references/operations.mdmarkdown5.8 KB
references/outline-examples.mdmarkdown11.2 KB
references/outline-structure-templates.mdmarkdown6.4 KB
references/outline.mdmarkdown8.9 KB
references/pagespeed-insights.mdmarkdown10.4 KB
references/pipeline-stages.mdmarkdown3.3 KB
references/pre-publish-checklist.mdmarkdown7.4 KB
references/pre-publish-hugo-frontmatter.mdmarkdown5.3 KB
references/pre-publish-seo-guidelines.mdmarkdown4.1 KB
references/pre-publish.mdmarkdown10.8 KB
references/reddit-moderate.mdmarkdown7.9 KB
references/script-commands.mdmarkdown3.7 KB
references/seo-audit.mdmarkdown16.4 KB
references/seo-guidelines.mdmarkdown5.5 KB
references/seo-keyword-placement.mdmarkdown6.0 KB
references/seo-title-patterns.mdmarkdown5.6 KB
references/seo.mdmarkdown8.9 KB
references/series-planner.mdmarkdown11.7 KB
references/series-planner/cadence-guidelines.mdmarkdown6.8 KB
references/series-planner/cross-linking.mdmarkdown7.2 KB
references/series-planner/output-format.mdmarkdown3.8 KB
references/series-planner/series-types.mdmarkdown7.6 KB
references/taxonomy-audit-report-format.mdmarkdown3.2 KB
references/taxonomy-consolidation-rules.mdmarkdown6.7 KB
references/taxonomy-examples.mdmarkdown9.7 KB
references/taxonomy-guidelines.mdmarkdown5.5 KB
references/taxonomy.mdmarkdown9.0 KB
references/topic-brainstormer.mdmarkdown10.1 KB
references/topic-brainstormer/content-filter.mdmarkdown7.1 KB
references/topic-brainstormer/priority-scoring.mdmarkdown8.1 KB
references/topic-brainstormer/topic-sources.mdmarkdown7.6 KB
references/wordpress-upload.mdmarkdown11.2 KB
references/x-api.mdmarkdown7.8 KB
scripts/publish/link_scanner.pyscript21.4 KB
scripts/publish/pagespeed.pyscript15.3 KB
scripts/publish/tests/test_load_env_file.pyscript3.8 KB
scripts/publish/tests/test_wordpress_inline_urls.pyscript4.4 KB
scripts/publish/tests/test_wordpress_media_upload.pyscript1.5 KB
scripts/publish/tests/test_wordpress_scraper.pyscript4.1 KB
scripts/publish/wordpress-edit-post.pyscript21.2 KB
scripts/publish/wordpress-media-upload.pyscript8.7 KB
scripts/publish/wordpress-scraper.pyscript23.4 KB
scripts/publish/wordpress-upload.pyscript44.2 KB
scripts/reddit-moderate/reddit-automod-cron.shscript3.9 KB
scripts/reddit-moderate/reddit-mod.pyscript83.0 KB
scripts/reddit-moderate/tests/test_reddit_mod.pyscript31.3 KB

references/email-sequences.md

View on GitHub
---
title: Email Sequences — Architecture, Subject Lines, Branching Logic, Benchmarks, A/B Testing
domain: marketing
level: 3
skill: marketing
---

# Email Sequences Reference

> **Scope**: Email sequence architecture for lifecycle and campaign use cases. Covers sequence type templates, subject line patterns, branching logic, flow diagramming, engagement benchmarks, and A/B testing frameworks. Serves EMAIL mode.
> **Generated**: 2026-05-05 — benchmark data is directional. Actual performance varies by industry, audience size, and sender reputation.

---

## Sequence Architecture

### Narrative Arc Design

Every sequence tells a story. Before writing any email, define the arc:

| Element | Definition | Example (Onboarding) |
|---------|-----------|---------------------|
| **Opening state** | Where the recipient is now | Just signed up, hasn't used the product |
| **Transformation** | What changes across the sequence | Goes from uncertain to confident and active |
| **Escalation** | How intensity/value builds | Welcome -> quick win -> deeper feature -> social proof -> advanced use |
| **Success signal** | Action that means the sequence worked | Completed 3 key setup steps within 14 days |
| **Exit event** | When to stop sending | Converted, or reached end of sequence |

### Journey Stage Mapping

Map each email to a specific stage:

| Stage | Email Purpose | Tone | CTA Intensity |
|-------|-------------|------|---------------|
| **Welcome** | Set expectations, build trust | Warm, enthusiastic | Soft |
| **Activate** | Drive first value moment | Helpful, encouraging | Medium |
| **Engage** | Deepen usage or understanding | Educational, supportive | Medium |
| **Convert** | Move to desired action | Confident, evidence-backed | Direct |
| **Retain** | Reinforce value, prevent churn | Appreciative, consultative | Soft-Medium |

---

## Sequence Type Templates

### Onboarding (5-7 emails, 14-21 days)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | Welcome | 0 | Set expectations, deliver first-use link | Start using [product] |
| 2 | Quick win | 1-2 | Guide to immediate value | Complete [first action] |
| 3 | Core feature | 4-5 | Deep dive on primary feature | Try [feature] |
| 4 | Advanced feature | 7-8 | Show depth and integration | Explore [advanced capability] |
| 5 | Social proof | 10-12 | Customer story, community invite | Join community / Read story |
| 6 | Check-in | 14-16 | Ask for feedback, offer help | Reply with feedback / Book call |
| 7 | Upgrade prompt | 18-21 | Next steps, paid tier (if freemium) | See plans / Start trial |

### Lead Nurture (4-6 emails, 3-4 weeks)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | Value-first content | 0 | Educational content, no pitch | Read / Download |
| 2 | Pain point identification | 5-7 | Mirror their problem, position the category | Read case study |
| 3 | Solution positioning | 10-12 | Show your approach with proof | See how it works |
| 4 | Social proof | 15-17 | Customer results, testimonials | Read full story |
| 5 | Soft CTA | 19-21 | Offer trial, demo, or resource | Start trial / Book demo |
| 6 | Direct CTA | 24-28 | Clear ask with value recap | Sign up / Buy / Schedule |

### Re-engagement (3-4 emails, 10-14 days)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | "We miss you" | 0 | Compelling reason to return, what's new | Come back and see |
| 2 | Value reminder | 3-5 | Highlight what they're missing | Re-activate |
| 3 | Incentive | 7-9 | Exclusive offer or discount | Claim offer |
| 4 | Last chance | 12-14 | Clear deadline, final ask | Use before [date] |

### Win-back (3-5 emails, 30 days)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | Friendly check-in | 0 | Ask what went wrong, show you care | Reply / Take survey |
| 2 | What's new | 7-10 | Product improvements since they left | See what changed |
| 3 | Incentive | 14-18 | Special offer to return | Claim offer |
| 4 | Feedback request | 21-25 | Even if not coming back, learn why | Take 2-min survey |
| 5 | Final goodbye | 28-30 | Door open, list cleanup notice | Stay subscribed / Goodbye |

### Product Launch (4-6 emails, 2-3 weeks)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | Teaser | -7 to -3 | Build anticipation | Get notified |
| 2 | Launch announcement | 0 | Full details, primary offer | Try now / Buy |
| 3 | Feature spotlight | 3-5 | Deep dive on key feature or use case | See in action |
| 4 | Social proof | 7-10 | Early adopter results or reviews | Read story |
| 5 | Limited offer | 12-14 | Time-limited bonus or pricing | Claim before [date] |
| 6 | Last chance | 17-21 | Final reminder, urgency | Last chance |

### Educational Drip (5-8 emails, 4-6 weeks)

| # | Email | Day | Purpose | CTA |
|---|-------|-----|---------|-----|
| 1 | Welcome + overview | 0 | What they'll learn, set cadence | Read intro |
| 2 | Lesson 1 | 3-5 | Foundational concept | Practice / Apply |
| 3 | Lesson 2 | 8-12 | Build on foundation | Practice / Apply |
| 4 | Lesson 3 | 15-19 | Advanced concept | Practice / Apply |
| 5 | Application | 22-26 | Practical exercise or challenge | Complete exercise |
| 6 | Resources | 29-33 | Tools, templates, further reading | Explore resources |
| 7 | Graduation | 36-42 | Recap, certificate, next steps | Next course / Product |

---

## Subject Line Patterns

### Approach Taxonomy

| Approach | Formula | Example | Best For |
|----------|---------|---------|----------|
| **Curiosity** | Incomplete loop, question, unexpected | "The one thing we got wrong about onboarding" | Cold audience, awareness |
| **Benefit** | Clear value statement | "Cut your reporting time in half" | Warm audience, conversion |
| **Urgency** | Time-bound, scarcity | "48 hours left: your exclusive access" | Re-engagement, offers |
| **Personal** | Name, behavior, history | "[Name], your setup is 80% done" | Onboarding, nurture |
| **Question** | Direct question to reader | "What would you do with 5 extra hours a week?" | Engagement, consideration |
| **Number** | Specific quantified claim | "3 emails that doubled our demo rate" | Education, consideration |
| **Story** | Narrative hook | "How a 2-person team outranked enterprise competitors" | Nurture, thought leadership |

### Subject Line Rules

- Under 50 characters (35-40 optimal for mobile)
- No ALL CAPS words
- No excessive punctuation (!!!, ???)
- Replace spam-trigger words (free, act now, limited time, congratulations, click here) with specific value statements
- Preview text complements -- never repeats -- the subject line
- Always provide 2-3 options per email for A/B testing

### Preview Text Patterns

| Subject Line | Bad Preview | Good Preview |
|-------------|------------|-------------|
| "Your setup is almost done" | "Your setup is almost done. Complete..." | "One more step and you'll see why teams love this" |
| "3 ways to improve your pipeline" | "3 ways to improve your pipeline..." | "We tested each one. #2 surprised us." |
| "Big news from [Company]" | "[Company] is excited to announce..." | "It's the feature you've been asking about since Q1" |

---

## Branching Logic

### Core Branching Patterns

#### Open-Based Branching

```
Email 1 (Day 0)
    |
    ├── Opened? ──Yes──> Email 2 (Day 3)
    |                        |
    |                   Clicked CTA? ──Yes──> [EXIT: Converted]
    |                        |
    |                       No
    |                        v
    |                   Email 3 (Day 7)
    |
    └── Not opened ──> Email 1b (Day 2)
                           [Resend with new subject line]
                           |
                      Opened? ──Yes──> Email 2 (Day 5)
                           |
                          No
                           v
                      Email 2 (Day 7)
                      [Reduced expectations path]
```

#### Engagement-Based Branching

```
Email 2 (Day 3)
    |
    ├── Clicked CTA ──> [Skip to Email 4 - advanced path]
    |
    ├── Opened, no click ──> Email 2b (Day 5)
    |                        [Softer re-ask, different angle]
    |
    └── Not opened ──> Email 3 (Day 7)
                       [Continue standard path]
```

#### Behavior-Based Branching

```
Email 3 (Day 7)
    |
    ├── User completed setup ──> [EXIT: Move to activation sequence]
    |
    ├── User partially completed ──> Email 3b (Day 9)
    |                                [Help with remaining steps]
    |
    └── User inactive ──> Email 4 (Day 10)
                          [Re-engagement angle]
```

### Exit Conditions

Define clearly for every sequence:

| Condition | Action | Example |
|-----------|--------|---------|
| **Conversion** | Remove from sequence, move to next stage | Signed up, purchased, booked demo |
| **Sequence complete** | Remove, add to regular newsletter | All emails sent |
| **Unsubscribe** | Remove immediately, honor preference | Clicked unsubscribe |
| **Hard bounce** | Remove, flag for list cleaning | Invalid email |
| **Support contact** | Pause for 48-72 hours | Opened support ticket |
| **Entered competing sequence** | Suppress the lower-priority sequence | Triggered both nurture and onboarding |

### Suppression Rules

Standard suppressions to implement:
- Already in another active sequence (priority rules determine which wins)
- Unsubscribed from marketing communications
- Contacted support within last 48 hours
- Purchased within last 7 days (unless post-purchase sequence)
- Marked as spam or complained
- Inactive for 180+ days (move to re-engagement first)

### Re-entry Rules

| Sequence Type | Re-entry Allowed? | Conditions |
|--------------|-------------------|-----------|
| Onboarding | No | One-time sequence |
| Lead nurture | Yes, after 90 days | Must have re-engaged with content |
| Re-engagement | Yes, after 120 days | Must have been active, then lapsed again |
| Win-back | Yes, after 180 days | Only if they returned and churned again |
| Product launch | No | Event-specific |
| Educational | No | Content is the same |

---

## Performance Benchmarks

### By Sequence Type

| Metric | Onboarding | Lead Nurture | Re-engagement | Win-back | Product Launch | Educational |
|--------|-----------|--------------|---------------|----------|---------------|-------------|
| Open rate | 50-70% | 20-30% | 15-25% | 15-20% | 25-40% | 30-50% |
| CTR | 10-20% | 3-7% | 2-5% | 2-4% | 5-10% | 5-15% |
| Conversion | 15-30% | 2-5% | 3-8% | 1-3% | 5-15% | N/A |
| Unsubscribe | <0.5% | <0.5% | 1-2% | 1-3% | <0.5% | <0.5% |

### By Position in Sequence

| Email Position | Relative Open Rate | Relative CTR | Notes |
|---------------|-------------------|-------------|-------|
| Email 1 | Highest (baseline) | Highest | Novelty and recency |
| Email 2 | -10-15% | -15-20% | Normal decay |
| Email 3 | -15-25% | -20-30% | Decision point for many |
| Email 4+ | -25-40% | -30-40% | Engaged core remains |

If open rates drop more than 50% by email 3, the sequence has a content or targeting problem, not a length problem.

### Metric Interpretation Guide

| Metric Pattern | Diagnosis | Action |
|---------------|-----------|--------|
| High opens, low clicks | Subject lines work, content/CTA fails | Improve email body, test CTA placement/copy |
| Low opens, good clicks | Content is good, subject lines fail | Test subject lines, check deliverability |
| High unsubscribes early | Audience mismatch or frequency too high | Review targeting, extend delays between emails |
| High unsubscribes late | Content fatigue or wrong sequence length | Shorten sequence, add branching |
| Declining engagement across sequence | Normal if gradual; problem if steep | Check content escalation, add behavioral branching |

---

## A/B Testing Framework

### What to Test (Priority Order)

| Test | Expected Impact | Sample Size Needed | Duration |
|------|----------------|-------------------|----------|
| Subject line | High (directly affects opens) | 1,000+ per variant | 24-48 hours |
| Send time | Medium (affects opens and clicks) | 2,000+ per variant | 1 week |
| CTA text | Medium (affects clicks) | 1,000+ per variant | 1 week |
| Email length | Medium (affects clicks and conversion) | 1,000+ per variant | 1 week |
| Personalization | Medium (affects opens and engagement) | 1,000+ per variant | 1 week |
| Design/layout | Low-Medium (affects clicks) | 2,000+ per variant | 1-2 weeks |

### Testing Rules

1. Test one variable at a time. Multi-variable tests require significantly larger samples.
2. Define the success metric before launch. Opens for subject lines, clicks for CTA, conversion for offers.
3. Calculate required sample size before starting. Do not end tests early based on gut feeling.
4. Run for at least one full business cycle (one week for B2B, shorter for high-volume B2C).
5. Statistical significance threshold: 95% confidence minimum.
6. Document every test result. Failed tests are data.
7. Roll out winners to remaining audience. Apply learnings to future sequences.

### A/B Test Documentation Template

| Field | Value |
|-------|-------|
| **Test name** | [Descriptive name] |
| **Hypothesis** | "If we [change], then [metric] will [improve/increase] because [reasoning]" |
| **Variable** | What's different between A and B |
| **Success metric** | Primary metric to determine winner |
| **Sample size** | Per variant |
| **Duration** | Start and end date |
| **Result** | Winner, lift %, confidence level |
| **Learning** | What this tells us for future sequences |

---

## Email Copy Patterns

### Hook Patterns for Email Body

| Type | Structure | Example |
|------|-----------|---------|
| **Problem mirror** | Name their pain, show you understand | "You've set up your account, but the dashboard still feels empty. We've all been there." |
| **Quick win** | Immediate actionable value | "Here's one thing you can do in the next 5 minutes that will [outcome]." |
| **Story** | Customer narrative | "Last month, [Customer] was in the same position you are. Here's what they did next." |
| **Data** | Surprising number | "Teams that complete setup in the first week are 3x more likely to renew." |
| **Question** | Engage curiosity | "What if your reporting took 10 minutes instead of 2 hours?" |

### Body Structure Rules

- 2-3 sentences per paragraph maximum
- Bold key phrases for scanners (most email is scanned, not read)
- One idea per paragraph
- Personalization tokens where relevant: {first_name}, {company}, {product_used}
- Mobile-first: test on phone before sending
- Link CTA button, not just text (buttons get 28% more clicks than text links)

### Tone by Sequence Position

| Position | Tone | Reasoning |
|----------|------|-----------|
| Email 1 | Warm, welcoming, low-pressure | Building trust, setting expectations |
| Email 2-3 | Helpful, educational, encouraging | Proving value, building habit |
| Mid-sequence | Confident, evidence-backed | Credibility established, time to show proof |
| Penultimate | Direct, value-focused | Clear about what's at stake |
| Final | Honest, respectful, door-open | Last chance without desperation |

---

## Sequence Overview Table Template

| # | Subject Line (Primary) | Purpose | Day | Primary CTA | Condition |
|---|----------------------|---------|-----|-------------|-----------|
| 1 | | | 0 | | All subscribers |
| 2 | | | 3 | | Opened #1 |
| 2b | | | 2 | | Did not open #1 |
| 3 | | | 7 | | Did not convert |
| 4 | | | 10 | | Did not convert |

## Setup Checklist (Platform-Agnostic)

1. Create automation/flow in your email platform
2. Set enrollment trigger (form submit, tag applied, event fired)
3. Add each email with specified delays
4. Configure branching conditions and exits
5. Set up conversion tracking (goal event or tag)
6. Suppress recipients in competing sequences
7. Enable send-time optimization if available
8. Test with internal addresses before activating
9. Monitor first 48 hours closely for deliverability issues
10. Review performance weekly for first month, then monthly
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall