The Myth of Being Available All the Time

The most common mistake with the myth of being available all the time is treating every incoming message as a promise to reply soon. That habit can cost you attention and leave others unsure about what you have actually agreed to do.

Imagine a clearly hypothetical situation: Mara helps a small community group organise a local book exchange. She often answers the group chat while cooking or settling in for the evening, so members begin sending questions her way and expecting a same-day reply. Nobody has asked her to be the group’s contact person, but a pattern starts to feel like a role.

The question is not whether Mara cares about the group. She does. The question is whether her repeated replies represent a commitment she chose or an expectation that grew around her behaviour.

Fast replies can quietly become an assumed role

At first, Mara answers because she happens to see the messages. She confirms which boxes are needed, suggests a place to leave them and helps settle small uncertainties. Each reply solves a real problem, but the group has no agreed rota or named coordinator.

Then messages arrive when Mara would rather leave her phone in another room. A question posted after dinner seems to require an answer before morning. If she does not respond, she catches herself composing a defence: she was cooking, tired or away from her phone.

That imagined defence matters. Mara acts as if she has broken a promise, although no one asked her to provide evening cover. Her past habit has become evidence in her own mind: because she answered before, she assumes others can require her to do it again.

Responsiveness can create that impression without anyone deliberately trying to impose it. A group sees a dependable reply and adapts around it, while missing that it came during a spare moment rather than from a standing offer. Start by identifying what was agreed, not by guessing what everyone expects.

Separate an actual commitment from an inferred one

Mara writes down the duties she explicitly accepted. She agreed to help choose the exchange’s venue and bring a table on the day. She did not agree to monitor the chat, answer every question or make decisions whenever another member is unsure.

An actual commitment has a recognisable shape: a task, someone it serves and an understanding of when it is due. An inferred commitment often has only a vague pressure attached to it, such as “they usually ask me” or “it would be awkward if I did not answer”.

For each request, Mara can check:

• If she clearly agreed to take responsibility, she should confirm the task and its due time; if not, she should treat it as unassigned.
• If the request is connected to a task she accepted, she should decide whether it falls within that task; if not, she should name the part she has not taken on.
• If a response time was discussed, she should follow that arrangement; if none was agreed, she should state when she can reply rather than assume immediate availability.
• If someone else needs to own the work while she is unavailable, she should identify that gap; if no owner is named, she can ask the group to assign one.
• If the request is time-sensitive, she should check whether she accepted responsibility for that kind of urgency; if not, she should direct it to the person coordinating the work.
• If she is unsure what her earlier agreement covered, she should clarify the scope before acting; if the task is outside it, she should leave it open for another volunteer.

These checks are not a way to avoid every inconvenient request. They help Mara respond to the request in front of her rather than obeying an unspoken rule she never chose. If a task is genuinely hers, she can honour it; if it is not, she can offer help within limits or leave it for the group to assign.

Say Mara receives a message asking who will collect spare books the following morning. She agreed to bring the table, not organise collections. When she next checks the chat, she replies, “I’m bringing the table, but I haven’t taken on collections. Could someone volunteer for that?” The group can then see that collection still needs an owner instead of assuming Mara has accepted it.

Make the boundary visible before silence is misread

Mara’s next move is to state what she can offer, rather than announcing a broad withdrawal. A useful boundary names the responsibility and gives people a clear alternative where possible. It does not require a long explanation about her evening, mood or private plans.

She might write: “I can help with the venue and bring the table. I don’t keep up with messages in the evening, so please put decisions in the shared document or ask the person coordinating that part.” This tells the group what she has accepted, what she has not and where unanswered questions can go.

A boundary is easier to follow when it describes an action that belongs to you. Mara can decide when she checks messages and whether she replies. She cannot control whether every member likes the arrangement, but she can stop presenting an informal habit as a promise.

Her actions also need to match her words. If she says she will check the group chat during lunch but continues answering late messages, the group receives conflicting information. She can mute the chat outside the time she has chosen to check it. Muting is not a punishment; it stops a casual channel from setting her schedule by default.

If the group needs a route for genuine urgency, it can name who is responsible for time-sensitive decisions. That is clearer than treating every notification as urgent. The arrangement should reflect the group’s actual responsibilities and make it clear whom to contact.

Expect the group to adjust to the new pattern

When Mara stops replying in the evening, one member may still send a follow-up. Another may ask whether she saw the message. That does not automatically mean the boundary has failed. People may need time to adjust when an informal pattern changes.

Mara can answer once, plainly: “I check the chat during the day. The collection question still needs a volunteer.” She does not need a fresh excuse each time. Repeating the limit calmly keeps the conversation on the task rather than turning it into a debate about whether she is helpful enough.

She should still attend to responsibilities she genuinely accepted. If she agreed to bring the table but can no longer do so, she should tell the group promptly so someone can make another plan. A limit around unclaimed work does not cancel chosen duties.

What is not worth the effort is writing a perfect announcement that anticipates every objection. Mara does not need a policy document for a small group chat. A concise message, a consistent habit and a visible owner for open tasks are more useful than elaborate wording.

How can you tell whether someone is relying on you?

Leave the agreement clearer than you found it

As the book exchange approaches, Mara replies during the day, completes the work she accepted and leaves other tasks visible for the group to assign. A member volunteers to coordinate collections. Questions still appear in the chat, but it no longer silently makes Mara their default destination.

This invented situation cannot promise that every group will respond smoothly. Its practical lesson is narrower: quick replies can look like an agreement even when no agreement was made. To avoid that confusion, name the work you have taken on, state the limits around your availability and make unclaimed tasks visible.

The myth of being available all the time weakens when you treat attention as yours to offer, rather than a resource others can claim by sending a message. Before answering the next request, pause long enough to identify whether it belongs to a real commitment or only to a habit. Then give the clearest response the situation needs.