How to do it
- One workspace per client On the Agency plan, each client gets a workspace with its own connected accounts, brand memory, and agent keys.
- Brand memory per client Voice rules, product names, and banned topics are stored per client, so an agent drafting for one brand never borrows another's tone.
- Agents draft in bulk Your team's agents draft the month in Claude Desktop, ChatGPT, or an n8n flow, scoped only to that client's networks.
- Client approves Clients approve, reject, or request edits from the inbox on desktop or phone. Pro and Agency plans support multi-reviewer approvals.
- Show the record The audit log shows drafter, approver, and timestamps, and can be verified, which settles "who approved this" questions quickly.
Scenario: a craft coffee client wants three LinkedIn posts and a Bluesky thread for a new single-origin release. Your agent drafts all four from the product sheet, the account manager tweaks one headline, and the client approves three and requests an edit on the fourth from their phone. The audit log records each step.
Built for the approval step, not just the drafting step
Agencies have plenty of ways to generate copy. What they lack is a clean path from draft to client approval to publish that holds up when something goes wrong. SocialHandoff puts approval at the center: agents cannot publish what a person has not approved unless you promote them, and no agent can approve its own work.
Agency setup
- Choose the Agency plan for client workspaces. See billing and plans and pricing.
- Create a workspace per client and connect their accounts: LinkedIn, X, Instagram, Facebook, TikTok, and others.
- Write brand memory with the client. Their banned topics and product names are the most valuable part.
- Invite client reviewers and decide whether posts need one approver or several.
Permissions for agency agents
Give each drafting agent a key per client, scoped to that client's networks, with draft and schedule. Keep analytics on a separate reporting agent. Separate keys mean a mistake in one client's automation cannot touch another client's accounts. Read agent keys and permissions.
Reporting to clients
Pull per-post metrics with an analytics-scoped agent for monthly reports. Where the network does not return a metric, the report says so instead of guessing. Engagement and best-time comparisons are labeled as heuristics, which is the honest way to present them to a client.
Pitfalls
- Auto-publishing client content. The trust ladder allows it, but most agencies keep client posts draft-only and use promotion only for low-risk recurring formats.
- Crossed accounts. Scoped keys prevent it; do not share one key across clients.
- Urgent pauses. If a client has a crisis, the kill switch holds queued posts until you resume.
Useful formats: case study post and LinkedIn carousel caption.