MARKETING

Daily Domain Reputation Scorecard: Rank Recipient Domains and Page on Critical Drops

Each morning it builds a per-domain deliverability scorecard from yesterday's send data, grades every recipient domain, posts the ranked digest to Slack.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionAggregate per-domain metrics for yesterdayPostgreSQLPostgres
  • LogicScore and rank domains into health bands
  • OutputPost ranked scorecard to SlackSlack
  • LogicAny critical high-volume domain?
  • ActionPage on-call via PagerDutyPagerDutyPagerDuty

What it does

Once a day this workflow rolls up the prior day's sends, bounces, complaints, and open signals per recipient domain, scores each domain into healthy / watch / critical bands, and produces a ranked scorecard. It posts the full digest to Slack so the team starts the day with a clear deliverability picture, and if any high-volume domain has dropped into the critical band it escalates to PagerDuty so on-call can intervene before the next big send.

When to use it

Use this as your daily standing report when you want proactive visibility into reputation drift rather than only reacting to spikes. The PagerDuty branch ensures a genuine emergency doesn't sit unseen in a chat channel overnight.

How it works

  1. 1A daily schedule fires in the morning.
  2. 2Postgres aggregates yesterday's per-domain send, bounce, complaint, and engagement metrics.
  3. 3A logic step scores and ranks domains into health bands.
  4. 4Slack posts the ranked scorecard digest to the team channel.
  5. 5A logic step checks for any high-volume domain in the critical band.
  6. 6PagerDuty pages on-call when a critical domain is found.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.