Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
add non-support emails page
Browse files Browse the repository at this point in the history
  • Loading branch information
gabtorre committed Mar 20, 2024
1 parent a9433d5 commit 9a1bbab
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 0 deletions.
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# Support Team Processes

- [Updating Known Issues Page](known-issues.md)
- [Handling Non-Support Emails](non-support-emails.md)
- [Case transitions](case-transitions.md)
- [Cloud Maintenance Window Process](cloud-maintenance-window.md)
- [Collaboration time](collaboration-time.md)
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Handling Non-Support Emails

Occasionally, non-support emails will be sent to [email protected], either cold outreach, employment verification, bills, marketing, or spam. We can forward these emails to the appropriate team and close the ticket.

**Marking Spam:**
If an email is spam, navigate to the ticket menu and select ‘Mark as spam’.

**Forwarding Emails:**
To forward an email, expand the menu on the message and click ‘Forward via email’. ZenDesk removes the original sender's email from the forward, so paste it into the message. If you need to access the support mailbox, use the credentials in the shared 1Password vault.

**Determining the Appropriate Recipient:**
Consult the relevant Slack channel to identify the correct recipient for the email:
#discuss-marketing: Cold outreach, marketing, media.
#ask-people-team: Employment verification, job applications, etc.
#discuss-finance: Bills, POs, or receipts.

If you are unsure where to direct an email or need help determining the appropriate action, request guidance in the #team-support-engineering channel.

0 comments on commit 9a1bbab

Please sign in to comment.