Social posts

Review the thread before it goes out, not after.

Short copy, several opinions, one live file. Agent connect rewrites the reply that sounds like an ad.

livesocial/decaf-launch-thread.md

Decaf launch thread

Owner: Theo Marsh. Brand: Brambleway Coffee. Not scheduled yet.

Five posts and two reply drafts for the decaf tier. Nothing here is scheduled. Nadia posts from her own account, and she will not post a line she would not say in the shop.

Posts

  • Post 1: Tuesday is the roast day for every bag, including decaf. No freshness claim.
  • Post 2: Decaf is a different bean, roasted the same day, not a lesser roast.
  • Post 3: switch before Thursday. Freshest decaf in the country, guaranteed.
  • Post 4: how to switch a subscription before the Thursday ship cutoff, in three taps.
  • Post 5: one photo of the Tuesday roast, no slogan under it, and no freshness line in the alt text.

Reply draft

Taste the freshest decaf in the country. Your cup will thank you.We roast decaf on Tuesday, same as the other bags.

That reply is what we send when someone asks if decaf sits around. It should answer the question and then stop. It should not sound like an ad.

Hold

  • Do not schedule post 3 while it still repeats the freshness claim from the blog. Hana already pulled that claim out of the blog. It should not sneak back in through this thread.
  • Hana pulled that claim once. It does not get a second life in this thread. It does not belong in a reply either. Post 3 has to lose it before anyone schedules the thread.

Freshest decaf in the country

Hana Ito

Post three used to repeat the freshness claim we pulled from the blog. This version should not.

Nadia Sorensen

I will not post that from my account.

Your cup will thank you

Nadia Sorensen

@agent this reply reads like an ad, make it a plain answer.

agent

Rewrote the reply into a plain answer about the Tuesday roast.

resolved
Start with @agent to ask the agent
ResolveReply
Fictional example: a Brambleway Coffee decaf launch thread in Gander, with a claims thread and a scripted agent connect reply.

How social drafts get reviewed today

A chat paste is fast, which is why teams use it. The agent then revises the file, and the approved reply is the one in chat, not the one that will post.

A shared doc adds comments and loses the shape of a thread. Reviewing in the social tool itself is the last step, not the draft, and it is a poor place to ask an agent for a rewrite.

Make it a plain answer

Theo Marsh asks his agent for a five-post launch thread and two reply drafts for Brambleway Coffee's decaf tier. The agent saves social/decaf-launch-thread.md. Theo runs gander watch and sends the link to Nadia Sorensen and Hana Ito.

Hana highlights post three and says the freshness line is the same claim they pulled from the blog. Nadia replies that she will not post it from her account. That thread stays human.

Nadia starts a new comment on a reply draft: "@agent this reply reads like an ad, make it a plain answer." Theo's agent rewrites the reply, posts the new wording in the thread, and resolves it. Hana sees the plain answer on the same link. The thread goes to the scheduler when Nadia says so.

Who's in the doc

WriterFounderClaims ownerThe author's agent

Writer Content or social lead. Sends the link.

Founder Posts from their own account. Final say.

Claims owner Stops a line the team cannot support.

The author's agent Rewrites the reply when someone uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit social posts

Grok BotShort prose from a brief, then agent connect through the Gander MCP server.
Claude CodeWhen the drafts live in a repo, MCP carries agent connect to the session.

Approve the thread on the live draft. Schedule it after that, in the tool you already use.

See how it works on the homepage