One control room for every Instantly sending mailbox

See warmup status, daily send volume, and bounce risk for every sending account in one grid, with the riskiest mailboxes floating to the top.

App
InstantlySlackSalesOperationsResearch & MonitoringAI Reports
PromptCreate

Build me an app that works as a single control room for the health of my cold email sending infrastructure. I run outbound from dozens of sending mailboxes across many domains, and today the only way to check on them is to click through Instantly account by account. I want one screen instead.

The main view is a grid of every sending account, loaded from Instantly's List Email Accounts. Group the rows by sending domain, because reputation damage travels domain-wide and one bad mailbox drags its siblings down with it. Each domain gets a group header showing the domain name, how many mailboxes sit on it, and the worst health flag among them, so a bad domain is obvious before I expand anything.

Each mailbox row shows: the email address, its warmup status pulled from Get Warmup Analytics, how many emails it has sent today versus that account's own configured daily sending limit from Get Daily Account Analytics (show it as sent of limit plus the percentage of the limit consumed), its recent bounce rate, and a red / amber / green health flag.

Bake in these health rules. A mailbox is RED if its bounce rate is above four percent, or if it fails Test Account Vitals, or if Instantly reports it as disconnected or inactive. AMBER covers the warning band: bounce rate climbing between roughly two and four percent, warmup switched off while the account is actively sending, or the account running at or over its daily limit. Everything else is GREEN. Sort so the riskiest float to the top: red first, then amber, then green, and inside each band sort by bounce rate highest first. Order the domain groups themselves by their worst member, so the most damaged domain is the first thing I see.

From any row I want to act without leaving the screen. A Run vitals button calls Test Account Vitals on demand and shows the pass or fail result inline with whatever detail comes back. A warmup toggle calls Enable Warmup for Accounts or Disable Warmup for Accounts. An editable daily limit field writes the new value back with Update Email Account. After any action, refresh that row and recompute its health flag. Note that the warmup enable and disable calls kick off background jobs rather than finishing instantly, so show a pending state on the toggle until the change is confirmed.

Each domain group header gets a "Diagnose this domain" button that kicks off a background agent. The agent gathers every mailbox on that sending domain, pulls Test Account Vitals and Get Daily Account Analytics for each one, works out which campaigns those mailboxes feed, and pulls Get Campaign Analytics for those campaigns. It should pay special attention to campaigns sitting in Instantly status -1 (Accounts Unhealthy) or -2 (Bounce Protect), since those are direct signals that sending health is already hurting delivery.

The agent then writes a plain English remediation brief back into the app, stored against that domain and displayed in a panel on the domain group with a timestamp, keeping past briefs as history so I can see whether a domain is recovering or getting worse. The brief should say what is actually wrong, name the worst offending mailboxes and campaigns, state whether the problem is domain-wide or isolated to one or two accounts, and give specific recommended steps such as resting the domain, cutting a daily limit to a particular number, re-enabling warmup, or pausing a campaign. Write it for a human operator, not as a data dump.

Two follow-up actions hang off the brief. First, a button to run Pause Campaign on the worst offending campaign the agent identified, with a confirmation step before it fires. Second, a button to post the brief to a Slack channel using the Slack Send a Message action, with a channel picker so I choose where it lands.

A few details that matter: persist my daily limit edits and the generated briefs, show when the grid data was last refreshed with a manual refresh button, and keep the whole grid readable on one screen. Dense is fine, I would rather see forty mailboxes at once than scroll through paginated cards.

What does this prompt do?

  • Puts every one of your sending mailboxes in a single grid, grouped by sending domain, so you can see the health of your whole setup at a glance instead of opening each account.
  • Flags each mailbox red, amber, or green. Anything above a 4% bounce rate or failing its health check goes straight to red and floats to the top of the list.
  • Lets you fix problems on the spot: run a health check, switch warmup on or off, or change a mailbox's daily sending limit without leaving the screen.
  • Adds a Diagnose this domain button that sends a research assistant to investigate a struggling domain, check the campaigns it feeds, and write you a plain English fix list you can share to Slack in one click.

What do I need to use this?

  • An Instantly account on a plan that allows connections from other tools (Growth or higher)
  • Your sending mailboxes already connected inside Instantly
  • A Slack workspace, only if you want to share the domain briefs with your team

How can I customize it?

  • Move the thresholds: the 4% bounce rate line that triggers red, and the warning band that turns a mailbox amber.
  • Change how rows are grouped and sorted, for example by client or by mailbox provider instead of by sending domain.
  • Pick which Slack channel the domain briefs get posted to, or leave the Slack step out entirely.

FAQs

Why does a 4% bounce rate turn a mailbox red?
Staying under 4% is the widely used safety line in cold email. Once you drift above it, inbox providers start treating your sending domain as a risk, and the damage builds quietly before you notice it in reply rates. The app treats that number as a hard line so a slipping mailbox gets your attention immediately, and you can move the threshold if your team works to a stricter target.
Why are the mailboxes grouped by sending domain instead of listed flat?
Reputation damage is contagious across a domain. If one mailbox on a domain starts bouncing, the other mailboxes sending from that same domain inherit the problem, so fixing accounts one at a time misses the real picture. Grouping by domain shows you whether you have one bad mailbox or a domain that needs to be rested entirely.
Does this change anything in my Instantly account automatically?
No. The app only reads your account data until you click something. Turning warmup on or off, changing a daily sending limit, and pausing a campaign are all manual actions you take from a row or from a brief, and pausing a campaign asks you to confirm first.
What does the Diagnose this domain button actually do?
It kicks off a background assistant that looks at every mailbox on that domain, checks each one's health and how much it is sending, then looks at the campaigns those mailboxes feed to see whether delivery is already suffering. It writes the findings back into the app as a short plain English brief telling you what is wrong and what to do about it, and you can post that brief to Slack or pause the worst campaign straight from it.
Do I need Slack for this to be useful?
No. Slack is only used for sharing a domain brief with your team, so the grid, the health flags, the row actions, and the diagnosis briefs all work without it. Connect Slack if you want deliverability problems to land in a channel where the rest of the team sees them.

Related templates

Client-by-client cold email pipeline review for agencies

Pick a client and a date range to see sent, replies, meetings booked and the real deal value your cold email produced, campaign by campaign.

Instantly
HubSpot
Slack Bot
App
Partner tier review board for quarterly promotion calls

Work every partner tier decision from one board, with the revenue and commission numbers, clear promotion thresholds, and AI review briefs.

Introw
HubSpot
Slack
App
Reconcile partner commissions between HubSpot and Introw

Open one board at month end to find every closed deal missing a commission, every commission with no deal behind it, and every amount that does not add up.

Introw
HubSpot
Slack
App
Compare cold email sequence steps and rewrite the losers

Line up every step of every Instantly sequence side by side, spot the follow-ups that get no replies, and rewrite them with your approval.

Instantly
App
Partner payout approval queue with Xero bill handoff

Review Introw partner payouts line by line, approve them from one board, raise the matching bill in Xero, and post every approval to Slack.

Introw
Xero
Slack
App
One inbox for every Jira Service Management approval waiting on you

See every access, purchase and leave request waiting on your decision in one screen, approve or decline in place, and send the reason back to the requester.

Jira Service Management
Confluence
Slack
App

Stop clicking through mailboxes one account at a time.

Get one screen that shows which sending accounts are about to burn your domain reputation, and fix them before they do.