What is the best way to sort out the mail of a department or team in the Yandex.Connect service?

Question

Yandex.Mail for domain

I want to transfer a small organization to Yandex.Connect (Yandex.Connect). Now she has two boxes, each of which has access to several employees at the same time. Suppose they are [email protected](administration) and [email protected](technical department).

The convenience is that one mailbox is one inbox. Each new letter is opened by any of the employees who have access to the mailbox. The letter is assigned the appropriate labels, the necessary actions related to it are performed and sent to the archive. The process is very transparent, because everyone can always see which letters are completely new, what has begun to be processed, what the answer is partially ready in the general drafts, and what has already been completed. The whole team works as a single organism, constantly striving to clean up the common inbox.

After moving to Yandex.Connet, the addresses of the two mailboxes will turn into something like [email protected](administration) and [email protected](technical department). For example, forwarding will be set up from old addresses, so that there will be no problems for customers due to the move.

It is not clear that: how now to jointly rake the common boxes? The help for Yandex.Connect suggests that each employee create an individual account of the type [email protected], and assign general addresses to departments or teams by setting up employee affiliation.

In itself, the presence of individual boxes is good. One person - one mailing address - one personal password. But what about the transparency of the process of parsing general letters? A message addressed to [email protected], simultaneously enters several mailboxes ( [email protected],[email protected]and [email protected]). Each person sees this letter separately, that is, does not know whether someone has already begun to parse it or not. The answer of one of the employees, most likely, will not be visible to the rest by default, if you use the "reply" button, and not "reply to all". There are no common tags, no common archive, and so on. A person, returning from vacation, will see hundreds of letters in his personal box, but will not know what has already been done by others, and what needs to be done by himself.

Obviously, instead of creating employees and departments, you can simply create these two "persons": [email protected]and [email protected]. However, this is more like a crutch than a correct solution. Groups of employees will again have a common account, as before the move, and this is not very good in terms of security, flexibility and convenience.

I seem to be missing something in understanding the process. How to organize everything correctly?

Answer 1

Hello, Alexander! I work for Yandex. I clarified with my colleagues - in Yandex.Connect there is only one tool for working with the general flow of letters - these are mailing boxes in which you cannot physically log in.
He told the development team about the ability to create a common box in which employees of the organization could work with letters at the same time. They wrote down the idea, they will think about how to implement it in the future :)

Answer 2

CRM
rest - your fantasies
, but you can also crutch

Answer 3

they didn’t ask about CRM.
if you only need to share access to incoming / sent - would put Thunderbird to employees in the field. why I'm talking about it - with the introduction of OAuth with GSuite, only the latest Outlook will work normally, some kind of 2010 or 2007 is no longer just friends.
to each user to register both boxes in the mail client. sending outgoing messages (with their personal signatures) - from the box that you set up for whom. sent - save in a folder on the server.
addition:
I did not immediately notice that we were talking about YandexConnect. those OAuth haven't done yet. so you can use the old MS Outlook for some time.