5-Minute Broken Campaign Checklist (No Technical Knowledge Required)

If you're running a small team and your campaign just stopped producing results, the internet is full of deep technical articles with SPF syntax, DMARC policy modes, and IP warmup curves. Useful for the person who fixes it. Not useful at 9am on Monday when you just need to know whether the problem is your copy or your plumbing.

This is the five-minute version. Seven steps. A browser and a sent-mail folder. At the end you'll know whether the next action is "rewrite the subject line" or "ask a technical friend to look at our DNS."

Minute 0: open Inbox Check in another tab

Go to the Inbox Check homepage. It's going to do most of the diagnostic work for you. Keep the tab open; you'll paste your campaign message into it in minute 2. Free, no signup.

Minute 1: Send yourself the campaign

From the same tool, account, and sender address you use for the real campaign, send the exact message to yourself. If you have multiple personal addresses, send to all of them — a Gmail, an Outlook, and anything else you use.

What you're looking for:

Did it arrive at all?
Is it in Inbox, Promotions, Spam, or Junk?
Is there a red warning banner? ("This message might be dangerous," "unverified sender," etc.)

If it went to your own Spam folder, you have a deliverability problem. Humans at other domains are seeing worse. Stop blaming copy.

Minute 2: Run a seed test

Copy the same campaign message. Paste it into Inbox Check. Hit send. In 2–3 minutes, you'll see folder placement across 20+ real test mailboxes — Gmail, Outlook, Yahoo, and more.

Read it like a scoreboard:

Inbox 70%+: deliverability is not your problem. Jump to minute 6.
Inbox 40–70%: you have a meaningful deliverability issue. Continue to minute 3.
Inbox below 40%: severe problem. Every other theory can wait.

Minute 3: Look at the per-provider breakdown

Your seed result shows placement per provider. Note which providers send you to spam or junk. Three common patterns:

Pattern A: Only Outlook/Microsoft fails

You tripped SmartScreen. Usually either volume ramp, blacklist, or content. The fix lives in the next week; it's not a today-fix.

Pattern B: Only Gmail fails

Most likely domain reputation or content flagging. Check if you recently changed your content template or increased volume.

Pattern C: Everybody fails

Authentication problem (SPF/DKIM/DMARC) or major blacklist. This is the widest-blast-radius scenario and the one you'll need technical help for.

Minute 4: Check authentication (without reading DNS)

Inbox Check shows you SPF, DKIM, and DMARC status as PASS or FAIL. No syntax required. Just look at the three rows:

All three PASS: authentication is fine. The problem is elsewhere.
Any FAIL: that's your culprit. Send a screenshot to whoever manages your domain and ask them to fix it. ("Our DMARC is failing, can you take a look?")

A clean authentication row won't fix bad reputation, but a failing row will cap placement regardless of anything else you do.

Minute 5: The "something changed" question

Think back over the last 30 days. Write down anything that changed:

New sending platform?
New domain or subdomain?
Volume increase?
New content template?
New person added to the team who's also sending from the same domain?
Someone migrated the mail setup (moved to Google Workspace, M365, etc.)?

If anything on this list happened, it's the prime suspect. Deliverability failures almost always coincide with a specific change on the sender side.

Minute 6: The one-replier test

Look at the last campaign's replies and auto-replies combined. Count anything that came back — "not interested," OOO, bounce, unsubscribe. If the total is zero across a campaign of 500+ messages, deliverability is the dominant story regardless of what else you found. Real humans at real companies generate OOOs and unsubscribes even on dead lists; zero of anything means the mail didn't land.

If you have a handful of OOOs and unsubs but no positive replies, deliverability is probably OK and the problem is copy or ICP.

Minute 7: Decide your next action

Based on the last six minutes, exactly one of these is your next action:

Seed test showed 70%+ placement, clean auth, decent auto-replies: your campaign isn't broken. Iterate on copy, subject line, offer, and list quality. Spend your time on the creative work.
Seed test showed 40–70% placement, clean auth: work on sender reputation — reduce volume, warm the domain for a week, trim aggressive content. Re-test in 7 days.
Authentication failure: contact the person who manages your domain (IT, agency, or yourself). Show them the Inbox Check result. Ask them to fix SPF/DKIM/DMARC as flagged.
Placement below 40% across the board: you likely need outside help. This is not a weekend fix. A deliverability consultant or your ESP's premium support can trace the root cause.

What you do NOT need to do today

You do NOT need to learn DNS syntax.
You do NOT need to understand DKIM key rotation.
You do NOT need to read 40-page deliverability guides.
You do NOT need to guess whether the problem is copy or plumbing — the seed test tells you.

FAQ

I don't have time even for five minutes. What's the one-minute version?

Send your campaign to yourself. If it lands in your own Spam, deliverability is broken. If it lands in Inbox, run a seed test to confirm for other providers.

The checklist says placement is low. Can I fix it today?

Sometimes. If the fix is authentication, it's a 1–4 hour task for a technical person. If the fix is reputation recovery (a cold ramp went bad), it's a 1–2 week process of reduced volume and re-warming.

What if my own test mail lands fine but real prospects don't reply?

Your own inbox is a weak signal because your domain trusts itself. The seed test across 20+ mailboxes is the real answer — that's why it's minute 2.

Can I skip the seed test if my ESP shows 95% delivered?

No. "Delivered" in ESP dashboards means SMTP-accepted, not inboxed. The gap between the two can be 40+ points. The seed test is the only way to know placement.

5-minute broken campaign checklist: no tech knowledge needed