Catch ProblemsBefore Clients Do.
Configurable email alerts for scheduling gaps, draft pileups, inbox backlogs, expiring tokens, and underperforming posts. Catch the issue before it lands in your client's lap.
Built-in rule library
Scheduling gaps
No posts scheduled for the next N days. Catch dry weeks before they happen.
Draft pileups
M+ approved drafts sitting unscheduled. Time to slot them in.
Outperforming posts
A post is doing X% above your average, reshare or boost while it's hot.
Inbox backlog
Y unanswered comments / DMs older than Z hours. Audience expectations slipping.
Token expiration
A connected account is about to lose access. Reconnect before publishing fails.
Stale automations
An automation hasn't fired in N days. Probably broken or no longer relevant.
Engagement drop
Average engagement falls X% week-over-week. Worth investigating.
Campaign deadlines
A scheduled-end campaign post is still in the queue past its deadline.
Warning Rules FAQ
What kinds of warnings are available?
Scheduling gaps (no posts scheduled for the next N days), draft pileups (M+ approved drafts unscheduled), outperforming posts (engagement > X% above your average), inbox backlog (Y unanswered items older than Z hours), token expiration (connected account about to expire), and stale automations (zero runs in the last N days). New rule types ship regularly.
How often do warnings fire?
Per-rule. Each rule defines its own cadence. Most run daily; some (token expiration) run hourly. You can disable any rule globally or per-workspace.
Are warnings per-user or per-workspace?
Per-workspace. You configure which users get notified when a rule fires, owner only, all admins, or a custom subscriber list. White-label clients can have their own delivery list separate from the agency owner.
Can I create custom rules?
Phase 1 ships with a fixed set of built-in rules. Phase 2 will add custom rule definitions via the UI (and via API). For now, request new rule types in the public roadmap.
Do warnings stack with the inbox feed?
Yes, every warning also appears as an actionable banner in the relevant in-app surface (calendar, inbox, content library). Email is the off-app delivery channel; the in-app surface is always there.
Proactive ops for social
Configurable alerts that catch the issue before it becomes a fire.
See it in Aidelly
Checks that catch a risky post before it publishes.
