Sending Notices

1. You are here:
2. Handbook
3. Support Team Handbook
4. Support Workflows
5. Sending Notices

On this page

• Overview
• Blocked Accounts
• Mirror Abuse
• MailChimp Notices

Overview

From time to time we'll be asked by various teams within GitLab to send notices out to GitLab.com users and customers to inform them of various actions that we've either taken or will be taking on namespaces under their control.

We may also occasionally need to do this to inform certain users of a feature that will be deprecated that they're taking advantage of. This workflow details the various macros that we currently have in use to inform users of these specific situations and the steps that you, as a GitLab.com Support Engineer, should take to use them.

Blocked Accounts

** Macro:** Support::SaaS::Notices::Account Blocked

We may be asked by infrastructure either through an issue or Slack to notify a user or customer that their account has been temporarily blocked for some reason. In these cases, do the following:

1. Copy the link to the issue where it's mentioned that the user was blocked. If none exists, create one in internal-requests with the details.
2. Create a new ticket in Zendesk with the requestor as the primary email address of the user that is being blocked and apply the macro.
3. If the user has a subscription, review the organization notes and check for alternate contacts that should be added as a CC to the case.
4. If the organization has a TAM, reach out to the TAM on Slack to inform them of the blocked user, and add them as a CC on the ticket.
5. Supplement the response provided by the macro with the specific reasoning for the block and send it.
6. Add a note to the ticket that contains a link to the issue.
7. Add an admin note to the blocked account that links to the issue.

Mirror Abuse

Macros:

• GitLab.com::Notices::Mirror Abuse - Personal Namespace
• GitLab.com::Notices::Mirror Abuse - Group

Infrastructure may ask us to notify a particular user or group that the mirror of either gitlab-ce or gitlab-ee that they've recently created with the Trigger pipelines for mirror updates option enabled has caused extreme load on our shared runner fleet. In these cases, do the following:

1. Create a new ticket in Zendesk with the requestor set to one of the following:
   • For personal namespaces: set it to the primary email address of the user.
   • For groups: set it to the primary email address of any user in the group with Owner permissions.
     • Add each other Owner of the group as a CC to the ticket.
2. Apply the appropriate macro, either Mirror Abuse - Personal Namespace or Mirror Abuse - Group.
3. Replace any placeholder information in the response provided by the macro and send it.
4. Provide a link as an internal note in the ticket to the issue where this was brought to our attention.
5. Provide a link to the ticket in the issue where this was brought to our attention.
6. Be prepared to follow up with infrastructure if necessary should the user(s) respond back with any questions or comments.

MailChimp Notices

Outside of Zendesk we may be asked to be involved in the process of sending mass notices to users via MailChimp. In these cases, do the following:

1. Open an issue in the marketing/digital-marketing-programs issue tracker using the Email-Request-mpm template.
2. Fill the template out in its entirety.
3. Submit the issue and be ready to adjust the subject and/or body of the notice based on feedback.