> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streamnative.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Support

> How to contact StreamNative Support, set the right priority on a ticket, manage who in your organization can file tickets, and review past requests.

## Overview

When you need help from StreamNative for a question, bug report, or incident, you have two ways to reach the support team:

* **Support portal** **(recommended)**: [`https://support.streamnative.io`](https://support.streamnative.io)
* **Email**: `support@streamnative.io` ([Moderate](#severity-levels)-priority tickets only, see the warning below)

Both channels open a ticket with the same support team, but they are **not** equivalent. Use the portal whenever possible. It is the only channel where you can set the ticket priority, attach context up front, and track the request afterward.

<Warning title="Email tickets default to Moderate priority">
  Tickets created by email are automatically categorized at **[Moderate](#severity-levels)** priority and can't be escalated by replying to the email thread. If you need a higher priority (for example, a production outage), file the ticket through the [support portal](https://support.streamnative.io) and/or increase the priority on the existing ticket through the support portal.
</Warning>

<Note title="No active support plan?">
  The support portal is only available to organizations with a contracted support plan. If your organization doesn't have one, you won't be able to sign in to the portal. See [No active support plan](#no-active-support-plan) for how to reach support instead.
</Note>

## Choose your channel

| Channel                                           | When to use                                                                                                             | Priority                                                                                                                     |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Support portal](https://support.streamnative.io) | All technical issues, bugs, and errors. The support portal gives our engineers the visibility they need to investigate. | You choose at submission                                                                                                     |
| `support@streamnative.io`                         | When you can't reach the portal                                                                                         | Fixed at [Moderate](#severity-levels); best effort with no SLA if your organization doesn't have a contracted support plan   |
| [In-console chat widget](#other-ways-to-reach-us) | Quick questions from any organization                                                                                   | [Moderate](#severity-levels) by default; best effort with no SLA if your organization doesn't have a contracted support plan |

### No active support plan?

Access to the support portal requires a contracted support plan on your organization. If your organization doesn't have one, StreamNative doesn't create a portal account for you, and signing in shows **Portal unavailable**.

Without a contracted support plan, use `support@streamnative.io` or the chat widget in the [Cloud Console](/cloud/get-started/cloud-console) instead — both work regardless of plan status. These tickets are handled on a best-effort basis with no guaranteed response time, since there's no support plan attached to your organization.

If you need guaranteed response times, [contact StreamNative sales](https://www.streamnative.io/contact) to add a support plan.

## Before you need support

Set up portal access **before** you have an urgent issue. During an incident is the worst time to discover that no one on your team can log in.

### Self-register and verify access

1. Open [`https://support.streamnative.io`](https://support.streamnative.io) and create a profile using your **corporate email address**.
2. Follow the on-screen steps to set credentials and verify your email.
3. Sign in and confirm you can see the **Submit a request** option and the list of your previous tickets.

If sign-in fails or you don't see your organization's tickets after registering, email `support@streamnative.io` from your work address and ask to be added to your organization's support portal. Include your organization name as it appears in the [StreamNative Cloud Console](/cloud/get-started/cloud-console).

### Add teammates to the support portal

We recommend granting portal access to anyone in your organization who may need to file or follow up on tickets. Typical roles include on-call engineers, administrators, and operators. Members added to the portal can:

* File tickets at any priority, including high-severity incidents.
* See the full history of their organization's tickets.
* Be copied on tickets filed by other teammates.

To manage members, open the support portal, go to your organization's settings, and follow the steps in the [Pylon Customer Portal member management guide](https://docs.usepylon.com/pylon-docs/customer-portal/portal-experience#manage-members). The support portal is powered by Pylon.

## File a ticket

1. Sign in to [`https://support.streamnative.io`](https://support.streamnative.io).

2. Click **Submit a request** (or **New issue**).

3. Fill in the request form. The most important fields:

   * **Priority / severity**: Set this to reflect the real customer impact. See [Severity levels](#severity-levels).
   * **Summary**: One sentence describing the symptom. For example, "Producers failing with `TopicNotFound` on cluster `my-cluster` since 14:05 UTC."
   * **Description**: Include the [information listed below](#what-to-include).

4. Submit the ticket. You'll receive a confirmation email with the ticket ID.

### Severity levels

When you file through the portal, you choose the severity. Pick the level that matches the real impact on your workload, not what feels polite. The support team responds first to the highest-severity tickets.

| Severity             | Use when                                                                                                                                                                                                |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **SEV-1 (Fatal)**    | Core capability is completely unavailable, causing a material impact on your business or operations, or there is a security breach. No workaround is available.                                         |
| **SEV-2 (Critical)** | Critical capability is interrupted, degraded, or unusable, causing a severe impact on your business or operations. A workaround may be available.                                                       |
| **SEV-3 (Moderate)** | Non-critical capability is interrupted, degraded, or unusable, with a minor impact on your business or operations. Typically a workaround is available. This is the default for tickets filed by email. |
| **SEV-4 (Low)**      | Non-critical inquiries or issues that don't impact your business operations. Examples include general questions, documentation, feature requests, and billing or usage questions.                       |

The exact response-time commitments for each severity depend on your support plan. Refer to your contract or your StreamNative account representative for the response times that apply to your organization.

### What to include

A ticket that includes the right context up front avoids back-and-forth and gets resolved faster. For any ticket, include:

* **Description of the problem**: what you expected to happen versus what actually happened.
* **Business or user impact**: who is affected and how severely. This helps the team understand the urgency.
* **Organization name and ID**, visible in the [Cloud Console](/cloud/get-started/cloud-console) under **Organization**.
* **Cluster name**, and instance name if applicable.
* **Cloud provider and region** (for example, `aws-us-east-1`).
* **Timestamps in UTC** for when the issue started, and for any specific events you observed.
* **Steps to reproduce**, including the exact command, client configuration, or API call.
* **Supporting logs and screenshots** that show the failure.

#### For Cloud Console issues

Attach a **HAR file** so the support team can see the network requests made by your browser. See [Generate a HAR file](/cloud/references/generate-har-file).

#### For client-side issues

To track client-side issues, such as failures from Pulsar or Kafka client libraries in your application, include:

* **Exact timestamps in UTC** of the failed requests or operations.
* **The full client-side error message** and stack trace from your application logs.
* **The client library and version** you are using. For example, `pulsar-client-java 3.2.4`, `confluent-kafka-python 2.4.0`, or `librdkafka 2.4.0`.

## Track and follow up on tickets

After you submit a ticket, you can:

* **Review status**: Open [`https://support.streamnative.io`](https://support.streamnative.io) and go to **My requests** (or **Issues**) to see the status of every ticket filed by you or your organization.
* **Reply with new information**: Add a comment in the portal, or reply to the ticket notification email. Both update the same ticket.
* **Escalate**: If the severity of the issue increases (for example, a [Moderate](#severity-levels) question becomes a [Fatal](#severity-levels) outage), update the priority in the portal and add a comment explaining what changed. Do **not** open a new ticket for the same issue.
* **Reopen**: Closed tickets can be reopened from the portal by adding a new comment.

## Other ways to reach us

* **Shared Slack channel** (optional): If your organization has a shared Slack channel with StreamNative, use it for general questions, recommendations, and feature requests. Slack is **not** a substitute for the support portal for technical issues, bugs, or errors, because Slack threads don't give our engineers the same visibility as a ticket, and **there is no SLA** on Slack responses.
* **In-product chat**: The chat widget inside the [Cloud Console](/cloud/get-started/cloud-console) routes to the same support team and is convenient for quick questions while you are working in the console. Tickets opened through the chat widget are filed at **[Moderate](#severity-levels)** priority by default. If the issue is a [Fatal or Critical](#severity-levels) outage, open the ticket in the [support portal](https://support.streamnative.io) (or escalate the chat-created ticket from the portal) so the priority is set correctly.
* **Account representative**: For commercial questions, capacity planning, or anything that isn't a technical issue, contact your StreamNative account representative directly.