Who Responds? Clarifying Email Responsibility in Your Team

When emails to team addresses are answered twice or not at all, it rarely comes down to the people involved. The real issue is a missing agreement: For each mailbox, it must be clear who is responsible for handling it and who is allowed to see it. These two rules – responsibility and visibility – solve most of the problem.

Responsibility diffusion: the real issue

The phenomenon is well known: the more people who see a task, the less any individual feels responsible for it. In a team mailbox, this means: multiple people have read the customer inquiry – and each thought someone else would take care of it. Conversely, the same lack of clarity leads to duplicate work: colleagues answer the same email, the customer gets different information.

Both have the same root cause: Being able to see was established (everyone has the password), but being responsible was not.

Two separate decisions

The key is to separate two questions that in practice are constantly mixed together:

1. Who is responsible? Exactly one person per mailbox (plus a backup). They don’t necessarily answer everything themselves – but they review, assign, hand off, and ensure nothing falls through the cracks. All open items come together with them.
2. Who gets to see it? This is a conscious decision per mailbox: info@ usually tolerates organization-wide visibility – that helps with coverage and context. Mailboxes like careers@ or accounting@ belong in a tight circle.

With webRichtung inbox, you open the door to email and messaging work in an enterprise context. You consciously define the organizational rules for responsibility and visibility in your team, rather than deriving them from shared passwords.

Handoff instead of silent forwarding

Responsibility only works with clean handoffs. Silent forwarding – pushing an email to a colleague and hoping – is the most common breaking point: the colleague treats it as information, not a task. Better is explicit handoff with three elements:

• Recipient: “Can you take this?” to a specific person, not a distribution list
• Expectation: What should happen – answer, review, report back?
• Timeline: By when? Even a rough “this week” is better than nothing.

Only when the colleague has accepted does responsibility transfer – until then it stays with the mailbox owner.

Rules that work

1. One email, one owner: Once someone takes on a request, it’s theirs – including follow-up questions and follow-up.
2. Define response time: The team agrees on a response time for initial replies. An honest interim message counts too.
3. Done means done: Completed items are marked as such so no one processes them again.
4. Plan coverage before vacation: Responsibility that goes on vacation is the second most common reason for requests to slip through the cracks.

The result

When responsibility and visibility are explicitly defined per mailbox, the question “Did someone actually reply to that?” comes up less often. How to lay the organizational foundation for this is described in the article Organizing a Shared Mailbox Properly in Your Team.