Step 1: Conversation initiated by the customer
Step 2: Notification is in Slack under Support Agent
Step 3: While under Support Agent select Home and see incoming tickets under Waiting for Help
Step 4: To assign the ticket to yourself select ‘…’ and then select Start.
Step 5: Identify if there is action for CS or not if it’s not clear, post in #customer-support-triage and brainstorm the best path.
If there is an action for CS, go to Step 6. There is an action for CS if the action is to:
- explain how a feature works in the product/how to do something in the product
- handle incident customer communication
- handle anything related to security for a customer without a TA
- handle a feature request for a customer without a TA
If there is no action for CS, go to back to step 4 select ‘…’ and then select Ignore then proceed to step 8. There is no action for CS if the action is to:
- handle anything related to security for a customer with a TA
- handle a feature request for a customer with a TA
- provide guidance on how to think about using Sourcegraph/drive adoption (ie more proactive in nature guidance)
- for employment verifications, we can reply and send the requestor to our Truework landing page where they can get what they need.
Step 6: Selecting View Thread will allow you to respond to the customer within the slack thread.
Step 7: Once done communicating with the customer in the Slack Thread, you will go back to support agent and from there you can put the thread on Hold with Notes or End Chat.
- Hold: Chat can be placed on hold while you are working on stuff in the background. When you are not interacting with the customer. To Resume communication you will go to Support Agent, Hold ‘…’, select Resume.
- End Chat: This is the same information that is filled out when closing a Zendesk ticket and is automatically transferred over to the Zendesk.
Step 8: If there is no action for CS, use the “no action for CS macro” in Zendesk and leave a reason why not then submit the ticket as solved.
It is important that we maintain consistent quality across our support tickets to ensure the collection of valuable data that can be shared with our Product and Engineering Teams.
The Zendesk ticket subject should be clear, concise, and structured with relevant keywords. This will enable both the product and engineering teams to quickly read and understand the issue or question.
It is crucial to thoughtfully select ticket tags for the quick and efficient categorization of the ticket’s content. Use relevant keywords and phrases as tags to aid in seamless search and filtering. This practice benefits both our product and engineering teams. To enhance overall ticket management, avoid using overly generic or ambiguous tags. Instead, maintain a consistent and organized tagging system that aligns with Sourcegraph’s specific support needs. Examples:
To ensure accurate information for both users and organizations, it’s important to verify and update these details. When you encounter
create next to the organization, please select the appropriate organization and then update the domain section in Zendesk. If the user is not associated with an organization, select the user’s name and update the organization section in Zendesk accordingly.
1. What should I do when I see a ticket originating from Slack with an internal user as the post owner?
The first step would be to open up the slack channel in which the Sourcegraph colleague posted, which is linked in the Zendesk ticket. In here we can see what happened in the conversation. This helps build context as to whether similar tickets correspond to this as well (may or may not necessitate a merge). Based on a slack channel, tickets can be created in Zendesk that are related to the challenge that the customer is facing. For this, it would be great to merge them and associate them to the customer. Also great to note that the ticket can be closed if the colleague in the thread doesn’t need our help.
If the other ticket is still open, merge the new ticket into it and alert our teammates who is responsible for the active ticket. This is easiest to see for tickets that originate from Slack. If you catch it for those that come in via email, that is great, but it can be harder to do.
No. Hopefully in the future, Zendesk will give us this feature; for now, we can link to the other ticket and be sure the requestor is correct.
We sometimes get all company updates or solicitation emails delivered to support mailbox. When you come across these, please go ahead and delete them.
If the email is clearly spam mark them as such (this can be done by clicking the three vertical dots on a ticket and selecting
Mark as Spam) which will delete the ticket and make sure we don’t get a similar email again.
If the email is around something that could be of interest to another team (examples could be a bill for a service that is about to expire or some security update) forward those to the appropriate team via Slack (or email group if its known). For employment verification emails see above for steps.
When SLA is close to expiring and the ticket is assigned, we ask SE to send a first response; otherwise, we collaborate as a team to provide a meaningful initial response to prevent SLA violations.
When we see post in the Customer Support channel, we need to make sure whether or not a ticket needs to be created for the SE’s following the same processes as listed above. There may be circumstances that involve additional action. Please view those here.
Sometimes custom scripts are developed by the CE or TA team, if the customer reaches out regarding any issues with running the script. It would be no action for the CS team.
When a customer replies to a solved Zendesk ticket a new ticket will be created. You will want to remove all the tags and triage following the same steps listed above.
If it’s from the Hubspot form and for marketing, engage them in the #marketing Slack channel and @ mention @marketing-operations.
If it’s from Hubspot, change the subject to “Sourcegraph help request”.
For the Hubspot form, we will need to email the person from our work Gmail account with a subject like “Sourcegraph inquiry” and email@example.com in cc and let them know a member of the team will help them. We do this so that we can ensure the customer gets the email since Zendesk could block it.
Simply navigate to the support agent app in Slack and at the top expand the title with the drop-down arrow. Choose the first option,
Add this app to a channel and either search out or type the channel you’d like to add the integration to. Here’s a quick video on how to do it. Please ping @CS-Leadership so they can complete the setup