Verify org email
GPT-6 Astra passed
- Tokens
- 51,325
- Cost
- $0.42
Write the transactional email Norvane Labs sends when someone adds an email address to a Norvane organization on the developer platform and the address has to be verified. Cover the facts below.
Subject: Verify the email address for your Norvane organization. Preview text: Paste the code into your open browser window, or open the verification link. Headline: Verify your email address.
The body, in order:
- One paragraph: the recipient should confirm that this email address should be connected to the tidewell organization on Norvane, either by pasting the code below into the browser window they already have open.
- The one-time code, H7K4-Q2XD-M9RT, set apart on its own in monospace so it can be read and copied at a glance.
- A short line offering the alternative: or by opening the verification link.
- The verification link, https://norvane-email.s3.amazonaws.com/console/verify/H7K4-Q2XD-M9RT, shown as a plain text link so it can be copied if the code cannot.
- A closing paragraph: if the recipient did not ask to verify this address they can ignore the email, and if they have questions they can reply to it.
- Sign-off: The Norvane team.
There is no button; the code is the primary action and the link is the fallback.
The footer links Console, Docs, and Support at https://norvane-email.s3.amazonaws.com/console, https://norvane-email.s3.amazonaws.com/docs, and https://norvane-email.s3.amazonaws.com/support, gives the postal address from tokens.json, the copyright line, and links Privacy and Terms at https://norvane-email.s3.amazonaws.com/privacy and https://norvane-email.s3.amazonaws.com/terms.
Use /world/norvane-email for brand chrome and CSS; this is the transactional family, and the header is the compact N mark (assets.mark and assets.markDark), a single letter N, centered at the top of the email. The code uses the kit's monospace stack from tokens.json. Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.
Dark mode should be supported.
Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.