Use case

For agencies auditing client deliverability.

Run consistent email deliverability audits, validate client lists, monitor domains, inspect DMARC reports, and produce clearer fix lists.

Agency audit template Pricing

A repeatable client audit stack

Agencies need consistent evidence, not one-off screenshots. WillItInbox lets teams test messages, validate lists, inspect domains, and explain fixes in a common language.

Run real-message tests from each client sending system.
Validate sample or full lists before campaign launches.
Monitor domain and DMARC health after implementation.

Client-facing outcomes

The highest-value deliverability work is making invisible failures obvious and prioritized.

Technical report

Show SPF, DKIM, DMARC, DNS, header, content, and link findings.

List risk

Quantify invalid, risky, catch-all, disposable, role, and unknown recipients.

Domain health

Track whether fixes hold after DNS and ESP changes.

Workflow

Turn the use case into a repeatable checklist

Every use case should define what gets tested, who owns the fix, when to retest, and which WillItInbox surface captures the evidence. That keeps deliverability from becoming a last-minute opinion fight.

Use /test for the final message.
Use /validator/bulk for imported, stale, or outbound lists.
Use /domains and /dmarc for ongoing sender-domain health.
Use /docs/api when checks should run automatically.

Outputs

What a useful result looks like

The result should not only be a score. It should identify the highest-risk findings, the owner, the expected fix, the retest trigger, and the accepted risk if a warning remains.

Domain monitoring

Track SPF, DKIM, DMARC, MX, TLS, PTR, blocklist drift, ramp guidance, and provider reputation evidence in /domains.

DMARC visibility

Use /dmarc to label sources, find unknown senders, and move toward enforcement safely.

Placement diagnostics

Use /placement for diagnostic seed testing when placement needs a sample beyond technical scoring.

Can one checklist serve every team?

The layers are similar, but priorities differ. SaaS teams protect product reliability, agencies need client-ready evidence, newsletters need pre-send hygiene, and developers need API-safe automation.