A phone call needs two people on the line at the same moment. A letter needs neither of them anywhere near a mailbox at the same time. That difference — whether both sides have to show up together — is the entire distinction between synchronous and asynchronous communication, and it decides almost by itself how correspondence between two people's AI assistants has to be built.
Synchronous: both sides present at once
Synchronous communication requires both parties in the exchange at the same moment. A phone call. A video call. A live chat where you can watch the other person typing. A shared coding session where two people and one assistant work through the same problem together. Presence is the whole mechanism: take one side away and the exchange does not pause, it stops. A reply has to land inside the window both people are actually there for, or it does not land in that exchange at all. That is why synchronous channels treat silence as a signal — a pause on a call means something, because absence is the exception, not the default.
Asynchronous: sent once, read whenever
Asynchronous communication decouples sending from reading. A message goes out complete, on its own, with no assumption that anyone is on the other end at that instant. Email works this way. So does a letter, a voicemail, a briefing. The sender finishes their turn and moves on; the message waits, unbothered, until the recipient has attention free to give it. The reply might come back in a minute or after a long gap — the format does not build in an expectation either way, which lets both people operate on their own clock instead of a shared one.
Why two people's assistants end up asynchronous
An assistant can take part in either kind of exchange, and which one matters.
Two people sharing a single assistant in one live session — pair programming with a model at the keyboard, or two colleagues talking through a document with one assistant open between them — is synchronous. One shared context, both humans actually present, the assistant a participant in a room that exists only while everyone stays in it.
Correspondence between two different people's own assistants is a different shape entirely. Each person works something out privately, with their own assistant, on their own time — the pattern any AI-mediated communication between two people starts from. There is no shared room to be present in, and neither assistant can make the other person show up. So the channel has to assume the other side is not reachable at that moment — because most of the time, it is not.
That is not a compromise forced on AI correspondence by clumsy engineering. It is the same assumption email has always made, applied to a different kind of sender — the same way letters, rather than a shared phone line, have always let two people correspond without being in the same place at once.
The gap is not just something to route around
It is tempting to treat the delay between send and reply as a cost a faster system would eventually remove. That gets the design backwards.
The gap is what makes private, unhurried thinking possible on both ends. The sender's working session can run as long as it needs — trying an idea, discarding it, asking a follow-up question — because none of that has to happen in front of anyone, and nothing crosses over until the sender decides it is ready. The recipient gets the same room on the way back: read the message, sit with it, work through a reply with their own assistant, and answer once they have actually reached a conclusion — not react on the spot because someone is waiting on a call.
A synchronous channel cannot offer either half of that. Presence has a cost, and the cost is pressure: answer inside the window, or the moment passes. Remove presence from the requirement and both sides get to think before they are on the record — the entire value correspondence has over conversation.
Designing for the gap, not around it
A channel that is genuinely asynchronous breaks if it is built as though it were not. A few things follow from taking the gap seriously:
- Do not require a live connection. A tool that needs both assistants online at once has quietly rebuilt a phone call under a different name.
- Make status checkable, not assumed. Nobody should have to guess whether a message has been read or answered; that is a knowable answer, not a feeling to sit with.
- Compose for someone who is not there. A reader who cannot ask a clarifying question in the moment needs the message to carry its own context — see why composing, not sending, is the hard part of email.
- Do not read "they'll read it eventually" as permission to pad it. The gap buys flexibility about when to answer; it says nothing about how much the reader should have to read — see respecting the reader's time.
None of that is exotic. It is the same discipline good written correspondence has always required, with the gap made explicit instead of assumed away.
Suited to different jobs
Synchronous and asynchronous are not a hierarchy. They suit different jobs. A live call is right when a decision needs to be worked out together, in real time, by people who can interrupt each other. Correspondence is right when each side needs room to think before committing to a position — which, for two people who each keep their own AI assistant private, is most of what actually needs saying.
If you want a channel built for that gap rather than one pretending to be a chat window, connect your assistant — the exchange waits for both of you on your own schedules, not the same one.