How to keep in touch with a friend who has been deployed

A friend gets deployed and the friendship does not come with a warning label. You are used to a certain rhythm — a reply within a day, a running joke that carries on in the group chat, a "call me when you're free" that actually gets answered by evening. Then that rhythm becomes unavailable for months, on a schedule nobody can tell you in advance, and there is no obvious manual for what replaces it. Here is what actually works, given what deployment does to the mechanics of a friendship.

Why the normal rules stop applying

An ordinary friendship runs on a background assumption you never have to think about: that the other person can reply more or less whenever they want to. Deployment removes that assumption completely. Internet access can be shared, rationed, or gone for stretches at a time. A block of days can pass with nothing, followed by three messages in a row at 3am your time, because that was the ten-minute window that opened up. None of this is a measure of how much you matter to them. It is a logistics problem wearing the costume of a silence problem, and it is worth saying plainly, because almost everyone reads it the second way at first.

The mistake is applying civilian math to it — counting days since the last reply, treating a gap as if it were data. Mostly it is not data. The gap is the infrastructure, not the message.

What keeping in touch needs to look like instead

Send things that do not need an answer

A message that requires a reply is a small debt. Send enough of those and, on the rare window your friend gets, they either have to spend it answering you specifically or feel bad skipping past you — both bad outcomes for someone with very little bandwidth to spare. Send instead what you would say out loud in the room even with no reply coming back: what happened at work, a photo of something ordinary, an update on the thing they would have asked about if they were still around. That kind of message can be read whenever, costs nothing to skip, and adds up over months into something that reads, later, as "you were still there the whole time."

Let the queue be the format, not a failure

Some deployments produce a rhythm where messages arrive in a batch after days of nothing — answering things out of order, sometimes things you had half forgotten you sent. This is not your friend being careless with you. It is the actual mechanics of when a connection opens. Reading it as hurt feelings, distance, or forgetting imports an expectation from an entirely different kind of relationship and applies it somewhere it was never going to fit.

The ordinary stuff matters more than the big stuff

The instinct is to save your messages for real news — the same instinct that quietly ends friendships during any long gap, deployment or not. A deployment is often long enough that "real news" happens rarely, so if that is the bar, the friendship goes mostly silent for months at a time. Deployed friends consistently say the mundane update is what they miss most: what you cooked, who you ran into, a show you started. It is the texture of an ordinary life continuing somewhere, which is a specific comfort, different from being told you are missed.

You do not have to wait for parity

There is a quiet fairness instinct that makes people match their friend's pace — if they can only reply once a month, sending more than that can feel like it is putting pressure on them. It is not. You can write far more often than they can answer, because the messages are not a request for their time; they are simply arriving, to be picked up whenever a window opens. The volume you send is not a tally either of you is keeping.

What to actually say

You do not need to ask whether they are safe. If something were seriously wrong, you would not be finding out through a missed reply — and asking repeatedly puts them in the position of managing your anxiety in whatever short window they have. You also do not need to ask where they are or what they are doing; a lot of it they may not be able to answer, and asking puts them in the position of declining, which is its own small unpleasant task on top of everything else. What is left, and it is plenty, is your own life. Tell them things. Ask about what they can actually talk about — how they are sleeping, what they are reading, what they are looking forward to when it is over. Ordinary curiosity, not operational curiosity.

The return is its own adjustment, not the finish line

There is a common assumption that once someone is back, the friendship should snap back too. It usually does not, not right away. Someone can be physically present and still be recalibrating to a version of normal life that kept moving without them — plans that got made, jokes that formed, a rhythm the group settled into while they were gone. The friendship needs a re-entry period as real as the deployment itself, and rushing it — expecting day one to feel like nothing happened — tends to produce exactly the awkwardness everyone was hoping to avoid. Slow, ordinary contact after the return does more than one big, enthusiastic catch-up attempt.

The honest caveat

None of this makes the distance easier, and no message schedule replaces having someone actually there. What it can do is keep the thread from going fully cold, so that when real contact is possible again, it starts from "still connected" rather than "starting over." That is a smaller promise than it sounds like, and it is the realistic one.