Text-message / chat story: structure, script and how to clone it
Text-message / chat story is a proven short-video structure. Here is why it holds attention, how its beats are timed, a script you can start from, and the command that clones it for your own subject.
Why this format works
Chat overlap formats are read, not watched: the viewer scans the messages, which makes them unusually cheap to produce and easy to follow on mute.
Structure breakdown
1. Setup (0–3s)
Who is talking and why it matters, as a single caption.
2. Message 1 (3–10s)
The confident claim, revealed message by message.
3. Complication (10–25s)
The reply that changes the situation.
4. Resolution (25–40s)
The final message lands the point, often as a screenshot of the outcome.
A script you can start from
Segments, takes and selection anchors — this is the part of the project that changes when you re-run the format:
<script>
<segment> id="thread">
<take>He said || @claim it would take a week. || Then || @complication the client moved the date. || Here is || @result what shipped.</take>
</segment>What you need
- — A readable message layout
- — Real or representative messages
- — A payoff screenshot if the story has one
Run it
hypit run clone --reference ./reference/chat-story.mp4 --script ./chat.svsThe reference video stays fixed. Change the script, re-run, and you get a new edit in the same format — that is the whole point of cloning instead of prompting.
Keep reading
FAQ
Should the messages be real?
Representative messages are fine if you label them; real messages need the other person's consent before you publish them.
How many messages?
Three to six, each on screen long enough to read once — that pacing is the whole format.
Does this work without a voice-over?
Yes, and it often performs better that way: music plus readable messages is a complete video.