PromptSharp › Prompt Library › Marketing › Inbox placement dropped: work the causes in the right order

Inbox placement dropped: work the causes in the right order

Opens fell off a cliff and the instinct is to blame the subject line. Work deliverability in the order the causes actually rank.

The prompt — copy and run it

You are an email deliverability analyst triaging a drop in inbox placement. I will describe the program and its metrics. Produce:

A) THE ORDERED DIAGNOSIS, most to least likely given MY data: authentication and domain setup, list acquisition and hygiene, sending pattern and volume changes, engagement segmentation, then content and links. For each, the specific check to run and what a failing result looks like — and say plainly where my data already rules a cause out.
B) THE TIMELINE RECONSTRUCTION: line the drop up against every change I described — a new list source, a volume ramp, a template change, a domain or platform move — and rank which correlate. State clearly where correlation is all the data can support.
C) THE REMEDIATION SEQUENCE, separating what must happen before the next send from what is a multi-week reputation rebuild, with the metric that will show recovery working and roughly when it should begin to move.

My program: [DESCRIBE: send volume and cadence, recent changes, list sources and consent method, authentication setup, engagement segmentation rules, bounce/complaint/open trends by receiving domain if available, ESP]

Rules: Do not invent, estimate, or fabricate any statistic, benchmark, or performance figure — if a number is not in the material I give you, write "not provided" and flag it. Mark every claim I should verify in my analytics or source systems before it is published or presented. Never include customer personally identifiable information or client-confidential terms.

Why this prompt works

Deliverability gets debugged backwards — teams rewrite subject lines while an unconsented list source quietly poisons the sending reputation. Ordering causes by real likelihood and reconstructing the timeline against changes finds the culprit in one pass, and separating pre-send fixes from reputation rebuilds sets expectations before someone declares the fix failed on day two.

Frequently asked

Related Marketing prompts