Somebody asks you to catch them up. You have a long session open. The fastest thing in the world is to hit share, or copy the transcript, or drop the link into Slack and write "see below." At work, that is how you hand a colleague your scratchpad and call it a briefing.
The failure is not only that context does not transfer. At work the export is also the wrong kind of document: it was never correspondence.
A chat is indexed to you, and it shows
The model already knows which vendor you mean, which deadline is real, and which joke is a joke. A colleague does not. Every piece of shorthand that resolved against you becomes a puzzle for them. They either guess, or they write back asking you to decode your own notes.
Worse, the session holds things you would never put in an email. The nickname you use for a client. The side comment about a person who was not in the room. The option you floated and then talked yourself out of, still sitting there in confident prose. Forwarding the chat publishes all of that under your name, without the moment where you decide what leaves the room.
There is no ask, so there is no job
A transcript does not say what you want back. It is a record of thinking, not a request. The colleague who receives it has to invent the job: summarise this, decide this, poke holes in this, or just acknowledge that they saw it. Most people pick the cheapest of those and write "looks good."
A briefing names the response. Decision, opinion, review. One question, enough context for a reader who was not in the session, and a note you approved. The colleague can do the job without reconstructing your afternoon.
Approval is missing, so accountability is missing
When you forward a chat, nobody can later say which sentences you signed. The model wrote most of them. You skimmed. A week later someone quotes a paragraph and asks whether that is the plan. You do not remember. They do not have a label. You have an argument about a paste.
RelayLink's send path refuses that shape. A draft is a preview of what the other person will see. You approve it. The labels say who wrote what. If you change the note, that difference is recorded. The chat can stay messy. The thing that leaves does not.
What to do instead
Compose for the person who was not there. State the closed directions in one line each. Mark guesses as guesses. Leave the nickname and the aside in the session. Put one ask at the end.
That takes longer than forwarding. It is still cheaper than the meeting you will schedule to explain the paste, or the week spent acting on a sentence you never meant to publish.
If the colleague is not on RelayLink, the same object travels as email and a page. They do not need an assistant to read it or reply. The chat stays off the record either way.