Treat account health as part of publishing.
A scheduled post cannot ship if the target account needs attention. Slash Social makes that state visible before the team assumes the queue is healthy.
Account health
Catch account issues before posts fail.
Watch account connection state, expired tokens, reconnect needs, and platform-specific blockers from the same Slack workflow as publishing.
Slash Social
App
Lumen Trail
Workflow preview
Planning, approvals, publishing, inbox, and reporting stay tied to one brand.
Today
Action queue for Lumen Trail
NOW
Review the customer proof post
A LinkedIn variant is ready for approval with one Threads adaptation waiting behind it.
Why it matters
Catch account issues before the queue fails at publish time.
- Connection status for social accounts
- Reconnect prompts for expired or disconnected accounts
- Publishing blockers surfaced in Slack
- Platform-specific status tied to each target
Put reconnect work in front of the right owner.
Teams can see which account needs action and route the reconnect to someone with the right access.
Keep platform status attached to the item.
Each platform target can carry its own status so one blocked account does not hide the rest of the work.
Outcomes
What your team gets from account health in Slack.
Built into the same workflow as intake, review, publishing, inbox ownership, and reporting.
Built into the same workflow as intake, review, publishing, inbox ownership, and reporting.
Built into the same workflow as intake, review, publishing, inbox ownership, and reporting.
FAQ
Account health questions
Can one platform fail while others continue?
Yes. Platform targets can carry separate state, which helps teams understand what shipped and what needs attention.
Can account issues show up in Slack?
Yes. Account and publishing blockers can surface where the team can act on them.
Ready when your team is
Bring account health into Slack.
Start with the workflow that hurts most, then connect the rest of your social operation around it.