Who you are connected as on RelayLink

whoami answers which account and which RelayLink host this connection is. set_my_name is what recipients see. A placeholder name is recorded on the account — not guessed from the shape of your address.

3 min read

You have two connectors on one assistant and you are no longer sure which one just answered. Or you invited someone and the request went out under a mangled local-part. Both are identity questions. whoami, set_my_name, and the settings page answer them.

Which account, which host

whoami returns which account this connection is, and which RelayLink host. It reads the handle this deployment actually uses — the same word /docs and the landing page show — so a sandbox names its own handle rather than production's.

That matters because the @ shorthand is taught as a function of the handle. Two hosts teach two words so a package meant for a test account does not land on a real person. When both are connected to one assistant, ask who you are before you draft.

It also says when the account's name is still a placeholder, states the account's preferences, and — if shared memory is switched on — lists what your assistants have noted about you, so whichever one is answering starts from the same picture as the others. Switch it off and that block is simply absent.

The name recipients see

set_my_name and the settings page write the same field: what every recipient sees on packages, requests, and threads that name you. Setting it is one of the first useful things a new account does.

A nickname you set for someone else is a different object — private to your list. Your display name is public to anyone you correspond with.

Placeholder is recorded, not guessed

Accounts created by a cold send or a first sign-in get a display name derived from the address so the row is not blank. That state is a flag on the account. RelayLink does not decide "this looks like a placeholder" by comparing your name to your address. Doing that called real names placeholders.

What the flag changes:

  • A contact row under a nickname does not add a third line that is just the address again
  • list_contacts does not print the placeholder in parentheses next to a nickname
  • The contacts page tells you when your name is still the placeholder, with a link to fix it
  • whoami says so in words

Once you set a name, the flag clears and stays cleared. Requests that went out before that used whatever was there.

Handles and short forms

The long form is this host's handle, shown on /docs. The short form is derived when the handle contains "relaylink" — @rl on production, a sandbox-shaped alias on a sandbox. Both open a draft and never a send. The shorthand is the addressing story.

If you are unsure which connector you are talking to, ask who you are. Then set the name recipients should see — on settings or by telling your assistant — before the next invite goes out.

Frequently asked questions

Why does whoami mention which server I am on?
Because people often connect more than one RelayLink host to the same assistant — production and a sandbox, for example. The handle is how a package meant for the sandbox stays off a real person. whoami says which account and which host.
Is my display name the local part of my email?
Only as a temporary placeholder when the account was created without a name. That state is recorded on the account, not guessed from the address. "Anthony" for anthony@ is a real name someone chose. Set the name on your settings page or with set_my_name.
Do contact requests go out under the placeholder?
Yes, until you set a name. The contacts page says so when your own name is still the placeholder, with a link to fix it. Recipients see that string as who asked.