Threads hooks that get replies
Every post is judged on one line, in about a second, by somebody who was scrolling past. That line has one job, and it is not being clever.
The short version
- The first line is the post until somebody taps to see the rest.
- Write for replies, not likes. Replies are what the algorithm weights and what pulls a post into other people's feeds.
- A claim beats a question. Disagreeing is easier than answering.
- Specific beats clever. A number, a price, a date, a name: anything that could not have been written by anyone else.
- Write twenty at a time, separately from the posts they will open.
What is a hook on Threads?
The first line of the post, the only part that appears before the reader decides. Threads truncates longer posts and shows the opening line in a feed of other opening lines, so the hook is not an introduction to the post. For most people who see it, it is the entire post.
This is the part that makes text platforms different from video ones. On a reel the first frame competes with motion, colour and a soundtrack. On Threads your line competes with forty other lines of the same size in the same typeface, and the only variable you control is what it says.
You are not writing an opening. You are writing the whole post, and then some extra for the people who tap.
Why replies and not likes?
Because a like is a dead end and a reply is distribution. Threads weights replies far above likes when deciding how far to push a post, and each reply is a real person's network briefly attached to yours. A hook that earns fifty likes and no replies has produced almost nothing.
The mechanics are in how the Threads algorithm works. The writing consequence is narrow and useful: when you test a hook, ask whether a reader could reply to it with something other than agreement. If the only available response is a nod, the line will collect nods.
Leave a gap on purpose. A post that answers itself completely gets agreement. A post that states a position and leaves out the reasoning gets asked for the reasoning, and you get to answer in the thread, which restarts the post.
Which hook shapes actually work?
Seven, and all of them are ways of creating a gap rather than tricks. A claim somebody might argue with, a number, a mistake the reader may be making, a reversal, a confession, a specific moment, and a comparison. What they share is that none of them can be written without knowing something.
| Shape | Example opening | Why it earns replies |
|---|---|---|
| The claim | "Free trials are worse than a money-back guarantee." | People with the other view have to say so |
| The number | "Four months at $9. Then I doubled it." | Concrete, and invites the obvious question |
| The mistake | "Your bio is doing one job. It should be doing three." | Self-diagnosis, then a request for the rest |
| The reversal | "Posting more made it worse." | Contradicts the received advice |
| The confession | "I spent six weeks building the wrong feature." | People reply with theirs |
| The moment | "A customer emailed me at 2am to cancel. Here's what it said." | A story with a withheld ending |
| The comparison | "Gumroad took $340 last month. Stripe took $61." | Numbers side by side always get argued with |
Notice that six of the seven require you to have done something. That is not incidental: it is the reason hook lists mostly do not work. The shapes are transferable; the material is not, and the material is what makes the line worth reading.
Why do questions underperform?
Because a question asked cold puts the work on the reader and offers nothing first. "What's your biggest struggle with pricing?" is a survey, and people scroll past surveys. The version that works states your answer and lets people disagree. The reply rate on a position is several times the reply rate on a question.
There is one exception worth knowing: a question that follows a claim, in the same post, works well. Take a position, give the reasoning, then ask what everyone else does. By then the reader has something to react to, and answering is a continuation rather than a request for free labour.
- Cold question: "How do you price your products?" A survey.
- Claim then question: "$9 was the worst price I ever charged. It signalled the product was thin, and refunds went up, not down. Anyone found a floor that works?" A conversation.
How do you write twenty in a sitting?
By mining rather than inventing. Hooks come out of things that already exist: your own week, the questions you keep being asked, the advice you disagree with, and the numbers in your own dashboards. Sitting down to think of a good line produces nothing; sitting down with your last month produces a list.
- Your own week. Five things that happened, however small. Each one is a moment hook.
- Questions you were asked. Every DM you answered twice is a post: the answer is the body, the question reversed is the hook.
- Advice you think is wrong. The most reliable source of claim hooks, and the most replied-to genre on the platform.
- Your numbers. Anything you can state precisely. Precision is the rarest thing in a feed of generalities.
- Your mistakes. Uncomfortable, and consistently the best-performing category for a small account.
Twenty lines out of those five buckets is one sitting, and it is the raw material for a fortnight. This is the same argument as the post bank, applied one level down: the bank holds the posts, the hook list holds their opening lines, and neither should be produced at the moment you want to publish.
How do you tell whether a hook worked?
Replies in the first hour, and nothing else. Not likes, which follow reach and tell you about distribution rather than about the line. Not views, which mostly tell you when you posted. The hook's only measurable job is turning a scroll into a response, and that number is visible within the hour.
- Test one variable. Same idea, different opening line, a week apart. Two changes teach you nothing about either.
- Judge across five posts. Single-post variance on Threads is enormous.
- Keep the winners in a file. A hook shape that beat the others twice is a template, not a one-off.
- Reply to every reply. The hook opens the conversation; the replies are what keep the post alive: the reply strategy is the other half of this.
Never write a hook the post cannot pay off. A line that wins the tap and loses the reader teaches people that your openings are inflated, and that is a reputation that outlasts any individual post.
Frequently asked questions
What makes a good hook on Threads?
Specificity and a gap. The line has to be about something concrete, and it has to leave the reader with a question they want closed. \"Most people get this wrong\" has a gap and no specifics; \"I priced it at $9 for four months\" has both.
Should a hook be a question?
Usually not the first line. Questions asked cold read as engagement bait and most people scroll past them. A claim that somebody might disagree with earns far more replies than a question, because disagreeing is easier than answering.
How long should the first line be?
Short enough to read without deciding to. Roughly six to twelve words. The rest of the post can be long; the first line is what is being judged.
Do hooks work the same on Threads as on Instagram?
The shapes transfer, the medium does not. On Instagram the hook is text on a video frame competing with the footage. On Threads it is a line of text competing with other lines of text, so precision matters more and spectacle matters less.
How many hooks should I write at once?
Twenty, away from any particular post. Writing one hook per post, at the end, while tired, is why most accounts have a hook problem. It is a separate task from writing the post and should be a separate sitting.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.