The subject was “The first email.”
The body was just two words: get excited.
It was a test of a new company email setup. The product and brand were moving toward the name Goodword, and the basic systems had to move with them.
A new name touches more than a logo. The domain needs mail records. Accounts need addresses. Shared tools need new owners. Invitations, support replies, and automated messages need to come from places people recognize.
The first message did not prove that all of that worked. It proved that one email could leave the account and arrive somewhere else.
The private record contains domain and account detail that should not be public. It also contains old working names that are not needed to explain the event.
The safe version is a short operational checkpoint. We had picked the public name. We were preparing the systems around it. Email was one of the first things to test.
The tone was not formal. There was no launch copy in the message and no explanation of the product. It was a note between people who knew why the new address mattered.
Later work would include moving team accounts, setting up support and feedback inboxes, checking authentication records, and preparing a beta announcement.
The test was intentionally small. It did not need a mailing list, a template, or production copy. A single message made it possible to check the sender name, the domain, and the basic route from one inbox to another.
After it arrived, the address could be used as the starting point for the remaining setup. Each additional system could be moved and checked separately instead of treating the new domain as one large switch.
The whole story fit into a subject line and two words.
The first email arrived.