Approvals that do not
get lost in an inbox.
Writing the text is usually quick. Agreeing on it is what takes time. capty replaces the chain of forwards, screenshots and follow-up questions with one flow where the post, the comments and the decision sit in the same place.
The problem
When feedback arrives by email, nobody can tell which version is current. Comments get lost, and eventually something goes live that nobody actually approved.
Trimmed. Approved from my side.
Illustrative example. The interface shown and the values in it are for illustration.
What that means in practice
Four things that make the difference day to day.
Comments on the post
Feedback sits with the post it refers to, not in a thread you have to go looking for.
One-click sign-off
Whoever gets to decide decides right there. No reply mail, no "fine by me".
A trail you can follow
Who commented and approved what, and when, stays on record. That ends arguments about who signed off.
Roles and rights
Not everyone on the team needs approval rights. Writers write; approvers approve.
How it works
Submit
The finished post goes to review instead of straight out.
Comment
The team responds, right on the post.
Approve
One click and the post is cleared to publish.
Frequently asked questions
Can approval require more than one person?
The approval flow can be set to the people who need to agree. How many that is, is up to you.
What happens if a post is rejected?
The post goes back into editing along with the comment. Nothing is deleted and the history stays intact.
Is this the same as client approval?
No. Team approvals are internal. For external clients without a capty account there is separate client approval.
Related features
Try capty before everyone else
We are close to launch. Join the waitlist and secure your spot.
Join the Waitlist
Trim the first line, otherwise good.