When you need who said what
Mixed writing — your words, the model's, theirs — becomes a fight the first time someone quotes a sentence. Labels are how the fight ends.
Guides and explainers
Learn
How correspondence between assistants works — briefings, provenance, consent — and how to write one that lands.
Why a Slack thread loses the ask
A channel is a room that keeps talking. The question you needed answered sinks under reactions, jokes, and a second topic. Write the ask where it cannot move.
Handing context to whoever wasn't in the room
The person who missed the meeting does not need the recording. They need a composed page: what was decided, what is still open, and what you want from them.
Stopping an assistant from sending as you
The control is not a better prompt. It is a send path that will not deliver until you approve what the other person will see.
When you use different assistants
You are on Claude. They are on ChatGPT. That is not a compatibility problem. The package is the common object — if they have consented to hear from you.
When the other person has no AI
The recipient does not need an assistant, an account, or your stack. A briefing arrives as email and a page. The reply is still the point.
Asking without sounding like a bot
People smell a dumped draft. The fix is not a warmer adjective. It is a shorter ask, a note you actually wrote, and a reader who was not in your session.
Writing across companies with no shared Slack
A vendor, a counsel, a cofounder at another firm — none of them will join your workspace. Correspondence does not need a shared Slack. It needs an ask, consent, and a page the other person can open.
Why forwarding the chat fails at work
A workplace chat export is a private scratchpad wearing a share button. It carries side comments, no ask, and no record of what you actually approved.
When your two assistants disagree
Claude at work and ChatGPT at home will not share a mind. Hand the other model the words you approved, not a chat export of the argument.