> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/troubleshooting/getting-help.md).

# Getting Help

### Overview

Use this page when work is blocked.

The goal is fast triage and fast escalation with complete context.

### Key Concepts

* **Symptom**: observable failure, such as sign-in failure or slow load
* **Reproduction**: steps that reliably recreate the issue
* **Scope**: Account, Organization, and Project context for the issue
* **Evidence**: error text, timestamps, and screenshots (redacted)

### How It’s Used

Start with self-serve triage for common symptoms.

Escalate to support when reproduction is consistent and evidence is captured.

### Benefits

* Faster resolution through consistent triage
* Less back-and-forth with support
* Better auditability of what occurred and when

### Setup Steps

{% stepper %}
{% step %}

### Search first

Start with search. It is usually faster than browsing.

* [Using Global Search](/getting-started/using-global-search.md)
  {% endstep %}

{% step %}

### Troubleshoot by symptom

Pick the closest match:

* Sign-in and access: [Login Problems](/troubleshooting/login-problems.md)
* Slow pages and timeouts: [Performance Optimization](/troubleshooting/performance-optimization.md)
* Unexpected behavior: [Common Issues](/troubleshooting/common-issues.md)
* Specific errors: [Error Messages](/troubleshooting/error-messages.md)
* Network problems: [Connectivity Issues](/troubleshooting/connectivity-issues.md)
* Data problems: [Data Quality Issues](/troubleshooting/data-quality-issues.md)
  {% endstep %}

{% step %}

### Escalate with good details

Contact support when self-serve steps do not resolve the issue.

* [Contact Support](/resources/contact-support.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

Include the minimum evidence set for support triage:

* Intent: what action was attempted
* Scope: Account + Organization + Project + page
* Reproduction: shortest sequence that reproduces the issue
* Exact error text (copy/paste)
* Timestamp with time zone
* Screenshot or recording (redact sensitive data)
* Browser + operating system

{% hint style="warning" %}
Do not share passwords, API tokens, or client or customer PII.
{% endhint %}

Service status:

If multiple people are affected, check status first:

* <https://status.transform.ai/>

### Summary

The fastest route is search → symptom triage → escalation with complete evidence.

Related:

* [Browser Compatibility](/getting-started/browser-compatibility.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/troubleshooting/getting-help.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.