Would a response window be better than “online”?

I work remotely across time zones, and I’m increasingly suspicious of presence indicators. “Online,” “active,” and “last seen” look like coordination tools, but they quietly turn distributed work into an always-available performance. If I hide them, colleagues may not know when to expect me; if I leave them visible, every green dot can feel like an invitation—or evidence that I’m ignoring someone.

What if the default were a user-defined response window instead: “I’ll respond within one business day,” or “by tomorrow afternoon”? That might reduce interruption and anxiety, and make productivity judgments less dependent on who happens to be awake. But I can also imagine managers turning the window into another metric, with escalation when reality intervenes.

Would you trust response windows? What failure modes or better alternatives have you seen?

I like the distinction between reachable and responsive. A green dot answers the wrong question. I’d make the window visible only when someone is composing a request, not as a permanent profile badge. Otherwise the interface may still turn a human estimate into a social score.

The hard part is that “within one business day” needs a calendar, a time zone, and a definition of business day. Systems already struggle with basic presence accuracy. I’d rather see a message-level urgency field plus an expiry time than one global promise attached to a person.

The idea is plausible, but I’d be careful saying it reduces anxiety. Research supports that response expectations can improve coordination, while also finding that expectations can contribute to work outside normal hours. The design and governance matter more than the label.

In operations, a window only works if urgent work has a separate route. Otherwise people will mark everything urgent because they don’t trust the queue. I’d want team-level norms, not just each person choosing a number in isolation.

I would not trust a precise window from a tool that also records when I’m active. The privacy leak remains; it just gets a nicer name. Give me a coarse, optional commitment, and let me set it per channel or project.

There’s a product trap here: the humane feature becomes valuable precisely because companies want visibility. Once administrators can report on missed windows, the incentive changes. Maybe the commitment should be visible to collaborators but deliberately unavailable in management dashboards.

Presence is still useful for genuinely synchronous work. I’d keep it, but make it explicitly “available for chat,” not “working.” Then add a separate, approximate reply expectation. Replacing one overloaded signal with another probably won’t fix the norm underneath.

My alternative is gloriously low-tech: put “not urgent” in the subject and stop treating every message like a page. Tools can help, but teams still decide whether silence for six hours is normal or suspicious.