---
title: "Who answers? Clarifying email responsibility within the team"
description: "Answered twice or not at all: why team mailboxes fail due to unclear responsibility and how to cleanly settle accountability and visibility."
type: "wissen"
product: "mail"
slug: "team-email-responsibility"
source_language: "de"
target_languages: ["de", "en", "es", "pl", "tr"]
published: "2026-06-10"
status: "publish"
faq_json: [{"q":"Why do emails in team mailboxes remain unanswered?","a":"Because of diffusion of responsibility: when several people see an email, everyone relies on someone else answering. The problem isn't laziness, but a lack of arrangement about who is responsible."}, {"q":"How do you prevent duplicate replies from a shared mailbox?","a":"Through a shared working environment instead of five private copies of the same mailbox – and through the rule that one person per mailbox is responsible for handling it and hands over inquiries explicitly."}, {"q":"What does responsibility for a mailbox mean concretely?","a":"The responsible person ensures that incoming emails are reviewed, assigned, and handled. They don't have to answer everything themselves – but with them, everything that's open comes together."}, {"q":"Should everyone in the team see all mailboxes?","a":"No, visibility should be granted deliberately for each mailbox: info@ usually organization-wide, sensitive mailboxes like bewerbung@ only for a narrow circle. Visibility and answering responsibility are separate arrangements."}, {"q":"How does webRichtung mail support clarifying responsibility?","a":"The organization's mailboxes are connected centrally in core; for each mailbox, responsible persons and visibility are set – organization-wide or privately/directly shared. The team works from a common state instead of with shared passwords."}]
language: "en"
source_id: "wissen/team-email-verantwortung"
source_hash: "f1587dd3481673ba033adb311db0855b3fea3febf254aca0fd70b2c6cc8c2dc4"
---

When emails to team addresses get answered twice or not at all, it's rarely down to the people, but rather to a missing arrangement: for each mailbox, it must be clear who is responsible for handling it and who is allowed to read along. These two arrangements – responsibility and visibility – solve most of the problem.

## Diffusion of responsibility: the actual problem

The phenomenon is well known: the more people see a task, the less the individual feels responsible. In the team mailbox, this means concretely: four people read Tuesday's customer inquiry – and each thought someone else would take care of it. Conversely, the same ambiguity leads to duplicated work: two colleagues answer the same email in parallel, and the customer receives two different answers.

Both have the same root: **being able to see** was arranged (everyone has the password), **being responsible** was not.

## Two separate arrangements

The key is to keep apart two questions that are constantly mixed up in practice:

1. **Who is responsible?** Exactly one person per mailbox (plus a deputy). They don't necessarily answer everything themselves – but they review, assign, hand over, and ensure that nothing is left lying around. With them, everything that's open comes together.
2. **Who is allowed to see it?** This is a deliberate decision per mailbox: info@ usually tolerates organization-wide visibility – this helps with cover and context. Mailboxes like bewerbung@ or buchhaltung@ belong to a narrow circle.

In [webRichtung mail](https://www.webrichtung.de/module/mail/), these two arrangements are exactly the core of the model: your organization's mailboxes are connected centrally in core under Administration → Integrations, and for each mailbox you set **responsible persons** and **visibility** – organization-wide or privately/directly shared. Instead of five private copies with a shared password, the team works from a common state.

## Handover instead of silent forwarding

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

- **Recipient:** "Can you take this on?" to a specific person, not to a distribution list
- **Expectation:** What should happen – answer, check, report back?
- **Deadline:** By when? Even a rough "this week" is better than nothing.

Only once the colleague has taken it on has responsibility moved – until then it lies with the person responsible for the mailbox.

## Ground rules that have proven themselves

1. **One email, one owner:** As soon as someone takes on an inquiry, it belongs to them – including follow-up questions and chasing it up.
2. **Define response time:** The team agrees on a response time for initial replies. Even an honest interim message counts.
3. **Done means done:** Processed cases are made recognizable as such so that no one touches what's already finished again.
4. **Arrange cover before vacation:** Responsibility that goes on vacation is the second most common cause of inquiries left lying around.

## The effect

Teams that have explicitly settled responsibility and visibility per mailbox report an unspectacular but noticeable effect: the question "Has anyone actually answered that?" disappears from everyday life. How to lay the organizational foundation for this is described in the article [Organizing a shared mailbox in the team correctly](/en/wissen/gemeinsames-postfach-team.html).