Skip to content

Process for handling [email protected] mailbox #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cassgvp opened this issue Jul 17, 2023 · 2 comments
Open

Process for handling [email protected] mailbox #244

cassgvp opened this issue Jul 17, 2023 · 2 comments

Comments

@cassgvp
Copy link
Collaborator

cassgvp commented Jul 17, 2023

Summary Sentence

Emails sent to [email protected] are received by the whole team, but there is currently no documented process for ensuring they are responded to effectively.

What needs to be done?

Decide a process for ensuring that emails received at [email protected] are responded to and actioned. Document and make the process explicit.

Suggested process:

Anyone feeling informed enough to respond to the email should reply. For transparency and to let others know the enquiry is being handled, please cc [email protected] in your reply.

[Confirm this] Where there is doubt or no clear ideal respondent, please start a thread on #tps-cms-only to have an internal conversation.

[Confirm this] This process to be added to induction information.

Who can help?

@malvikasharan @EKaroune ?


Update after the issue was opened

[Add details]

@malvikasharan
Copy link
Collaborator

This looks perfect Cass.

Is there anything else from the induction missing? I think the knowledge centralisation document (that is accessible to the team) is not mentioned too. I will do a review there and add those points to an issue. Thank you for raising these.

@cassgvp
Copy link
Collaborator Author

cassgvp commented Jul 17, 2023

I'm hoping to collate the induction material for #225.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants