Drafts come from five people and three AI tools. Review happens in comments on a doc, in chat, and over someone's shoulder. The final version gets pasted into a scheduler by hand, sometimes the wrong version, and nobody can tell afterwards who signed off.
How to do it
- Everyone drafts where they work Writers use Claude Desktop or ChatGPT, ops uses Zapier, and each agent has its own scoped key.
- One inbox All drafts land in the approval inbox, with per-network previews and inline editing.
- Request edits Reviewers approve, reject, or request edits, and the drafter sees the note.
- Extra eyes when needed On Pro, require two reviewers for posts that need them, such as pricing or partner news.
- Hand off to the calendar Approved posts are scheduled and visible alongside everything else planned for the week.
Scenario: a content marketer drafts a LinkedIn post about a new integration in ChatGPT. It lands in the inbox, the product marketer edits the second sentence, the head of marketing approves, and the post publishes Tuesday at 10:00. Both approvals are in the audit log.
The approval step is the team's shared workspace
Marketing teams rarely lack drafts. What they lack is a single path from draft to publish that everyone follows. When approval lives in chat and docs, versions drift and accountability is fuzzy. SocialHandoff is that single path: every draft, from every person or agent, passes through the same inbox. See approval workflow and content approval.
Setup
- Connect your brand accounts: LinkedIn, X, and Bluesky.
- Write shared brand memory so every drafter's agent uses the same voice and banned topics.
- Connect each team member's tools: Claude Desktop, ChatGPT, and Zapier for automated sources.
- Read approving posts with the team so everyone uses edit, reject, and request-edit the same way.
Permissions by role
| Role | Agent permissions |
|---|---|
| Writers | draft |
| Social lead | draft, schedule |
| Analyst | analytics |
Approval rights stay with owners. On Pro, multi-reviewer approvals add a second sign-off where you need it.
Measuring the workflow
Two things matter: time from draft to approval, and how often drafts are edited or rejected. The audit log shows both. For post performance, per-post metrics come from each network where available, and best-time comparisons are labeled heuristics. Tag links with the UTM builder.
Pitfalls
- Everyone approves everything. Reserve multi-reviewer rules for the posts that need them, or the queue backs up.
- Approval outside the tool. If a post was "approved in chat," it was not approved. Keep decisions in the inbox so the record is complete.
- No pause plan. Decide who owns the kill switch before you need it.
- Unclear ownership of networks. Name one owner per network who checks the calendar weekly, so gaps and clashes are spotted early.
Frequently asked questions
Can reviewers approve from their phones?
Yes. The approval inbox has a phone swipe stack and installs as a PWA.
Can we require more than one approval?
Multi-reviewer approvals are available on the Pro and Agency plans.
Does the drafter see why a post was rejected?
Reviewers can reject or request edits with a note, and the drafter or their agent sees it on the draft.