Protect your Apollo sender reputation before sequences auto pause

I want an app my outbound team opens every morning to protect our sender reputation, before Apollo pauses anything on its own. Build it against Apollo using a master API key, plus Slack Bot for sharing. The main screen is a deliverability risk board with a date range picker at the top and two tabs, Sequences and Mailboxes.

The date range picker drives every number on the page. Default it to the last 7 days and let me pick any range. This filter is load bearing: Apollo's Search Outreach Emails has a 50,000 record display limit, so scope the email search to the selected range, paginate through the results, and show a clear notice on screen if the range is wide enough to hit that cap, so I know when the numbers are truncated.

The Sequences tab lists one row per active sequence, pulled with Search Sequences. Each row shows the sequence name, emails sent, bounce rate, reply rate and spam complaint rate over the selected range. Build those numbers by pulling the sent emails with Search Outreach Emails, joining each email back to its sequence, and using Check Email Stats for per email delivery and engagement detail. Sort worst first, by bounce rate descending.

The Mailboxes tab lists one row per connected sending mailbox, pulled with List Email Accounts, with the same four columns computed by joining the same emails back to the sending mailbox instead of the sequence. Sort worst first here too. Each mailbox row must also list which sequences that mailbox is currently sending for, because one bad mailbox usually drags several sequences down at once. This per mailbox view is the important part: Apollo's own protection is per sequence, not per mailbox, so a failing inbox is invisible until several sequences start tripping thresholds separately.

Colour band the rows against our thresholds. For bounce rate, under 2 percent is healthy, 7 percent or above is a warning, and 10 percent or above is critical, because 10 percent is where Apollo auto pauses a sequence. Band the other columns against healthy benchmarks too: spam complaints under 0.1 percent, reply rate 5 percent or better. Keep the threshold values in one place in settings so we can adjust them without touching the rest of the app.

Clicking any row opens a detail panel for that sequence or mailbox. The panel lists the contacts whose emails bounced or failed inside the selected range, showing contact name, email address, which sequence they were in and what happened. I select the ones I want with checkboxes and remove them from the sequence with Update Contact Status in Sequence, in bulk, with a confirmation step and a clear result summary.

From the same panel I can pause or resume the sequence in place with Deactivate Sequence and Activate Sequence, without leaving the app. Bake in the cleanup rule Apollo expects: removing bounced contacts is the cleanup that should happen before a paused sequence resumes. So if a sequence is paused and still has bounced contacts I have not removed, warn me on the resume action and tell me how many are outstanding, instead of silently resuming it.

Add a Post to Slack button that sends the current risk summary to our revops channel using Slack Bot Send a Message. The summary should carry the date range, the worst sequences and worst mailboxes by bounce rate with their numbers, anything already at or over the critical threshold, and a count of contacts removed and sequences paused from the app in this session.

Everything reads live from Apollo when I open the app and when I change the date range, with a manual refresh available. Remember the date range I last used and the Slack channel I last posted to, per user. There is no schedule here, this is a surface a person opens and works out of.