Guides

Get alerted to what matters; ignore the rest

Mirgent generates a lot of notifications by default. This guide is the configuration to keep you informed without alert fatigue.

5 min read Beginner

What Mirgent can notify you about

Notifications break into 5 categories: critical (account / job failures), engagement (replies / mentions / comments), discovery (new leads), system (deploys / config changes), digest (weekly summaries).

Default-on for critical. Default-off for digest. The other three are per-category configurable. The right config keeps your inbox + Slack clean while ensuring you don't miss anything urgent.

Scheduling

5 notification categories

Lead Discovery

Channel-aware routing

AI Agents

Severity-based escalation

Analytics

Mute + snooze patterns

Email vs dashboard vs Slack vs SMS

Different channels for different urgencies.

1

Email (default)

All notification categories support email. Best for non-urgent: digests, low-severity engagement, weekly summaries. Don't enable email on every category, alert fatigue kills the signal.

2

Dashboard banner

In-app notifications surface as a banner on the Mirgent dashboard. Best for: items that need action when you're working. No interrupt cost when you're not in the dashboard.

3

Slack webhook (Pro+)

Pipe notifications to a Slack channel. Useful for team setups: one channel for critical alerts, another for daily digests. Configurable per-category.

Tip

SMS is on the 2026 roadmap (Q3). For now, the closest substitute is Slack mobile app, push notifications work the same, no telecom costs.

Critical notifications you should always enable

These are the alerts where missing them costs you actual money or trust.

1

Job failure alerts

When a scheduled post fails 3 retries, you get notified. Otherwise you discover failures days later from a confused client.

2

Session expired alerts

Platform login expired. Without this, jobs queue silently and you wonder why nothing posted. One-click reconnect prompt in the alert.

3

Daily cap reached

When per-platform daily caps hit, queued items auto-defer to tomorrow. Notification tells you 'Twitter cap reached at 2pm; 5 items shifted to tomorrow', explains why nothing posted after 2pm.

Daily / weekly digests

Aggregated summaries instead of per-event alerts. Best for non-urgent categories.

1

Daily digest email

Morning summary: what happened yesterday + what's queued today + AI confidence on the queue. Replaces 50 individual notifications with one readable summary.

2

Weekly Analytics digest

Sunday morning: top-performing post + biggest miss + follower delta + AI commentary. Skip the dashboard; act on the digest.

3

Per-workspace digests for agencies

Agency owners can configure per-client digests sent directly to client emails. Keeps clients informed without making them log into Mirgent.

Mute patterns to prevent fatigue

Mute specific items, users, or rules without disabling the whole category.

Scheduling Guide

Calendar, kanban, and queue modes

AI Agents Guide

Configure autonomous AI workflows

Integrations

Connect RSS feeds and platforms

Lead Discovery Guide

Find leads on Twitter and Reddit

Notification pitfalls

Mistakes that lead to notification fatigue or missed signals.

  • Email-on for all 5 categories. Inbox dies under volume; you stop reading any of them. Pick 1-2 categories for email; route the rest to dashboard or Slack.
  • Slack-channel-of-everything. Same fatigue problem. Two channels minimum: critical (admins notice) + everything-else (poll daily).
  • Disabling critical alerts because they're annoying. Critical means 'this WILL cost you money if missed'. Tune frequency, never disable.
  • Setting up + never reviewing. Notification config drifts over months. Review quarterly, remove what's not useful, add what you missed.

Three notification configurations

Tested by usage type.

  1. Solo: minimal config

    Email only critical alerts (job failures, session expired). Dashboard for everything else. Weekly digest email Sunday morning. Total notifications/week: 5-10.

  2. B2B team: Slack-first

    Slack channel #social-mirgent: critical + engagement (so AMs notice replies). Email digest for senior strategist only. Dashboard for daily work.

  3. Agency: per-client routing

    Each client workspace pipes critical to a per-client Slack channel + AM emails. Agency owner gets only highest-severity (account-level issues).

  4. {guide_not_walk4_title}

    {guide_not_walk4_desc}

  5. {guide_not_walk5_title}

    {guide_not_walk5_desc}

Notifications FAQ

Can I get notified about specific keywords or users?

Yes via Watchlists. Add specific keywords / users; matches generate immediate notifications regardless of category settings. Useful for VIP customer mentions.

What about iOS / Android push?

Mobile app on the 2026 roadmap. Currently use Slack mobile or email push for time-sensitive alerts.

How do I avoid Slack channel noise?

Severity-based filters. Slack channel #social-critical for severity ≥ critical only; channel #social-feed for everything else (poll-style, mute notifications). Most teams settle on this 2-channel pattern.

Can I customize the digest content?

Pro+ unlocks digest customization. Pick which sections to include (engagement, leads, follower-delta, AI commentary). Useful for client-facing digests where you want specific framing.

What time do daily digests send?

Configurable per-workspace. Default: 8am workspace timezone. Best practice: time it just before your morning routine so the digest is fresh when you sit down.

{guide_not_faq6_q}

{guide_not_faq6_a}