Back Office · office.temerarii.xyz
One published post, granular — the Social for W37 Thu, its copy, its output-policy format, and the video master it derives from. Part of the day's full output set.
postW37-Thu-social-5kindSocialweekW37dayThudate2026-09-17campaignlongform-youtubecadence5/day floor × 9 channels

Copy the published post text

Minus the Hype
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-minus-the-hype-W37-Thu
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)

ChannelNative caption
TiktokThey promise AI closes your support tickets with no human. What works: AI answers the common questions from your docs and sends anything odd or upset straight to a person. The honest cost is building the handoff that knows its limits. That router is the whole job. (AI-assisted)
Instagram"AI handles all your support tickets." Not quite. What works: AI answers the common ones from your docs It routes anything odd or upset to a person The cost: building the handoff that knows its own limits. That router is the real work. #customersupport #aitools #buildinpublic #cx #automation
LinkedinThe hype says AI closes your support tickets with no human involved. Here is the honest version. What actually works: AI answers the common questions straight from your docs, and it sends anything odd or upset to a person instantly. The cost nobody prices in: building the handoff that knows its own limits. A router that guesses on the hard tickets is worse than no router at all. The value was never the answers. It was the routing. Build that part well and the rest follows.
X"AI handles your support tickets, no human." What works: AI answers the common ones from your docs, routes anything odd or upset to a person. The cost: building the handoff that knows its limits. The router is the job.
FacebookThe hype says AI closes your support tickets with no human. Here is the honest version. What works: AI answers the common questions from your docs, and it sends anything odd or upset straight to a person. The real cost is building the handoff that knows its own limits. The router is the whole job. Build that part well first.
Threads"AI handles all your support tickets." Not quite. What works: AI answers the common ones from your docs, and routes anything odd or upset straight to a person. The honest cost: building the handoff that knows its own limits. The router is the real work, not the answers.
PinterestMinus the hype: AI does not close every support ticket alone. The honest method is to let AI answer the common questions from your docs and route anything odd or upset straight to a human. The real cost is building a smart handoff that knows its own limits. Customer support automation tips for operators.
Bluesky"AI handles your tickets, no human." Not quite. What works: AI answers the common ones from docs, routes odd or upset ones to a person. Cost: a handoff that knows its limits.
YoutubeTitle: Minus the Hype: AI Will Not Close Every Support Ticket Alone The pitch says AI handles your support tickets with no human in the loop. Here is the honest version. AI answers the common questions from your docs and routes anything odd or upset straight to a person. The real cost is building the handoff that knows its own limits, because a router that guesses on hard tickets is worse than none. The value was never the answers. It was the routing. From The Big T-M at temerarii.xyz.

Composition layer × scene 5 scenes · this post's OWN storyboard (distinct per asset)

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d
hook0–5.0skinetic-buildicon·wireframe♪ node_lock
AI closes every support ticket on its own, with no human in the loop, they promise.
on-screen: "AI handles support tickets"
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment wireframemotion kinetic-buildpower laser-lockinstrument laser-trace→"AI handles support tickets"
2s2
matches intent
TerminalRun
template
diff5.0–12.7scrossfade-8ficon·wireframe♪ node_lock
What works: AI answers the common ones from your docs. It sends anything odd or upset straight to a person.
on-screen: Answer easy, route hard
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual codeshape boxground whitetreatment wireframemotion crossfade-8fpower morphinstrument morph→Answer easy, route hardcurate codeLines
3s3
first render · fix pending
NumberedList
templatedead_air
teach12.7–17.7skinetic-buildicon·wireframe♪ node_lock
The cost is building the handoff that knows its limits, so it asks for a person on the hard ones.
on-screen: The cost: a smart router
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→The cost: a smart routercurate items, nodes
4s4
first render · fix pending
RankList
templatedead_airgeneric_scene
proof17.7–22.7sreceipts-counticon·wireframe♪ node_lock
Minus the Hype
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment wireframemotion receipts-countpower receiptsinstrument spotlight→Minus the Hypecurate rows, statsLabels
5s5
first render · fix pending
shared field
signature-3ddead_airgeneric_scene
resolve22.7–27.7scoalescenceicon·color♪ bed_out
Minus the Hype
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·color logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Minus the Hype

Cross-links this post in the day's output set