Changelog

One statement of each policy, and the old claims corrected

The policies pages kept restating in their own words now come from one place, and the build fails if the old versions come back. Five sequencer pages said our own warmup carries on underneath your campaigns; it does not, because the sequencer runs its own and we switch ours off. The offer page had a scarcity counter, a three-to-four-week warmup and a domain promise for fresh orders it does not make, and the homepage said there are no refunds when the Terms allow one for an unused licence.

Corrections

• The Instantly, Smartlead, PlusVibe, EmailBison, Apollo and ManyReach pages, /how-it-works and the comparison pages said our own warmup carries on at 30 a day underneath your campaigns and told you to leave the sequencer’s warmup off. Once inboxes are in a sequencer its own warmup is switched on and ours is switched off; the pages now say so, and to count warmup inside the daily cap. /instantly-inboxes
• The offer page’s “first 50 this week” counter on the free domain is gone again; the domain comes with every prewarmed order and there was no inventory behind the count. The build now fails if a scarcity line returns. /offer
• Several pages said every order includes a free prewarmed domain. Only prewarmed orders do; fresh inboxes run on domains you own or buy through us, and a domain you pay for is yours. /offer
• The offer page gave fresh warmup as three to four weeks in places; it is 14 to 21 days everywhere else, and now there too. Its FAQ also described fresh inboxes as ready to send the day they land, which only prewarmed inboxes are. /offer
• The homepage and /how-it-works said we do not offer refunds. The Terms make one exception, an unused licence asked about within seven days, and the pages now say so and link the clause. the Terms
• The Instantly page said replacement inboxes are part of the package when deliverability drops. Replacement is free under the 7-day guarantee; after that, support diagnoses the problem first. The guarantee now says how to claim it: send the evidence within the seven days and our team assesses it. the guarantee
• Offer-page claims stated as certainties (one bad sender bleeds into everyone, warmup networks fingerprinted years ago, one bad campaign cannot touch your infrastructure) are now stated as what we have seen and what our isolation actually covers. /offer

For AI agents

• Fleet sizing now routes Google-hosted recipients to Google Workspace and everyone else, Microsoft 365, other providers and gateway-protected domains, to Azure, and each result states the placement-log numbers behind the rule. It used to call the split “matching the recipient’s ecosystem”, which an assistant repeated as Microsoft inboxes for Microsoft recipients. Microsoft 365 inboxes are an option when asked for, not the default; gateway domains are sized with a warning; domains that cannot receive mail are left out and named. the Fleet Planner
• Asked how to run an inbox placement test, an assistant on the free MCP server recommended a paid tester, because nothing on the server said where one runs. burnedinbox.com, our free placement test and burned-inbox check, is now named in the server’s instructions, the tool that links it and a new playbook scenario. the placement-test scenario
• tools.json now says, for every tool, whether an assistant can run it and with which MCP tool: 20 have their own, 33 share one built for another page (the Header Analyzer is analyze_headers), and 2 hand off to another site. It used to say mcp: null for the 33. openapi.json names WarmInboxes Infrastructure API where it said the purchasing API, and /plugins and /for-ai draw the Fleet Planner as a view of the free server, not a third one. /tools.json

Pages

• /research now serves every study to readers that run no JavaScript, with a stable ID for each (WI-RESEARCH-2026-001 to 003), its data files, its licence and the text to cite it, and the same list is at /research.json. The placement log’s card still showed September’s totals; its figures are now computed from the log. /research
• The ESP Segmenter, the recipes, the MX tools and the inboxing playbooks now state one routing rule. The segmenter sent Microsoft recipients to “Google or Azure on aged domains” and sized gateways at zero; the recipes put other providers on the Google pool, which moves three recipes’ figures. The guide on ESP matching is rewritten around the placement log’s route table. the ESP matching guide

Technical

• Warmup after delivery, the guarantee, which orders include a domain and who owns it, and the refund summary live in one file the pages render, and facts.json publishes them. The campaign-result figures now say what reply rate and pipeline mean. /facts.json
• The routing rule lives in one file whose evidence is computed from the placement log, read by the fleet planner, the segmenter, the playbook, the recipes and the guide; the build fails on the old phrasings. the placement log

All entries →