Every Threads mention arrives in Slack with the conversation it came from and a reply already drafted in your account's voice, ready for a person to send or ignore.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
does this work if half the team is on Android, the last one we tried did not
The fourth reply in a thread somebody else started about tools for small design studios, now 61 replies long. She has 4,200 followers, runs a three person studio in Bilbao, and has never mentioned us before. The reply directly above hers says our onboarding was the easiest of the four she tested.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Threads
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Voice notes
How the account sounds and what it bothers replying to, in your own words: paste two or three real replies you were happy with, name the subjects you stay out of, and say who signs off on anything sensitive.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Threads is a reply first platform, and an account that only broadcasts gets treated like an ad. This agent takes each mention, reads the conversation it came out of, checks who wrote it, and drafts the response in the voice you described, so your community manager is approving a reply rather than staring at an empty box. Nothing is ever published by the agent: every reply leaves from a human hand.
What do we need connected?
A Threads account connected through its Meta app, with permission to read your mentions and replies, plus the Slack channel the drafts land in. After that the only thing left to write is the voice notes. Test Run stages a mention against your real instructions, so you can read three drafts before a live one appears anywhere.
How does it know how we sound?
From the voice notes and nowhere else. Paste two or three replies you actually liked, name the subjects you keep out of, and it copies that register rather than inventing a personality of its own. When a draft feels wrong, change the examples rather than the wording, because the examples are what it reads before writing anything.
A post about us went viral. What happens then?
Each mention triggers its own run, so a viral thread costs a run per mention and fills Slack at the moment you are least able to read it. The voice notes are where you bound that: tell it to skip mentions that ask nothing and to stay out of arguments it is only named in, and the volume drops to the handful genuinely addressed to you.
Free to start. Guided setup, a test run against staged conversations, and it's live.