Instantly

Instantly has a diagnostic endpoint built for exactly this question, and your assistant can call it. It returns the reasons a campaign is sending slowly or not at all, and the assistant can read the campaign's own configuration and the connected sending accounts alongside it, including an IMAP and SMTP connectivity test. That usually turns a vague slowdown into one named cause, such as an account that stopped authenticating.

What you end up with. A plain explanation of what is holding the campaign back, with the specific account or setting named.

Start with it bringing you the information and you deciding.

Never without. Take the diagnostic as the platform's own view of the problem, not as the whole of it. A campaign can also be slow because the schedule and the daily limits are doing exactly what you told them to.

Built on: Get Campaign Sending Status / Get Campaign / List Email Accounts / Test Accounts Vitals

It can pull the analytics overview for one or several campaigns, then break the same period down by sequence step and by variant, and by day. The overview alone tells you the campaign works or does not. The step and variant breakdown tells you whether it is the first email carrying the whole thing while three follow-ups annoy people, which is the version you can act on.

What you end up with. Reply, open, and click rates per step and per variant, with the steps that are contributing nothing identified.

Start with it bringing you the information and you deciding.

Never without. Never compare variants on a handful of sends. Reply rates on a few hundred emails move several points on noise alone, and Instantly will report the difference either way.

Built on: List Campaigns / Get Campaigns Analytics Overview / Get Campaign Steps Analytics / Get Daily Campaign Analytics

It can list every connected sending account, pull daily and aggregate warmup analytics including the health score Instantly calculates, check how many emails each account actually sent per day, and verify the custom tracking domain's SSL and CNAME setup. Deliverability problems show up in these numbers before they show up in your reply rate, which is the whole reason to look at them weekly.

What you end up with. A per-account view of warmup health, daily volume, and tracking-domain configuration, with the accounts trending the wrong way flagged.

Start with it bringing you the information and you deciding.

Never without. A warmup health score is the platform's estimate of how your accounts are doing inside its own warmup network. It is not a reading of what Google and Microsoft think of you, and the two can disagree.

Built on: List Email Accounts / Get Accounts Warmup Analytics / Get Daily Account Analytics / Test Accounts Vitals / Check Custom Tracking Domain Status

It can start an inbox placement test with your prepared email against the provider list you choose, then read the results back: the inbox, spam, and category split by provider and by date, the deliverability percentages against the previous period, and the blacklist and SpamAssassin reports behind them. Running one before a big send is cheaper than finding out from the reply rate.

What you end up with. A placement breakdown by provider showing where the message actually lands, plus the specific spam triggers the report picked up.

Start with it doing the work and checking with you.

Never without. Check whether inbox placement testing is included in your plan before it runs a batch of them. This is a metered service on the workspace billing plan, not a free report.

Built on: Get Email Service Provider Options / Create Inbox Placement Test / Get Inbox Placement Test / Get Inbox Placement Deliverability Insights / Get Inbox Placement Analytics Stats By Date / List Inbox Placement Blacklist & SpamAssassin Reports

It can create a lead list, import the contacts in bulk with your duplicate-handling rule applied, submit the addresses for verification, and then read the verification stats for the list so you can see how much of it is deliverable before any of it goes into a campaign. Sending to an unverified list is the fastest way to damage the sending accounts you just spent weeks warming up.

What you end up with. A named lead list loaded, deduplicated, and verified, with a count of how many addresses came back risky or invalid.

Start with it doing the work and checking with you.

Never without. Confirm the destination list by name before the import runs, and decide the duplicate rule yourself. Leads added to the wrong campaign start receiving that campaign's sequence, and an email that has gone out cannot be recalled.

Built on: Create Lead List / Add Leads in Bulk / Verify Email / Get Lead List Verification Stats / List Lead Lists

It can list the incoming emails, find which campaigns that address sits in, set the lead's interest status so the platform stops treating them as cold, and mark the thread read once it is handled. Where the follow-up is a repeatable pattern, it can also create or update a subsequence that triggers on that interest status, so the next person who replies the same way gets the same treatment.

What you end up with. Replies triaged with interest status set, threads cleared, and a follow-up subsequence in place for the ones that repeat.

Start with it doing the work and checking with you.

Never without. Read the reply yourself before a status change routes it. Interest status drives automated follow-ups, so a misread reply puts a sequence in front of someone who asked you to stop.

Built on: List Emails / Search Campaigns by Lead Email / Update Lead Interest Status / Mark Thread As Read / Create Subsequence / Get Subsequence

This takes three moves and the assistant can do all three. Find every campaign that address appears in, pull the lead out of any subsequence it is running through, and add the address or the whole domain to the block list so no future campaign picks them up again. Removing a lead from a subsequence is flagged irreversible in the connector, so run it deliberately rather than as part of a sweep.

What you end up with. The person out of every active sequence and blocked at the address or domain level, with a written record of what was removed and when.

Start with it doing the work and checking with you.

Never without. Decide address or domain yourself before it writes the block entry, and confirm the exact lead before the subsequence removal, which cannot be undone. A domain block quietly excludes every future contact at that company, including the ones who never asked to be excluded, and nothing later tells you it happened.

Built on: Search Campaigns by Lead Email / Remove Lead From Subsequence / Create Block List Entry / List Block List Entries

It can export a campaign's full configuration, duplicate it, update the copy's name, schedule, and settings, and start sending when you say so. Instantly will refuse to activate until a campaign has a sender account, at least one lead, a sequence, and a schedule, so the assistant can check those four before it tries and tell you which one is missing.

What you end up with. A second campaign with the same sequence and settings, pointed at a new list, with the four launch prerequisites confirmed.

Start with it doing the work and checking with you.

Never without. Activation is the moment real email starts going to real people. Approve the sender accounts, the lead list, and the daily limit as three separate answers before it activates, and never let a duplicate go live still pointing at the original campaign's leads.

Built on: Export Campaign / Duplicate Campaign / Update Campaign / Activate Campaign / Pause Campaign