# Raising Support Tickets

### Submit a Request

From any portal page, select **Submit a request** from the top bar:

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FCn8LUFs8jkrTRkDgDs8p%2Fimage.png?alt=media&#x26;token=e59769d2-dc29-49c4-b5bc-ff63d1c894f2" alt=""><figcaption></figcaption></figure>

This opens the ticket creation form.

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2F5C71S77KX6G13AODsuqJ%2Fimage.png?alt=media&#x26;token=4718f59d-e1e5-4ee2-833c-ca09d82aa779" alt="" width="563"><figcaption></figcaption></figure>

Please fill in the fields as follows:

#### Subject

Provide a short, specific title. Keep it searchable.

* `HashSphere issue` is too vague.
* `I’m having difficulty ...` is too long. Save it for the description.
* `Dashboard access from provided link` is just right.
* Prefer a pattern like: `[Mirror Node] 500s on /api/v1/transactions (prod)`

#### Description

Provide enough detail for fast triage and reproduction. Aim to include:

* Description and symptoms of the issue
* The HashSphere components or services that are affected
* How you detected the issue
* What you tried to do to fix the issue, and the results
* The steps to take to recreate the issue
* Any relevant configurations

Include *exact identifiers* when you have them:

* Environment (prod/non-prod) and region
* Timestamps with timezone
* Transaction ID, account ID, contract ID, or topic ID
* Endpoint/URL, request ID, and HTTP status code (if applicable)

{% hint style="warning" %}
Do not share private keys, seed phrases, or unredacted secrets. Redact tokens and passwords.
{% endhint %}

The text entry has comprehensive formatting options, including code lines and code blocks:

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FYgSdxqmmHPoEsLgJA55G%2Fimage.png?alt=media&#x26;token=17c70966-eb2b-415b-8643-9338ca3313e5" alt="" width="563"><figcaption></figcaption></figure>

#### Business Impact

The Business Impact drop-down is used to indicate the urgency of the support ticket.

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FztDk17CfqMienBFIyxmc%2Fimage.png?alt=media&#x26;token=a8714293-05cc-4030-8181-cd9de1d3b8f0" alt="" width="563"><figcaption></figcaption></figure>

Use the following guidance when selecting impact:

* **Critical** - Complete service outage or data corruption affecting production operations, causing immediate and severe business disruption with no available workaround.
* **High** - Significant degradation of service performance or functionality in production, substantially impacting business operations with limited or complex workarounds available.
* **Medium** - Partial loss of non-critical service functionality or moderate performance issues causing noticeable but manageable impact to business operations with reasonable workarounds available.
* **Low** - Minor issues or general inquiries about the managed service that have minimal to no impact on business operations or can be addressed through documentation.

#### HashSphere Services Impacted

Select the services impacted by the issue. If you do not see a service, select **Service Not Listed**.

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FNwIMmLIZkbzU63f4uCAv%2Fimage.png?alt=media&#x26;token=e2e4d0f5-7188-42e0-979f-68978b1a0f89" alt="" width="563"><figcaption></figcaption></figure>

#### Attachments

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FCvxzTN77iVe3y72FYiZl%2Fimage.png?alt=media&#x26;token=5eab7e32-7102-4faf-9c1e-80694b00ac6a" alt="" width="563"><figcaption></figcaption></figure>

Attach any files that help diagnose the issue, in particular:

* Log files
* Configuration files
* Crash stack dumps
* Application architecture diagrams

### Submitting Tickets

Select **Submit** to create the ticket. The ticket is routed to a support agent.

<figure><img src="https://2074645427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1lwtTuSxq9S9wuqIw74y%2Fuploads%2FUe1ipCuE5TFR4bKPxYA6%2Fimage.png?alt=media&#x26;token=bbd3eca5-44d7-4c87-8000-5ac74a41864c" alt="" width="158"><figcaption></figcaption></figure>

You will receive a confirmation email.

### Next steps

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><a href="raising-support-tickets"><mark style="color:$primary;"><strong>Managing Support Tickets</strong></mark></a></td><td><a href="managing-support-tickets">managing-support-tickets</a></td></tr><tr><td align="center"><a href="support-overview"><mark style="color:$primary;"><strong>Support Overview</strong></mark></a></td><td><a href="support-overview">support-overview</a></td></tr></tbody></table>
