Below this confidence level, Claude sends the draft to your review queue instead of auto-sending. Higher = more human oversight. Lower = more automation.
This is the instruction Claude follows when drafting every reply. Edit to match your tone and any specific things you always want included.
Submit delisting request
Generate a professional, registry-specific removal letter and submit it. Each registry has different requirements — our system knows them all.
Bulk registry check
Check a domain against all 68 registries and get a full report with each registry's status and removal URL. Use this before drafting removal letters.
Full DNS record generator
Enter domain and configuration — we output every record they need to copy-paste into their DNS provider.
Formal dispute package generator
Creates a structured legal-style evidence package: clean sending history documentation, ISP contamination letter template, evidence summary, and the formal submission letter. Most registries have never received a submission this professional from a small business — it dramatically increases removal success rate.
IP pre-validation check
Before recommending any IP migration, check the destination IP against all registries. No point migrating to another dirty IP.
Warm-up schedule generator
Generate a 6-week IP warm-up plan based on the client's target sending volume. A new IP needs graduated volume to build reputation — this plan is what we share with clients post-migration.
Google Postmaster setup guide
Instructions to send to client for setting up Google Postmaster Tools — the only way to see your actual spam rate and reputation at Gmail. Required for any serious reputation recovery.
Reputation recovery campaign brief
After delisting, a client's internal Gmail/Outlook reputation may still be damaged. Generate a structured sending brief — the right volumes, frequency, and content signals to rebuild trust at the inbox provider level.
ISP direct escalation letter
Instead of just submitting a removal form to the blacklist, we write directly to the hosting provider's abuse team — not the automated mailbox, but the actual human abuse department manager. We formally request they investigate and issue a signed statement confirming the listing was caused by another tenant. This letter can be attached to removal submissions and has a dramatically higher success rate for L3 and range-based listings.
Registry policy challenge
UCEPROTECT Level 3 is controversial — it lists entire IP ranges based on the actions of other users, which many email standards bodies consider to be collective punishment. We've built a formal policy challenge letter that cites IETF RFC standards, industry best practices, and EU data protection principles to challenge whether the listing itself is legitimate. For some registries, this alone leads to removal.
Proactive sender reputation certification
Rather than waiting to get listed, we help clients apply to legitimate sender certification programmes — Return Path (now Validity), Google's Trusted Mailer programme, and ISIPP accreditation. Certified senders bypass many blacklist checks entirely. This is a proactive reputation asset most small businesses have never heard of, but it's what large ESPs use to protect their clients. We handle the application process.
Subdomain isolation strategy
Instead of sending all email from the root domain, we help clients set up a dedicated sending subdomain (mail.domain.com, send.domain.com) with its own clean reputation, separate DNS authentication, and isolated IP. If the sending subdomain ever gets listed, the root domain — and the business's credibility — is completely protected. Simple to implement, powerful protection. Almost no small business does this.
Paste bounce notification text
Paste the full text of a "Mail Delivery System" / "Undelivered Mail Returned to Sender" email. We extract every error code, identify the recipient addresses, and generate a complete diagnosis with fix steps you can send directly to the client.
Error code lookup
Look up any SMTP error code and get the exact cause and client-ready fix instructions.
Gmail authentication rejection fix kit
For clients getting 550-5.7.26 — Gmail blocked because DKIM and SPF both failed. This is the most common bounce we handle. Generate a complete fix package for any hosting provider.
Mail queue flush instructions
Generate step-by-step instructions for clearing a stuck mail queue — specific to the client's hosting panel. This stops the bounce flood immediately.
Complete client email — ready to send
Generate a professional email to send directly to the client explaining the problem, what caused it, and exactly what they need to do. Ready to copy and paste.