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

# Support

Stuck on a tool, hit an error you can't place, or seeing a transaction behave in a way you didn't expect? Email us at <info@j.tools> and we'll help you sort it out.

We're a small team. We read every message, but we can't promise a same-hour reply. The more detail you give us up front, the faster we reach a real answer.

{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% endhint %}

## How to reach us

The fastest path is email: <info@j.tools>. One clear message with the details below beats five short ones.

You can also find us on our official channels:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>X (Twitter)</strong></td><td>Launches and updates.</td><td><a href="https://x.com/jtools_official">@jtools_official</a></td></tr><tr><td><strong>Telegram</strong></td><td>Chat and support.</td><td><a href="https://t.me/JTools_Official">JTools_Official</a></td></tr></tbody></table>

For the full list of official links, see the [Official links](/help-and-security/links.md) page.

{% hint style="info" %}
Before you write in, take a quick look at the [Error codes reference](/reference/error-codes.md). Many issues have a documented cause and fix there, and you may not need to wait on us at all.
{% endhint %}

## What to include

A good report lets us reproduce or trace your problem without a long back-and-forth. Try to cover these:

{% stepper %}
{% step %}

### What you were doing

The tool you were using and the step you were on when it went wrong. "Creating a pool on Create LP, right after I clicked Confirm" tells us far more than "it broke".
{% endstep %}

{% step %}

### The error message or transaction signature

Copy the exact error text if you saw one. If a transaction was sent, the signature lets us look up what happened on-chain. You'll find it in your wallet's activity or on the result screen.
{% endstep %}

{% step %}

### Your browser and wallet

For example, "Chrome on Windows, Phantom" or "Brave on Mac, Solflare". A surprising number of issues come down to a specific browser and wallet combination, so this saves real time.
{% endstep %}
{% endstepper %}

Here's the same checklist at a glance:

| Include               | Example                                                |
| --------------------- | ------------------------------------------------------ |
| What you were doing   | "Burning LP on Liquidity Lock, right after connecting" |
| Tool name             | Create LP, Multi Sender, Token Creator                 |
| Error message         | The exact text shown on screen                         |
| Transaction signature | `5xPq...` from your wallet or the result screen        |
| Browser               | Chrome, Brave, Firefox, Edge                           |
| Wallet                | Phantom, Solflare, Backpack                            |

## What to never share

{% hint style="danger" %}
**We will never ask for your private key or seed phrase, and you should never send it to anyone.** Not to us, not to "support" in a Telegram DM, not into a form. J Tools is non-custodial: every action is signed in your own wallet, and that's the only place your key ever needs to live. Anyone asking for it is trying to drain you.
{% endhint %}

A transaction signature is safe to share. It's a public reference to something already on-chain, and it can't move your funds. Your wallet address is safe too. The private key and the seed phrase are the secrets, and they stay with you.

## Quick triage

A lot of the common ones you can clear yourself in under a minute.

<details>

<summary>My wallet won't connect</summary>

Refresh the page, make sure the wallet extension is unlocked, then try again. If it still won't connect, try a different browser. See [Connect your wallet](/getting-started/quick-start.md) for the full walkthrough.

</details>

<details>

<summary>My transaction failed or expired</summary>

Solana blockhashes age out when the network is busy. Most of the time, submitting again works. If it keeps failing, check that you have enough SOL for both the network fee and the platform fee, then send us the transaction signature.

</details>

<details>

<summary>My wallet showed a warning before I signed</summary>

For some multi-step tools, that caution banner is expected. We explain why on the [Phantom warnings](/help-and-security/phantom-warnings.md) page and on the relevant tool pages. If anything looks off beyond the usual banner, stop and email us before signing.

</details>

<details>

<summary>I have a question about commissions or a withdrawal</summary>

Those live in the affiliate section. Withdrawal statuses, balances, and tier rates are all explained in [How the affiliate program works](/affiliate/overview.md).

</details>

## Where else to look

{% content-ref url="/pages/Rodo9tl731yuAyBheYkO" %}
[Error codes](/reference/error-codes.md)
{% endcontent-ref %}

{% content-ref url="/pages/HfYyIOgWatge2th4v1Sb" %}
[Fee schedule](/reference/fee-schedule.md)
{% endcontent-ref %}

{% content-ref url="/pages/l7qpz78KpqXAZwvtDo7t" %}
[Quick start](/getting-started/quick-start.md)
{% endcontent-ref %}


---

# 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://docs.j.tools/help-and-security/support.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.