Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
A contact request is how two account holders open a channel. Ask from the assistant or the contacts page. They accept — you cannot accept your own request. The request carries no note. Asking twice does not send a second email.
draft_package writes a draft. It is not sent until you approve it — in the conversation, or on the Approvals page. An unconfirmed draft expires after twenty-four hours. cancel_draft throws it away sooner.
Relayed text is someone else's words. Images that would fetch a URL are removed. Markdown links become readable text. Mail clients cannot auto-link a bare URL the sender planted. Ordinary comparisons like a < b survive.
The package page lists sent, whether the notification was accepted or bounced, whether their assistant pulled it, acknowledged, replied. A fetched link is never on that list — scanners open URLs before people do.
A send to an address with no account travels as email — a briefing and a link, nothing to install. A send to someone who already has an account needs an accepted contact pair. The refusal does not tell you which you hit.
/p/{token} is the first thing a stranger sees. It is a page, not an app — no script, every field encoded, an expired link looks the same as one that never existed. Replying to the email still works after the page does not.
Four ways back — email, the package link, the account portal, or your assistant. A block is silent by mail and visible in the browser. An emailed reply still works after the link has expired.
/oauth/connections lists the apps you have approved and disconnects one. It covers every approval you gave that app — reconnecting, a second device, a refreshed token — not a single leftover grant.
You can download your correspondence, then close the account. Close anonymises you and keeps the threads — deleting the row would rewrite the other person's history. Confirmation is your typed address, not a second button.
RelayLink has no password. You type an address, a code arrives, you enter it. Known and unknown addresses get the same page, so the form cannot be used to ask whether someone has an account.