So now you have to store each email that includes important information in a second place, so that you remember to include it in their onboarding. Why not just post it to the intranet in a well-known location in the first place?
Ideally the information goes where itβs supposed to in your permanent knowledge repo. This could be a wiki, a website, etc.
The email is sent as a notification that the content has been added, updated or moved.
Email should ideally serve as a notification system and a lossy communication system where things you want to retain need to be backed up somewhere else.
The nice thing wth email is that being an open eco system there are a lot of integrations that are supported easily.
Right. But too often, as gregmac said, "people send mass company emails with, for example, new policy or forms attached, and don't post them elsewhere". Email should be used for notification and ephemeral communication, and not for information dissemination. In that way it's the same as chat.
