Product
Everything between the idea and the published post
Socio Pulse covers the part of social media work that spreadsheets and group chats handle badly: getting the client to say yes, and then making sure the thing they said yes to is what actually goes out.
01 - Workspaces
One workspace per client
Each client business is its own space: its own accounts, media, calendar and approvers. People are added per workspace, so a designer working on three clients sees three clients.
Client-side users see only their own business. They never see your other clients, your internal notes, or your team's private comments.
Seven roles, with real boundaries
| Agency Owner | Everything in the agency, including billing |
| Agency Admin | Everything except billing |
| Designer | Creates content for the clients assigned to them |
| Client Owner | Approves, and manages their own team |
| Client Approver | Approves or requests changes |
| Client Viewer | Sees the calendar and what published |
02 - Approvals
The approval is a record, not a message
A post moves through defined states. It cannot skip one, and it cannot go backwards into a state that would erase what happened.
When a designer resubmits after changes, the approval round increments. An approval from round one can never be mistaken for approval of round two - which is exactly the argument that otherwise happens by email.
What the client sees
The finished post, per platform, as it will appear - not a screenshot someone pasted into an email. They approve it, reject it, or request changes with a reason. Comments stay attached to the post.
What gets recorded
Who decided, what they decided, when, on which round, and why. That history is permanent and survives people leaving the agency or the client.
03 - Composer
Write once, adjust per platform
One caption is the base. Change it only where a platform needs something different - a shorter version for one, different hashtags for another. Anything you do not customise follows the base, so editing the base updates everything that was not deliberately changed.
Character limits, hashtag limits and supported post types come from each platform's real rules, held as data rather than hardcoded. When a platform changes a limit, we change a row - not a release.
04 - Calendar
Scheduling that survives daylight saving
Each client has a timezone, and you schedule in theirs. A recurring "every Monday at 9am" stays at 9am local through a daylight-saving change, because the rule is evaluated in the client's timezone and only then converted.
Every occurrence of a repeating series is its own post with its own approval, so one week can be edited or skipped without disturbing the rest.
05 - Media
A library per client
Upload once, reuse anywhere for that client. Files upload directly to storage rather than through the application, so large video is not limited by a web server's upload cap.
Deleting a file tells you which scheduled posts use it first. Deleted files sit in a recycle bin for seven days before they are permanently removed.
06 - Publishing
Status you can trust
A post going to three accounts has three outcomes. If two succeed and one fails, it says "partially published" and names the one that failed, with the platform's reason. Retrying only touches what failed.
If a publish is interrupted and we cannot be certain whether it went out, we stop and tell you rather than retrying and risking a duplicate on your client's feed.
Platforms
Official APIs, and the current status
Every integration goes through the platform's own review before we enable it. This list is generated from the running system, so it cannot say "available" for something that is not.
See it with your own client
Create an account, add one client business, and run a post through the whole approval flow. No card required to start.
Create an account