A post built for replies, not likes
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
Der Prompt
Write a Threads post on the topic "{topic}" designed to pull replies. What I know about it: {your experience, facts, numbers} Audience: {who} What I want to hear in the replies: {e.g. how other people solve this} Rules: — No longer than 500 characters, that is the platform limit. 300 is better. — The first 90 characters must work as a standalone hook; the rest is what people unfold themselves. — End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice. — Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say. Don't do this: — "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to. — Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow. Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Alles in geschweiften Klammern ersetzen Sie durch Ihre Angaben.
Beispielergebnis
Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.
Ähnliche Prompts
The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.
Write 20 opening lines for Threads posts on the topic "{topic}". Audience: {who} My role: {who you are to them — practitioner, seller, observer} Hard limits: — No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land. — No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past. — No caps lock, no emoji chains. Give 4 groups of 5: 1. Personal experience with a specific number or timeframe. 2. Disagreement with received wisdom in the niche. 3. An observation the reader recognises in themselves. 4. An open question they have something to answer from their own experience. After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Beispielergebnis zeigenBeispiel ausblenden
Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
Draw up a plan for the first 30 minutes after publishing a Threads post. Post text: {paste the post} Topic: {what it's about} Who I am in this niche: {role} Fo
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischaltenA link in the body sends people off-platform, and the feed accounts for that. The scheme: the post stands alone, the link comes as the first reply.
Split my link into a Threads post and a first reply. Where I'm sending people: {URL and what's there} Who needs it: {audience} What they get by clicking: {spec
Dieser Prompt gehört zur PRO-Auswahl
Zugang freischaltenA post worth arguing with on the merits. Checked separately so it doesn't turn into cheap provocation.
Help me put a strong opinion into a Threads post. Topic: {what about} What I actually think: {your position, a rough draft is fine} What it's based on: {experience, numbers, cases} I want a post some readers will disagree with — and want to explain why. But not at the cost of my reputation. Do this: 1. State my position in one sentence under 90 characters, so it is clear exactly what there is to argue with. 2. Assemble a post under 500 characters: the position, one piece of grounding from my own experience, and an admission of where I am wrong. That last part is mandatory — an opinion with no stated limits reads as posturing. 3. Write the three strongest objections that will come, and an honest answer to each. 4. Check the resulting post against this list and give a verdict on every point: — Would I repeat this under my own name a year from now? — Is this an argument about the work, or a swipe at people? — Do I have grounds beyond irritation? — If someone else had written this, would I reply on the merits or scroll past? If even one point fails, say so plainly and suggest how to reframe it.
Beispielergebnis zeigenBeispiel ausblenden
Position (84 characters): "AI courses sell a skill that goes stale faster than the course takes to finish." Check: — Repeat in a year: yes, the field is only speeding up. — About the work: yes, this is about the product, not the people. — Grounds: two courses taken, both outdated by the end. — Would reply myself: yes, there's a case to make about fundamentals.