Skip to content

Commit f13d1d0

Browse files
(DOCS-5209) Add getting started with support (DataDog#17834)
* (DOCS-5209) Add getting started with support * (DOCS-5209) Rename folder * (DOCS-5209) Move chat hours note * (DOCS-5209) Modify overview * (DOCS-5209) Modify following up section * (DOCS-5209) Use table * (DOCS-5209) Incorporate editorial feedback * (DOCS-5209) Add link to help page * (DOCS-5209) Modify link * Apply suggestions from code review Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com> * (DOCS-5209) Update link * (DOCS-5209) Add to TOC * (DOCS-5209) Add video summary * Incorporate editorial feedback * (DOCS-5209) Remove video --------- Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
1 parent c307d61 commit f13d1d0

File tree

4 files changed

+79
-1
lines changed

4 files changed

+79
-1
lines changed

config/_default/menus/menus.en.yaml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -183,6 +183,10 @@ main:
183183
url: getting_started/learning_center/
184184
parent: getting_started
185185
weight: 21
186+
- name: Support
187+
url: getting_started/support/
188+
parent: getting_started
189+
weight: 22
186190
- name: Glossary
187191
url: glossary/
188192
pre: features
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Getting Started with Datadog Support
3+
kind: documentation
4+
further_reading:
5+
- link: "https://docs.datadoghq.com/agent/troubleshooting/"
6+
tag: "Documentation"
7+
text: "Agent Troubleshooting"
8+
---
9+
10+
## Overview
11+
12+
Datadog provides two primary channels for customers seeking support:
13+
- [Opening a support ticket][1].
14+
- Chatting live with Datadog Technical Support Engineers through a text chat.
15+
16+
While both options focus on providing quick and effective solutions, one platform may be better suited depending on the timing, nature, and urgency of the request.
17+
18+
This guide provides best practices for reaching out to the Support team, and guidelines for determining the support channel that's right for you.
19+
20+
## Prerequisites
21+
22+
For the most efficient resolution of an issue, be ready to provide any of the relevant information and resources listed below:
23+
24+
- Organization name (if you have access to [more than one][2])
25+
- [Datadog Site][3]
26+
- Links to any pages demonstrating the issue in your Datadog account
27+
- Screenshots or screen recordings of the behavior in question
28+
- Steps that can be taken to replicate the issue
29+
- If the issue is related to the functioning of the Datadog Agent, an [Agent flare][4]
30+
- Links to any documentation pages used
31+
32+
## Chat or support ticket?
33+
34+
Use the table below to determine whether to open a [support ticket][1] or reach out on chat. Chat is available any business day between the hours of 10:00 and 19:00 Eastern Time (ET).
35+
36+
| Support Ticket | Chat |
37+
| ------------------------------- | ----------- |
38+
| Urgent issues | Product configuration support
39+
| Call/Screenshare requests | Setup questions
40+
| Incidents and outages | Documentation clarification
41+
| Complex support troubleshooting across many configuration files, logs, or queries | Minor issues involving a specific configuration file, log, or query
42+
43+
If you're not sure which option is best, feel free to use either channel to connect with Datadog support. A support ticket is automatically created whenever a chat is closed, so the issue can continue to be investigated even if it's not resolved in chat.
44+
45+
## Reaching out on chat
46+
47+
To get started, click **Live Chat** on the left panel of your Datadog Account.
48+
49+
{{< img src="getting_started/chat/chat_button.png" alt="The chat button highlighted in Datadog" style="width:80%" >}}
50+
51+
When a new chat is opened, you are asked if you have a **technical** or **sales** question.
52+
- For technical questions, you are routed to the first available Technical Support Engineer. This is ideal for any questions you have about using or configuring Datadog.
53+
- For sales questions, you are routed to the first available member of the Datadog sales team, who can answer questions about billing and account management.
54+
55+
**Note**: For urgent issues, it's best to reach out through a Support Ticket, and indicate why your request is urgent. This ensures that Support leadership can route your case to an appropriate expert immediately.
56+
57+
### Best practices for technical questions
58+
59+
Ensure that you have as many of the relevant [prerequisites](#prerequisites) available as possible. The Datadog team member you connect with on chat does their best to collect information about the issue and resolve it. Not all issues can be resolved in a chat session. If a more detailed investigation is required, Datadog support focuses on collecting the information needed to conduct the investigation after the chat is over.
60+
61+
### Following up
62+
63+
When the chat closes, a support ticket is automatically created. If the issue was resolved on chat, the ticket can be closed.
64+
65+
If additional investigation is required, the ticket is routed to experts in the appropriate areas, with a full transfer of the details and context provided during the chat. Use the ticket for further communication with the Datadog Support team.
66+
67+
## Further reading
68+
69+
{{< partial name="whats-next/whats-next.html" >}}
70+
71+
[1]: https://help.datadoghq.com/hc/
72+
[2]: /account_management/org_switching/
73+
[3]: /getting_started/site/
74+
[4]: /agent/troubleshooting/send_a_flare/

i18n/en.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@
5252
},
5353

5454
"live_chat_support_sentence": {
55-
"other": "Chat with the Datadog Support Team Monday through Friday from 10:00 to 19:00 ET (Eastern Time) using in-app chat."
55+
"other": "Chat with the Datadog Support Team Monday through Friday from 10:00 to 19:00 ET (Eastern Time) using in-app chat. See <a href=\"https://docs-staging.datadoghq.com/bryce/add-chat-page/getting_started/support/#reaching-out-on-chat\" target=\"_blank\" rel=\"noopener\">Reaching out on chat</a> for best practices."
5656
},
5757

5858
"event_stream_support_sentence": {
40.2 KB
Loading

0 commit comments

Comments
 (0)