The first completed sign-in used to drop you on an empty inbox. Nothing on that page said the next step was to paste one address into an assistant, or to open /docs. The code email cannot carry that — it goes out on every sign-in, to people who already know.
So there is a second mail, once.
When it goes
On the transition to a real account. Two self-serve paths:
- You verified a sign-in code, and the account had never been activated.
- You completed a first OAuth consent, same condition.
After the activation is committed. If the mail cannot be sent right away, the sign-in still succeeded, and the mail is retried. A welcome that fails is no reason to refuse the person who just proved they own the mailbox.
It does not go when:
- An operator provisions the account. Nobody may be reading that address yet.
- You issue an API key. That happens in a portal session that already went through sign-in.
Never again after that first time.
What it carries
No marketing. No ask. One sentence on what RelayLink does, then the same four steps as the checklist at the top of your account page, in the same words:
- Connect your AI — Claude, ChatGPT or Claude Code.
- Set your name — the name people see when you send them something.
- Save where you left off — tell your AI "Save where we left off in RelayLink." Your AI saves a short summary that only you can see.
- Pick it up in a new chat — in the same AI or a different one, say "Pick up where I left off in RelayLink."
Four of RelayLink's own URLs, in the text as well as the template:
/account/connect— the connect guide, with the address and the steps for each app- The setup guide, for reading first
/docs— the reference page, for anybody building their own connection/account— your account page, with everything you've saved, sent and received
It does not restate the MCP URL or whether a key header is required. Those change by host, and the connect guide prints what the host you signed up on uses. A sentence in this mail would be the copy that goes stale.
Reply-To is empty, like the sign-in code. A reply goes to the From address, which is why the domain has to receive mail.
What it is not
It is not the notification that arrives with a briefing. A stranger who was written to and has not signed in gets orientation there — receiving is free, nothing to install — because that mail is the product for them. They have not activated. They do not get this one until they do.
It is not a magic link that signs you in. The code mail still does the proof of the mailbox. This one assumes that already happened.
If you activated and never saw it, sign in at your account anyway. The checklist at the top of the page has the same four steps.