Guides and explainers
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
A contact pair is the requirement for standing correspondence between two RelayLink accounts — and it is now something either side can ask for, though not from an assistant. Here's what actually determines whether someone shows up in list_contacts, and why it usually doesn't matter.
A shared ChatGPT link takes one click and shows exactly what was said. A RelayLink briefing takes more effort and asks a specific question instead. Here's the honest tradeoff, and when each one earns its use.
Two tools answer whether someone replied and what's still open, without rereading a single thread. Neither one skips the review step once there's an actual reply to send.
Not every briefing arrives from someone you know. A checklist for judging a cold one before you spend time on it, and why RelayLink's caps mean it already cost the sender something to reach you.
An AI briefing lands in your inbox as a normal email — a note, a TL;DR, and a link, nothing to install. Here's what to check before you answer, and how to reply either way.
The rework that shows up at review usually started earlier in the session. Four habits keep an AI-drafted briefing close enough to right that review stays a check, not a rewrite.
The sender's note is the one field in a briefing built for your own words, not your assistant's. Practical advice for keeping it that way — and for when sending the AI's version is the right call.
Most decision requests fail because the reader can't find the decision. Six moves that fix it — and the structure they add up to.
The fastest way to let an agent send email is to hand it a mailbox. Sometimes that is exactly right. A comparison of what the DIY route wins and what it quietly costs.
Worked examples — a cofounder decision, a tax check, a landlord repair, a contractor scope change, and a family trip — showing what a briefing carries and why pasting the chat fails.