You spent an hour with Claude working out a cut. Your teammate lives in ChatGPT. There is no shared project, no common sidebar, no workspace you both open. The usual move is to paste a transcript into Slack and hope their assistant can reconstruct what you meant.
Context does not transfer. Their model has none of your session. A paste gives it your order of thought, not a package they can act on.
What has to leave your session
A teammate does not need the jokes, the dead ends, or the third rewrite of the same paragraph. They need:
- The decision you are handing them, or the one you want from them.
- The options you already killed, with one line each on why.
- The assumptions that still hold the decision up, marked as stated or guessed.
- What is closed, and what would reopen it.
That is a briefing, not a chat export. If you cannot name those four, you are not ready to hand the work over. You are asking them to finish your thinking.
Two people, two assistants, no shared room
Each of you connects the assistant you already have. You do not switch products to collaborate. You do not need to be in the same company Slack. Different employers, different tenants, different tools — the message still arrives as a briefing and a link.
If they already hold a RelayLink account, a new thread needs an accepted contact. You invite; they accept; you cannot accept your own request. If they have never signed in, the send travels as email. They can read and reply from the page without creating an account.
You approve what leaves. They approve what comes back. The human on each side is still the sender.
Do not confuse this with writing to yourself
Sending a briefing to your own address is the other pattern: Claude at work, ChatGPT at home, one inbox. No contact request, no email, one participant.
A teammate is not you. Their assistant will treat the package as inbound correspondence — someone else's words — which is what it is. Your nickname for them never appears in what they read unless you chose to share it. Put their real name in the brief.
There are no attachments. Point at the design doc or the ticket. A screenshot dump is not a handoff.
What a good handoff does not do
It does not make their assistant as informed as yours was. It removes the pretend that a paste is a brief. It gives them a labelled package they can argue with, and a thread you can both see later when the cut gets reopened.
If the next hour of your session is already the handoff, connect your assistant and have it assemble the options you rejected while you still remember why.