> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/enterprise-portal/support.md).

# Enterprise Support, Diagnostics & Tickets

Find out why a login fails in the RTKdata Enterprise Portal, use the guided runbooks, open support tickets and read your support agreement.

When a receiver will not connect, **Support > Diagnostics** usually finds the reason faster than a ticket. For everything else, **Support** keeps your whole conversation with RTKdata in one thread per ticket.

***

## Diagnostics

![The Diagnostics page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-5312ce97e4b186c561c8046bf35ff0e832363af4%2Fenterprise-diagnostics.png?alt=media)

### Step 1: check the login

Pick the login in **Check a License**. You get its signal before you start guessing: **Connected now**, **Last seen**, **Auth failures (30d)**, **GGA received (30d)** and **Parallel connections**. Three of those answer most cases on their own:

| Signal                                          | What it usually means                                                                  |
| ----------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Auth failures rising**                        | Wrong credentials on the receiver, or the portal login used instead of the NTRIP login |
| **GGA received: no**                            | The receiver is not sending its position, so no correction stream can be selected      |
| **Parallel connections above the data streams** | More receivers online than the login allows, disconnecting each other                  |

### Step 2: work through a runbook

**Troubleshooting Runbooks** holds a guided checklist per symptom:

| Runbook                             | Use it when                                                   |
| ----------------------------------- | ------------------------------------------------------------- |
| **Rover does not connect**          | No connection at all                                          |
| **Float only, no fix**              | Corrections arrive but never converge                         |
| **License expired?**                | You suspect the commercial side rather than the technical one |
| **Wrong mountpoint or coordinates** | The stream or the position looks wrong                        |
| **Credentials rejected (401)**      | The caster refuses the sign in                                |
| **Frequent disconnects**            | The session keeps dropping                                    |
| **GGA not received**                | The caster never sees the receiver's position                 |
| **Multiple devices, one license**   | Receivers knocking each other offline                         |

The field-facing versions of the same material are in [Common Connection Issues](https://docs.rtkdata.com/support/common-connection-issues.md) and [Troubleshooting & FAQ](https://docs.rtkdata.com/support/troubleshooting-and-faq.md), and the [Integration Hub](https://docs.rtkdata.com/integration-hub/integration-hub.md) has setup guides for most hardware. Both are good to pass on to your field teams.

### Step 3: escalate

Still stuck? **Escalate to RTKdata Support** on the same page asks for the login, the runbook you followed, the time window, what is happening and what you already tried, so support does not have to ask again. It becomes a ticket you can follow. **Report an issue** on a device or fleet page brings you here with that login preselected.

***

## Tickets

![The Support page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-61d0fedaf72a1b911eae396319bf217ff78081f6%2Fenterprise-support.png?alt=media)

**Open ticket** is the way to reach RTKdata support about anything.

![The Open a ticket dialog](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-087d7f17c4af7f605edec16fb5bc781f130bb56d%2Fenterprise-open-ticket.png?alt=media)

| Field                               | What to enter                                                     |
| ----------------------------------- | ----------------------------------------------------------------- |
| **Subject**                         | What it is about                                                  |
| **Category**                        | **Technical**, **Billing**, **Account** or **Other**              |
| **Severity** (optional)             | How urgent it is. Offered if your account has a support agreement |
| **Message**                         | What happens, since when, and what you tried                      |
| **License**, **Invoice** (optional) | The login or invoice it refers to                                 |

Answers arrive in the portal and by email, and a dot next to **Support** tells you something is unread.

![A ticket](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-9dec7eba6086714b1f5ac04d3d5179fbd82a6d8b%2Fenterprise-ticket-detail.png?alt=media)

The ticket page holds the conversation, with its details and history beside it. Reply below it, screenshots are welcome. **Waiting on you** in the status means RTKdata needs something from you.

**Close ticket** ends it once you need no more help. A ticket RTKdata marked as resolved closes by itself after 7 days.

Everyone on your team with access to Support sees all of your account's tickets, so a colleague can take over.

***

## Your support agreement

If RTKdata agreed response times with your company, **Your support agreement** at the top of the Support page shows them, with the coverage hours and a first response and resolution time per severity. A ticket with a severity shows the time that applies to it.

The times in the screenshot above are an example. Yours are the ones in your own agreement.

***

## Other requests

* **A question about one invoice:** use **Contact support** on that invoice, see [Billing](https://docs.rtkdata.com/enterprise-portal/billing.md#an-individual-invoice).
* **A bug in the portal:** use **Help > Report a bug**.
* **Base stations:** talk to your RTKdata contact.

***

## Next

* [Usage & Live Map](https://docs.rtkdata.com/enterprise-portal/usage-and-live-map.md)
* [Devices](https://docs.rtkdata.com/enterprise-portal/devices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rtkdata.com/enterprise-portal/support.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
