An open-day announcement on LinkedIn
The agent writes a question hook, a story hook and a statistic hook. The admissions officer picks the story, the agent polishes it, and the post is approved for publishing.
Polish approval
The ConvOps Social Post template makes your AI turn a brief into a ready-to-publish post: capture platform, audience, core message, proof and call to action, write three variants with different hook angles, then polish the one you pick. It stops once, before publishing. Reject it and the AI drafts new variants.
4 steps · 1 approval · 1 loop back
example · the steps are this template's real steps
For founders and marketers posting on LinkedIn, X or other platforms who want options, not one take.
Social Post is stored in ConvOps as four steps, and your AI client receives them one at a time. A Social Post run holds at Polish until an explicit approval is given.
The 4 Social Post steps in order, each with the instruction your AI receives there as Social Post stores it.
One approved post for one platform, chosen from three variants with different hooks and polished before approval.
Establish the brief for this post. Do not draft yet.
Capture, in plain prose:
If the core message is fuzzy, ask the operator before advancing: a vague message produces a forgettable post.
Save the full brief as a task note with task_notes_add. The next step (Draft Variants) reads this note.
Read the task notes with task_notes_list: the note from the Brief step contains platform, audience, message, proof, and CTA. Work from it.
Write three distinct variants of the post. What good looks like:
Label them Variant A, B, C so the operator can pick.
Save all three variants as a task note with task_notes_add. The Polish step reads this note and the operator's choice.
Read the task notes with task_notes_list: the note from the Draft Variants step contains Variant A, B, and C. Work from it.
Ask the operator which variant to run with. Polish the chosen one: tighten the hook, fix any awkward phrasing, confirm the link and CTA, check it reads well on the target platform.
Save the final polished post as a task note with task_notes_add. Then ask the operator to approve it for publishing. This is a checkpoint: publishing is the irreversible moment, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft Variants.
rejected → back to Draft Variants
The post is approved and ready to publish. Confirm the final post is saved as a task note, then close out the task.
The agent writes a question hook, a story hook and a statistic hook. The admissions officer picks the story, the agent polishes it, and the post is approved for publishing.
Polish approval
Social Post holds at Polish until an explicit approval is given, recorded with the account that gave it.
You choose the variant, the AI polishes it, and you approve before it is published. Reject it and the workflow returns to Draft Variants.
reject → back to Draft Variants
gates the engine checks without you
Social Post runs in a ConvOps workspace and attaches to the task type, so new work of that type starts on it. Social Post saves each step's output as a task note in ConvOps, and the next Social Post step reads it back. Social Post needs no repository, so a chat client such as ChatGPT or Claude can run it. Connect a client , then install Social Post from the catalog .
Once installed, Social Post is a workflow in your workspace. Ask your AI to change Social Post in plain words; the edit lands on the one step that needs it.
new chat
workflow_step_update · Social Postmore example prompts
The ConvOps Social Post template makes your AI turn a brief into a ready-to-publish post: capture platform, audience, core message, proof and call to action, write three variants with different hook angles, then polish the one you pick. It stops once, before publishing. Reject it and the AI drafts new variants.
In ConvOps, the Draft Variants step writes Variant A, B and C, each opening with a different hook angle (question, bold claim, story or stat), not three rewrites of one line. Each fits the platform's length and tone and carries the core message, the proof point and the call to action from the brief, so you pick between real alternatives.
Any. The ConvOps Brief step records the platform (LinkedIn, X or another) because format and length differ, along with the audience, the core message, a proof point, the call to action and any link. The variants are written to fit that platform, and Polish checks the chosen one reads well there before it goes up for approval.
Yes. In ConvOps, the post can serve as the brief: its core message and proof point go straight into the Brief step. For several channels at once, use the Content Repurpose template, which turns one source into a version per channel, each with its own approved angle. Both ship in the Content Studio kit with Blog Post and Newsletter Issue.
At the ConvOps Polish step your AI asks which variant to run with, then tightens the hook, fixes awkward phrasing, confirms the link and call to action, and checks the post reads well on the target platform. The final post is saved as a task note, and the run holds until an explicit approval is given. Reject it and it returns to Draft Variants.