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-W45-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 | Reader asks: my unsubscribes jumped, did I do something wrong? Usually it's how often you send, not what you say. Move readers who haven't opened in sixty days to a slower schedule this week and watch the rate settle. (AI-assisted) |
| Ask the operator: "Unsubscribes spiking." My unsubscribes jumped. Did I mess up? Usually it's cadence, not content. Move cold readers (60+ days no open) to a slower send. Watch the rate settle. #emailmarketing #newsletter #deliverability #marketing #askanything | |
| Reader question: my unsubscribes jumped, did I do something wrong? Usually it's cadence, not content. A spike in send volume is the first thing to check before you rewrite anything. The move: take readers who haven't opened in sixty days and put them on a lighter send this week. You stop annoying the disengaged, your unsubscribe rate settles, and your engaged readers still hear from you on the normal schedule. | |
| X | Reader: my unsubscribes jumped, what went wrong? Usually it's cadence, not content. Move readers who haven't opened in 60 days to a lighter send this week and watch the rate settle. temerarii.xyz |
| A reader wrote in: my unsubscribes jumped, did I do something wrong? Usually it's how often you send, not what you say. The fix: take readers who haven't opened in sixty days and move them to a lighter schedule this week. You stop bothering the disengaged and your unsubscribe rate settles. More answers at temerarii.xyz | |
| Threads | Ask the operator. "My unsubscribes jumped. Did I do something wrong?" Usually it's cadence, not content. A jump in how often you send is the first thing to check. Move readers who haven't opened in 60 days to a lighter send this week. |
| Why your email unsubscribes spiked, and how to fix it: usually it's send cadence, not content. Move readers who haven't opened in sixty days to a lighter schedule to settle your unsubscribe rate. Email marketing tips, newsletter cadence, list re-engagement. | |
| Bluesky | Reader: my unsubscribes jumped, what went wrong? Usually it's cadence, not content. Move readers who haven't opened in 60 days to a lighter send this week and watch the rate settle. |
| Youtube | Title: Why Your Email Unsubscribes Spiked (Fix the Cadence) Reader question: my unsubscribes jumped, did I do something wrong? Usually it's cadence, not content. A jump in send volume is the first thing to check. The move: take readers who haven't opened in sixty days and put them on a lighter send this week. You stop annoying the disengaged and your unsubscribe rate settles. |
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.0s | kinetic-build | icon·wireframe | ♪ node_lock | Email question: my unsubscribes went up. Did I do something wrong? on-screen: "Unsubscribes spiking" |
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape octaground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"Unsubscribes spiking" | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·wireframe | ♪ node_lock | Most times it is how often you send, not what you say. A jump in sends is the first thing to check. on-screen: Cadence beats content |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Lumen leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape octaground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→Cadence beats contentcurate items, nodes | |||||||
| 3 |  matches intent ComparisonTable template | proof | 10.0–15.0s | receipts-count | icon·wireframe | ♪ node_lock | Take folks who have not opened in sixty days. Put them on a slower send this week. on-screen: Slow the cold ones |
expected on screen: white ground · a ComparisonTable panel over a dimmed Signal Field · Lumen leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id ComparisonTablevisual receiptsshape octaground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Slow the cold onescurate colA, colB, rows, statsLabels | |||||||
| 4 |  first render · fix pending SchematicCard templatedead_airgeneric_scene | step | 15.0–20.0s | kinetic-build | icon·wireframe | ♪ node_lock | Ask the Operator |
expected on screen: white ground · a SchematicCard panel over a dimmed Signal Field · Lumen leads · pipeline · kinetic-build · icon·wireframe logo · caption bottom-left spec (the prompt): comp_id SchematicCardvisual pipelineshape octaground whitetreatment wireframemotion kinetic-buildpower throwinstrument laser-trace→Ask the Operatorcurate nodes, stages, steps | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 20.0–25.0s | coalescence | icon·ember-fill | ♪ bed_out | Ask the Operator |
expected on screen: white ground · octa hero in the shared Signal Field · Lumen leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape octaground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Ask the Operator | |||||||