Get client sign-off before a post goes out

Draft a week, send it for approval, and have nothing publish until the client has actually said yes.

Agencies whose clients want to see posts first, and in-house managers who need a manager's approval.

What it costs you today

• Captions pasted into email or a shared document, then re-pasted back with edits
• Approval that arrives as a message rather than as a decision attached to the post
• No record of who approved what, which becomes a problem exactly once

How it runs instead

1. 01The week gets drafted in placePosts, captions and times sit on the calendar as drafts rather than in a document that has to be transcribed back.
2. 02A role decides who can approvePeople have roles inside a workspace. Drafting and publishing are separate permissions, so the person who writes is not necessarily the person who can send.
3. 03The client sees their own account onlyA client signing in reaches their workspace and nothing else on your book, including any indication of who else is on it.
4. 04Publishing waits for the tapAnything that leaves the building waits for a confirmation, and that confirmation expires after 24 hours rather than sitting open indefinitely.

Approval is a permission inside the product, not a legal signature. It records that a person with the right role approved a post, which is what a disagreement about scope usually needs.

More on this: For agencies