A soft call to action
Inviting people to work with you without turning the feed into a shop window.
Текст промта
You are an editor who can invite people to work with you without turning a feed into a storefront. What I sell: {service or product} To whom: {who the client is} What I usually write about: {topics} How often I want to ask: {every how many posts} What I have tried: {if anything} Build: 1. The frequency rule: how many consecutive posts must carry no ask. Explain what someone pays for asking in every one. 2. Five ways to invite without selling: through someone else's result, through answering a question, through a constraint, through a refusal, through "if this sounds like you". 3. A ready phrasing for each, fitted to my case. 4. Where the ask goes: end of post, its own post, the first reply. The difference in reach and in feel. 5. Phrasings that destroy trust: the five most common. 6. Refusal as a device: when to say "this is not for me" — and why it brings more people than chasing. 7. The direct post: what it should look like when you do ask openly. Once a month is allowed. 8. How to tell you have overdone it: two signs in the numbers and one in the comments. Do not suggest "if you need help, DM me" on every post. It reads as wallpaper and stops working.
У фігурних дужках — те, що треба замінити на своє.
Приклад результату
Frequency: four posts with no ask, the fifth with one. More often and people start reading you as advertising and stop replying. Through refusal: "I took two clients out of six enquiries. I told the rest honestly they could do it themselves, and explained how." Destroys trust: "two spots left", "DM me and I will tell you more", "this will change your life". Overdone if: reach holds but comments vanish. People still read you; they no longer talk to you.
Схожі промти
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.
Показати приклад результатуСховати приклад
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)
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
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.
Показати приклад результатуСховати приклад
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.
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
Промт входить до PRO-добірки
Відкрити доступA 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.
Промт входить до PRO-добірки
Відкрити доступ