Skip to content

Commit dbde44b

Browse files
jcirinosclwyjcirinosclwy
authored
update-content.mdx
1 parent 354226a commit dbde44b

File tree

1 file changed

+36
-28
lines changed

1 file changed

+36
-28
lines changed

‎pages/account/how-to/open-a-support-ticket.mdx‎

Lines changed: 36 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: How to open and write a support ticket
3-
description: Learn how to open and write an effective support ticket
4-
tags: support help ticket support-ticket assistance
3+
description: Learn how to open and write an effective support ticket.
4+
tags: support help ticket assistance
55
dates:
6-
validation: 2025-07-29
6+
validation: 2025-10-23
77
posted: 2021-06-22
88
---
99
import Requirements from '@macros/iam/requirements.mdx'
@@ -15,59 +15,67 @@ Scaleway provides 24/7 basic technical support by ticket for free. You can conta
1515

1616
- A Scaleway account logged into the [console](https://console.scaleway.com)
1717

18-
## Opening a support ticket
18+
## How to open a support ticket
1919

20-
1. Click the question mark icon, or **Help** icon on the top menu. The [Help center](https://console.scaleway.com/support/tickets) displays.
21-
2. Click **Open a support ticket** under **Contact us**.
22-
3. Fill in the required information:
20+
1. Click the question mark icon on the Scaleway console header menu. The [Help Center](https://console.scaleway.com/support) displays.
21+
2. Click **Open a support ticket**, under **Contact us**.
22+
3. Fill out the required fields. [See what information to include to obtain faster responses]
23+
4. Attach any supporting files that may help our team identify and solve your issue.
24+
5. Click **Submit ticket**.
2325

24-
- **Selected product**: choose the product related to your issue from the available options, such as Instances, GPU, or Elastic Metal.
26+
## Required information
2527

26-
- **Related resource**: specify the exact resource affected by the issue, such as a specific Instance or volume.
28+
The information below must be included in your support ticket, allowing our team to identify the issues you are facing.
2729

28-
- **Severity**: select the severity level based on the impact of the issue (see table below).
30+
- **Product**: choose the product related to your issue from the available options, such as Instances and Elastic Metal. If your ticket is a general inquiry and does not concern a product, select **Other**.
2931

30-
| **Severity** | **Description** | **Example** |
32+
- **Related resource**: choose the affected resource, such as a specific Instance or volume.
33+
34+
- **Priority**: select the impact the issue has on your infrastructure. Refer to the table below to understand priority levels.
35+
36+
37+
| **Priority** | **Description** | **Example** |
3138
|--------------|------------------------------|-----------------------------------------------------------------------------------------|
3239
| **P1** | Service down | Your infrastructure is not working in production, and no workaround is available. |
3340
| **P2** | Partial service outage | Your infrastructure is partly functional but facing critical errors with no workaround. |
3441
| **P3** | Severely degraded service | The service is slow or highly degraded, but a temporary workaround is possible. |
35-
| **P4** | Minor incidents | The service is running with minor issues that do not impact your activity. |
36-
| **P5** | General question or request | You have a question or need information, but there is no technical issue. |
42+
| **P4** | Minor incidents | The service is running with minor issues that do not impact your activity. |
43+
| **P5** | General question or request | You have a question or need information, but there is no technical issue. |
44+
3745

38-
## Writing an effective subject and description
46+
- **Subject**: write a short and clear title that summarizes the issue, e.g., _"Instance does not start after an update"_ or _"API call returns 500 error for all requests"_.
3947

40-
Providing a clear subject and description will help us resolve your issue faster.
48+
- **Description**: include a detailed description to help us resolve the issue.
4149

42-
- **Subject**: write a short and clear title that summarizes the issue (e.g., "Instance not starting after configuration update", "API call returns 500 error for all requests").
50+
## What to include in a ticket for a quick resolution
4351

44-
- **Description**: write a detailed description to help us resolve the issue faster. Here are a few tips on how to write a ticket description:
52+
Providing clear and detailed information about the problems you are facing helps us quickly identify their causes. Follow our recommendations below to avoid unnecessary exchanges and reduce your ticket resolution time.
4553

4654
### Clearly describe the issue
4755
- **Context:** explain when and where the problem occurs.
48-
Example: “The issue occurs when attempting to start an Instance after applying a configuration update in the Scaleway console.”
56+
E.g., _“I get an error when trying to start an Instance after applying a configuration update in the Scaleway console”._
4957

50-
- **Expected behavior:** explain what you expected to happen.
51-
Example: “The Instance should start within 2 minutes without errors.”
58+
- **Expected behavior:** explain what was expected to happen.
59+
E.g., _“The Instance should start within 2 minutes without errors”._
5260

5361
- **Actual behavior:** describe what is happening instead.
54-
Example: “The Instance remains in "Starting" status for over 10 minutes and then switches to "Error".
62+
E.g., _“The Instance was stuck in a 'Starting' status for over 10 minutes, then switched to an 'Error' status and became unavailable"._
5563

5664
### Include relevant technical details
5765

58-
- **Environment details:** mention your operating system, tools, or SDKs (e.g., “Ubuntu 20.04, Scaleway API v2, Python SDK.”)
66+
- **Environment information:** mention your operating system, tools, or SDKs, e.g., “Ubuntu 20.04, Scaleway API v2, Python SDK".
5967

60-
- **Logs or error messages:** include any logs, request/response payloads, or error codes (e.g., “API call GET /instances returns 500 Internal Server Error.”)
68+
- **Logs or error messages:** include any logs, request/response payloads, or error codes, e.g., “API call GET /instances returns 500 Internal Server Error”.
6169

62-
### Add supporting files
70+
### Attach supporting files
6371

64-
You can drop or browse to attach files that might be relevant to understanding your issue. You can include screenshots, PDFs, and text files.
72+
If possible, upload files that may help us understand your issue. You can include screenshots, PDFs, and text files.
6573
<Message type="important">
6674
Keep in mind that:
6775
- You can attach up to 4 files per message and 10 files per ticket.
6876
- The size of each file cannot exceed 10 MB
6977
- The following file formats are supported: `jpeg`, `jpg`, `png`, `pdf`, and `txt`.
70-
- The uploaded data is exclusively intended to provide you with support in the use of Scaleway services. Do not transmit any inappropriate, or irrelevant sensitive data.
78+
- The uploaded data is exclusively intended to provide you with support in the use of Scaleway services. Do not transmit inappropriate or irrelevant sensitive data.
7179
</Message>
7280

7381
**Examples:**
@@ -76,5 +84,5 @@ You can drop or browse to attach files that might be relevant to understanding y
7684
- Logs
7785

7886
<Message type="important">
79-
If you have lost access to the Scaleway console and want to create a ticket, you must first [follow this procedure](/account/how-to/use-2fa/#how-to-regain-access-to-your-account) to regain access to your account.
80-
</Message>
87+
If you have lost access to the Scaleway console and want to create a ticket, you must first [complete the account recovery procedure](/account/how-to/use-2fa/#how-to-regain-access-to-your-account).
88+
</Message>

0 commit comments

Comments
 (0)