---
name: write-email-newsletter-from-video-key-insight
description: "Write one useful email from a real video. Give readers a clear lesson and a next step."
category: Content Factory — Process
stage: Process
definitive_article: GAP — to be written
status: needs-work
---

# Write email newsletter from video key insight

A short email can share one point your readers can use. This guide helps you turn a video lesson into a clear note. Start with the source, the reader, and the article you want to share.

**The path:** Source insight → Clear email → Checked destination → Draft or verified send.

**Use this when:** A processed video/article has one useful insight for an existing opted-in audience and the job calls for an email draft or send.

## Inputs
- The [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief, full source and checked article or clearly marked draft.
- The real sender/brand voice, email platform, intended list/segment and existing send scope.
- The current template, sender/reply settings, opt-out footer and suppression rules; keep the platform’s existing required controls.
- The campaign history, canonical destination, test recipient when authorized, and measurement owner.

## First-run prompt

> Draft one useful newsletter from this video and GCT in the real sender’s voice. Check the canonical article, intended audience and existing email controls. Complete tests/sends already authorized, then report exact campaign and delivery states. Keep drafts and scheduled sends distinct; do not invent opens, clicks or revenue.

## Steps
1. Choose the single lesson the source supports. State the reader’s useful takeaway before asking them to click. Do not invent a dramatic cost or customer result for the subject line.
2. Draft a few short specific subjects, then choose one that matches the body. Write an opening in the actual sender’s supported voice; company voice need not pretend the sender lived the video speaker’s experience.
3. Deliver the lesson in three to six short paragraphs or a compact list. Preserve the source’s limits and make the email useful even without a click.
4. Add one primary editorial call to action, usually the full owned article. Required footer/opt-out links still remain. Verify the final public canonical URL before a live send; a private draft is not a reader destination.
5. Place the draft into the approved template when in scope. Check names, reply identity, links, images, mobile layout, readable text and existing footer/suppression behavior. Do not change the list or broaden recipients from a previous send by assumption.
6. Send an authorized test to the named test address and inspect the received copy when that step is in scope. A platform preview is useful but not proof of inbox delivery. Keep test and production campaign IDs distinct.
7. Carry out the send or schedule if already authorized after checks pass; otherwise return the complete draft. Record the exact list/segment, chosen time zone, campaign ID and saved state. A scheduled item needs a named first-firing receiver and delivery-state check.
8. Read the platform’s actual post-send results and record sent/accepted, bounced or pending states accurately. A sent-folder copy proves dispatch, not delivery. Later opens and clicks are platform-reported signals, not proof of human reading or revenue.
9. Log the source, article, campaign and observed metrics/date for the existing [Metrics, Analysis, Action review](https://blitzmetrics.com/maa/). Keep unavailable metrics UNKNOWN and give the next owner the specific follow-up.

## Definition of done (QA checklist)

- [ ] One useful source-backed lesson and honest subject are present.
- [ ] Sender, intended audience, footer and final public destination are checked.
- [ ] Draft, preview, test receipt, scheduled and actual send states are distinct.
- [ ] Metrics and handoff use observed evidence without duplicate-send or business-result claims.

## Example(s)

**Fictional teaching example — no email was sent.** Subject: “Two photos that help before a bike repair visit.”

“A clear photo helps us prepare. Send one view of the whole bike, then one close-up of the issue. Add a short note saying when it happens. We may still need an inspection before a final quote.

See the full photo checklist: `https://maplecycle.example/repair-quote/`.”

The `.example` URL is invented teaching text. A real send needs the actual public article and existing footer. If the test email is received but the campaign is only scheduled, the log says exactly that; it does not report a delivered newsletter.

## Handoff and Content Factory context

The email owner receives the campaign/draft and pending checks. The project’s existing MAA owner later interprets measured results; drafting the email does not create that recurring review.

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

One newsletter per agreed source/topic. Use an existing authorized calendar if present; no automatic recurring send or new audience enrollment is created.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Process
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 3, gating 2 (runs every factory cycle or weekly)
- **Suggested previous station:** `create-social-media-posts-per-platform`
- **Suggested next station:** `create-dollar-a-day-ad-creatives`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Write email newsletter from video key insight](https://local-service-spotlight.github.io/task-library/?task=write-email-newsletter-from-video-key-insight#task-write-email-newsletter-from-video-key-insight)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [SEO Tree: give a page its right topic home](https://blitzmetrics.com/seo-tree/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- Dedicated article is unmapped; actual platform, list permission, test delivery and campaign metrics require real project evidence.