Copy the published post text
Ask the Operator
copy ready · render pending
Output-policy spec format · dimensions (asset_specs.output_policy)
formatnative cut · 9:16 · 1:1 · 16:9
dims1080×1920 · 1080×1080 · 1920×1080
cadence5/day floor × 9 channels
Channels 9 destinations
TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube
This post a distinct social asset — its own angle, storyboard, and cuts
thread-ask-the-operator-W29-Tue
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel
Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)
| Channel | Native caption |
|---|---|
| Tiktok | Inbox question: my newsletter sends but nobody opens. Where do I start? Before any fancy design, fix three things: a subject that earns the tap, a sender name people trust, and clean inbox placement. Then split-test one subject and let the data pick the winner. (AI-assisted) |
| Ask the operator. "Why no email opens?" Before fancy design, fix three things: a subject that earns the tap a sender name people trust spam placement Then split-test one subject line. #emailmarketing #newsletter #openrate #asktheoperator #aitools | |
| Reader question: my newsletter sends but nobody opens it. Where do I even start? Before any fancy design, fix three things: a subject line that earns the tap, a sender name people trust, and your spam placement. Those decide whether anyone ever sees the design you worked on. The practical move: split-test one subject line on your next send and let the data pick the winner. | |
| X | "My newsletter sends but nobody opens. Where do I start?" Before fancy design, fix three: a subject that earns the tap, a sender name people trust, spam placement. Then split-test one subject and let data pick. |
| An operator question this week: my newsletter sends but nobody opens it, where do I even start? Before any fancy design, fix three things: a subject line that earns the tap, a sender name people trust, and your spam placement. Then split-test one subject line on your next send and let the data pick the winner. | |
| Threads | Ask the operator. "My newsletter sends but nobody opens. Where do I even start?" Before fancy design, fix three things: a subject that earns the tap, a sender name people trust, and spam placement. Then split-test one subject line and let the data pick the winner. |
| Ask the operator: why does nobody open your newsletter? Before redesigning anything, fix the three things that decide opens: a subject line that earns the tap, a sender name people trust, and your spam placement. Then split-test one subject line on your next send and let the data pick the winner. | |
| Bluesky | "My newsletter sends but nobody opens. Where do I start?" Before fancy design, fix three: a subject that earns the tap, a sender name people trust, spam placement. Then split-test one subject and let data pick. |
| Youtube | Title: Why Nobody Opens Your Newsletter (Fix These 3 Things First) An operator question: my newsletter sends but nobody opens it, so where do I even start? Before any fancy design, fix the three things that decide opens: a subject line that earns the tap, a sender name people trust, and your spam placement. Then split-test one subject line on your next send and let the data pick the winner. |
Composition layer × scene 5 scenes · this post's OWN storyboard (distinct per asset)
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | matches intent shared field signature-3d | hook | 0–5.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Inbox question: my newsletter sends but nobody opens. Where do I even start? on-screen: "Why no email opens?" |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→"Why no email opens?" | |||||||
| 2 |  matches intent NumberedList template | teach | 5.4–12.8s | kinetic-build | icon·white-knockout | ♪ node_lock | Before fancy design, we fix three things: a subject that earns the tap, a sender name people trust, and on-screen: Subject, sender, spam |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Subject, sender, spamcurate items, nodes | |||||||
| 3 |  matches intent ComparisonTable template | proof | 12.8–17.8s | receipts-count | icon·liquid-chrome | ♪ node_lock | Split-test one subject line this send and let the data pick the winner. on-screen: Test one subject |
expected on screen: red ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→Test one subjectcurate colA, colB, rows, statsLabels | |||||||
| 4 |  first render · fix pending FlowSchematic templatedead_airgeneric_scene | step | 17.8–22.8s | kinetic-build | icon·white-knockout | ♪ node_lock | Ask the Operator |
expected on screen: red ground · a FlowSchematic panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id FlowSchematicvisual pipelineshape octaground redtreatment white-knockoutmotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 22.8–27.8s | coalescence | icon·white-knockout | ♪ bed_out | Ask the Operator |
expected on screen: red ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator | |||||||