Email Foundry Deliverability Recovery is exclusively for permission-based email.

If you are, we will ask what changed, what the symptoms look like and which mailbox providers seem to be affected.

This is optional. Add anything the structured questions may not capture, such as when the change started, a campaign that triggered it, or a pattern you have noticed.

Enter the platform, provider or sending setup in your own words. For example: Klaviyo, Mailchimp, HubSpot, SendGrid, Amazon SES, Postmark or our own SMTP setup.

Enter the provider used for receipts, password resets, account notifications or billing messages. If it is the same as marketing, just say so.

Use your normal month rather than your biggest ever campaign.

This gives us context. Transactional traffic is not included in the recovery price unless you later choose to move it.

Count contacts you could realistically market to, not every historical record in your CRM.

Use the average you normally see across your permission-based marketing campaigns. An estimate is fine.

Use the click rate you normally see across your permission-based marketing campaigns. An estimate is fine.

Optional. This lets the results show the value of the revenue channel the recovery programme is protecting.

This helps us understand the commercial impact of poor placement.

Enter whatever you know in your own words. For example: Outlook/Hotmail, Gmail, Yahoo, corporate Microsoft 365 addresses, several providers, or not sure.

Long-running reputation damage normally needs a more controlled recovery than a short-lived campaign problem.

Verification cannot prove consent, but it can stop invalid and risky addresses damaging sending quality.

Broad sends to weakly engaged contacts can drag down the signals mailbox providers see.

Strong early engagement gives providers a cleaner signal before volume is widened.

Keeping permanently inactive contacts in normal broadcasts can steadily weaken sender reputation.

Campaigns and automations can overlap and accidentally create complaint-driving pressure on the same people.

Sudden provider-specific volume jumps can trigger throttling even when the domain looks technically healthy.

One provider can be deteriorating while another remains healthy.

Delivery and open reports alone can miss the signals that explain why a provider is deteriorating.

Shared or poorly reputed tracking infrastructure can become part of the reputation picture.

Shared IPs are not automatically bad. This simply helps us understand which reputation controls are available.

This is sometimes shown as a custom MAIL FROM or bounce domain in your provider.

We will run public DNS checks for SPF, DMARC, MX and BIMI. Use the actual From domain where possible.

Optional. Examples include selector1, google, k1 or a provider-specific value. If supplied, we can check the public DKIM record too.

Optional. If supplied, we will check PTR / reverse DNS and forward-confirmation. Leave blank if your provider manages this or you do not know it.