Channel · rank 3 of 100
Transactional email
The short mail that confirms what you just did, such as a registration, without becoming a spam tool.
What it is
A mail a website sends because you did something: a confirmation, a receipt, a reference number. You do not ask for it separately; it follows your action.
For TrooIDs it means one short confirmation with a reference id after someone registers interest.
Why it matters
- Rank 3 of 100 in the TrooIDs channel ranking, with a score of 9.0.
- Both models put it in the top class: 80% or more of companies would open it.
- When an AI agent runs this channel, both models agreed it also does the work of: status-page notifications, calendar subscription feeds, email markup read by mailbox providers.
- See how the ranking works.
What TrooIDs built
A confirmation mail, built and tested in a lab copy that runs the site's real registration handler unchanged:
- only clean, consented registrations get a mail; spam, trap-field fills and posts from other sites never do;
- the mail never repeats what the visitor typed, so it cannot carry someone else's message;
- exactly one mail per registration, whatever retries happen;
- an independent mail parser reads every message with 0 defects.
Proof status, in three parts
- Live on this site: you can check it on trooids.com now.
- Fixture: built and tested with sample data on our test copy of the site; it is not running on trooids.com.
- Architecture: designed or required, not built here yet. Items marked "Owed" are still to do.
Live on this site
- The register-interest form and its handler /api/lead, which decides whose registration is clean enough to ever be mailed.
- The confirmation mail: since 28 October 2026 everyone who registers gets one short mail from noreply@trooids.com, signed for trooids.com (DKIM), at most 3 per address per day, and none for a registration scored as spam. Checked with our own test address: the mail arrived, the cap and the spam rule held.
Fixture
- The confirmation mail: 5 of 5 checks passed in the lab copy (34 cases, 21 October 2026); 53 of 53 build obligations met (status 28 October 2026).
Architecture
- Owed: a check by a mail receiver outside our own mail server. Our own server reads DKIM pass and DMARC pass; an SPF check against public DNS passes.
- Owed: the reverse-DNS name of the sending mail server, which helps delivery to large mailbox providers.
Was this page useful?
Anonymous: we keep your answer and, if you write one, your comment with email addresses and phone numbers removed — nothing that identifies you. Privacy.