The Call at the Worst Possible Time

The well-meaning person who contacts the Loop Keeper at the worst possible time is one of the most persistent and least addressed challenges of the role. Intrusion Timing is the pattern of well-intentioned but poorly-timed contact that generates additional coordination work for the Loop Keeper rather than reducing it, and managing it requires a structural approach rather than repeated attempts to ask people to call at better times.

You were in the middle of a conversation with the discharge coordinator when your phone buzzed. It was your uncle. He called at noon every day, without fail, to ask how your father was doing. You had asked him twice to text instead of calling. He was in his eighties and the calls were how he stayed connected. He did not mean any harm by it.

You let it go to voicemail. He called back. You excused yourself to answer it. It took four minutes. When you returned, the coordinator had been pulled away and you had to wait twenty minutes to resume. Your uncle had asked how your father was doing. You had told him things were progressing. The cost of that exchange was a twenty-minute delay in a coordination conversation already three attempts in.

What Intrusion Timing Actually Is

Intrusion Timing is about the structural mismatch between when people contact the Loop Keeper and when the Loop Keeper has capacity to receive that contact. The pattern is reinforced because it usually works, in the minimal sense that the Loop Keeper answers, the question gets answered, and the caller is satisfied. The cost is absorbed by the Loop Keeper in real time and is invisible to the caller.

Why 'Please Call at a Better Time' Does Not Solve It

The request to call at a better time fails for a structural reason: there is rarely a consistently better time that the caller can reliably identify and the Loop Keeper can guarantee will be available. The request also puts the caller in a position of constant uncertainty about whether this is a good time, which either produces continued interruptions or produces reluctance to call at all. Neither outcome is what the request was designed to produce. The more effective approach is not to manage the timing of incoming contact but to create an alternative channel that satisfies the caller's underlying need without requiring live contact.

What the Well-Meaning Caller Actually Needs

The person who calls daily to ask how the loved one is doing is usually not looking for a conversation. They are looking for reassurance. A regular update that answers these questions, delivered through a channel the caller can access without calling, satisfies the underlying need without requiring the Loop Keeper's real-time attention. The caller who knows that an update is posted every evening can wait for the update because they know it is coming. Most of the daily calls that interrupt Loop Keepers at the worst possible times are generated not by neediness but by the absence of a reliable alternative source of information.

How a Shared Update Channel Solves the Structural Problem

TwixTalk, The Family Loop is built around this function. The Loop Keeper posts one update, and every member of the Family Loop who would otherwise call to ask how things are going has the answer available without making the call. The person who was calling at noon every day does not stop caring about the loved one when they are redirected to TwixTalk. They start meeting that care in a different way, one that does not interrupt whatever the Loop Keeper is managing at noon.

Your uncle had asked how your father was doing. The discharge coordinator had been pulled away. It was four minutes of conversation that delayed a coordination process already three attempts in. He had not meant any harm. The cost was yours, invisible to him. The structural solution does not require him to change. It requires a channel that meets his need before he reaches for the phone.