Draft Discussions

What draft discussions are for

Most agency teams review social content in Slack. That works until two messages roll past and now nobody knows which version of the caption is final. Draft discussions move the conversation onto the draft itself — threaded comments, @mentions, emoji reactions, and a resolve button — so context never leaves the post it's about.

Available on Scale and Agency plans.

How to access

Open any draft post (chat draft, scheduled post, calendar event). The Discussions panel sits on the right side of the post detail view.

If you don't see the panel, click the 💬 icon in the post's toolbar.

Step 1 — Start a thread

1. Click the Comment input at the bottom of the discussions panel.
2. Type your note. Markdown formatting (**bold**, _italic_, code fences) works.
3. Press ⌘ + Enter to post (or click Send).

The comment posts immediately and notifies everyone watching the draft.

Step 2 — @mention a teammate

1. While typing, type @ to open the member picker.
2. Pick a workspace member from the dropdown (autocomplete by name or email).
3. The mentioned user gets:
   • An in-app notification
   • An optional email digest entry (instant / hourly / daily, per their notification settings)
   • The thread highlighted in their queue

The digest opt-in is the answer to "competitor tools spam me with notifications." Each member controls their own cadence in Settings → Notifications.

Step 3 — Reply, react, resolve

• Reply — click Reply under any comment. The reply nests under the original.
• React — hover any comment and click the emoji icon. Six built-in: 👍 ❤️ 🎉 🚀 👀 🤔. Toggles off if you click again.
• Resolve — when the conversation is done, click Resolve at the top of the thread. The thread collapses and filters out of the "Unresolved" view.
• Reopen — click Reopen on a resolved thread if the conversation comes back.

Step 4 — Internal vs external visibility

When you start a thread, choose its scope from the Visibility dropdown:

• Internal (default) — visible only to workspace members.
• External — visible to invited clients on shareable calendar links.

Most teams keep almost everything internal. External threads are for client-facing feedback that you want them to see in their read-only calendar view.

Step 5 — Filter the panel

The top of the discussions panel has three filter chips:

• All — every thread
• Unresolved — open conversations only
• Mentions — threads where you were @-mentioned

URL state persists, so you can bookmark or share filtered views.

Common patterns

• Round 1 of review — internal threads from the team on the draft.
• Client approval — switch to External and tag the client; they reply on the shareable calendar.
• Post-publish notes — add a thread after publish ("this hit 12k impressions — try the variation next time"). The thread sticks to the published post permanently.

Related guides

• Review and Automation — the broader approval workflow.
• Content Calendar — share read-only calendars with clients.