SUPERSEDED — these are v3.2 spec mockups, never wired to code. The platform's actual transactional emails (v3.4, live-rendered from relay-platform) are at /email/platform/.
RelayCTX
/ Email Spec v3.2
Design Tokens — Email Safe
bg
#ffffff
surface
#f5faf9
panel / code bg
#edf7f5
border
#daeee9
text
#0f1f1e
text-2
#446160
text-muted
#8caaaa
teal (primary)
#0d9488
success
#16a34a
warning
#d97706
error
#dc2626
Aa
Body / UI — Arial, Helvetica, sans-serif Syne substitute for email. Used for all headings, body copy, buttons, labels.
CODE
Codes / OTP — 'Courier New', Courier, monospace JetBrains Mono substitute. Used for Relay Codes, OTP codes, metadata.
Transactional Templates
Transactional
Sign-in code (OTP)
Your RelayCTX sign-in code
Magic-link OTP delivery. Large code display, 10-minute expiry note.
Transactional
Relay claimed
Your relay was claimed
Notifies sender when their relay is claimed. Shows Relay Code, claimant, timestamp.
Transactional
Relay expiring
Your relay expires in {{hours_left}}
Warning notification. Relay Code in amber, extend CTA, secondary create link.
Transactional
Registration approved
You're in — RelayCTX early access approved
Approval notification. Tier shown, sign-in CTA, warm welcome note.
Transactional
Team invitation
{{inviter_name}} invited you to join {{org_name}}
Team invite. Inviter name, org name, accept CTA, 7-day expiry note.
Base layout
{{headline}}
{{body}}
{{cta_text}}
Base
Email base template
Reusable shell for all templates
Header, body, CTA, footer. Placeholder variables. Start here for new templates.
Sending Rules
Platform
Resend · raw HTML templates · API delivery
From address
hello@relayctx.com — transactional · noreply@relayctx.com — automated alerts
Reply-to
erik@littlerocket.io for approved/invite emails. no-reply for OTP and system alerts.
Max width
600px — single column, centered, table-safe
Font stack
Body: Arial, Helvetica, sans-serif · Codes: 'Courier New', Courier, monospace
Styles
All inline — no external CSS, no CSS variables. Dark mode via @media (prefers-color-scheme: dark).
OTP / Code display
Courier New 32px · 0.2em tracking · teal #0d9488 · panel bg #edf7f5 · 1px border #daeee9
Relay Code display
Same pattern as OTP — consistent across all email types and the product UI
Legal entity
Footer: "Relay Context Inc. · relayctx.com" on all emails
Unsubscribe
Required on drip/marketing. Not required on transactional (OTP, invite, relay events).
Notification Roadmap
Phase 1
5 transactional templates
OTP, relay claimed, relay expiring, registration approved, team invite
Building
Phase 2
Remaining transactional
Relay expired, password reset, registration denied
Planned
Phase 2
7-email drip sequence
Trial onboarding — Day 0–14. Copy drafted, HTML templates pending.
Planned
Phase 3
Public relay URL
relayctx.com/r/QNHC2C — public claimed/pending/expired view. Unlocks dynamic OG images.
Planned
Phase 3
Dynamic relay OG image
Per-relay social card — code, status, expiry. For sharing and link previews.
Planned
Phase 3
QR code sharing
Generate a QR code per relay — scan to claim. Physical/visual share surface alongside the Relay Code. Useful for in-person handoffs, decks, printed briefs.
Planned
RelayCTX Email Spec  ·  v3.2  ·  Resend · 6 templates · light + dark mode relay-creative / prototype