Support

One inbox. One person reading it.

There is no ticket system, no queue position and no first-line script. Write in plain English, say what happened, and the person who wrote the code answers. Usually inside one working day, rarely later than two.

An unmarked note card and envelope on a dark work surface

Choose the route.

Two addresses, each read by the person who can solve the problem.

Bot, website and everything else

Signals, tiers, Crypto Pay charges, broken pages, security, partnerships. If you are not sure which address to use, use this one.

support@nextscalp.com

Journal purchases and licences

Checkout problems, lost licence keys, downloads, update windows and refunds. Write from the address you bought with so the purchase can be matched.

journal@nextscalp.com

Before you send

A message with details in it gets fixed.

Start the subject line with one of these and the reply comes back faster: Bug report, Signal question, Licence key, Download, Refund, Security.

  1. 01

    What you did

    The page URL or the exact bot command, and the step you were on when it went wrong.

  2. 02

    What happened

    The error text verbatim, or a screenshot. For a signal question, the symbol and the time in UTC.

  3. 03

    Who you are

    Your Telegram username for the Bot, or the email you paid with for the Journal. Never send us a licence key you did not buy, an API key or a password.

NextScalp Bot

The bot already knows who you are.

For anything account-specific, an in-bot command is faster than an email because it answers with your own state instead of a guess.

  • /status - what the radar is watching right now, and whether it is running at all.
  • /settings - your filters and thresholds, the usual reason a signal you expected never arrived.
  • /premium - your tier, the current price and what the trial covers.
  • /refund_policy - the refund rules for a subscription charge, in the bot, in full.

Everything a command cannot solve, including a charge that did not land or a signal you think is wrong, goes to support@nextscalp.com. The Bot docs cover every command in detail.

NextScalp Journal

Self-hosted, so the awkward parts are the ones we can still help with.

Lost your licence key

The key appears once, on the confirmation page, and is never emailed. Write from the purchase address and we will look it up by hand.

Download or update window

Every version released inside your 12 months stays yours forever. Renew from the download page to reach newer builds, never for more than you originally paid.

Install and exchange keys

Read-only keys are enough, and the Journal never needs trading or withdrawal permission. Send the exact error and the step you were on.

Your database, your backups, your server: we hold no copy of your trades and cannot restore them. The page guide explains what every screen does; anything else goes to journal@nextscalp.com.

Security and press

Found a hole? Tell us before you tell the timeline.

Report vulnerabilities to support@nextscalp.com with enough detail to reproduce them, and give us a chance to ship a fix before disclosing publicly. Reports are answered, credited on request, and never met with a lawyer.

Partnerships, integrations, interviews and press questions go to the same address. Legal detail lives in the Terms and the Privacy Policy.

Answered before you ask. The common ones.

How fast will I get an answer?

Usually within one working day, and rarely later than two. NextScalp is built and supported by one person in Warsaw, so there is no 24/7 desk and no overnight shift. Every email is read by the person who wrote the code, which is slower than a call centre and considerably more useful.

I lost my Journal licence key. Can you resend it?

Yes, as a courtesy. The key is shown once on the confirmation page after payment and is never emailed, and there are no accounts and no password reset. Write to journal@nextscalp.com from the address you paid with and we will look the purchase up. If we cannot match the request to a purchase we may decline.

How do refunds work?

The Journal is 14 days, no questions asked: email journal@nextscalp.com within 14 days of your purchase and we refund it in full. A refund ends the licence, so stop using the software and delete your copies. Bot subscriptions are non-refundable except where consumer law requires it; ask in-bot with /refund_policy or write to support@nextscalp.com within 14 days of the charge.

The Bot has been quiet for hours. Is it broken?

Usually not. Silence is the product working as designed: the quality gate rejects most candidates and the Bot does not invent a setup to fill the feed. Run /status to see the live state and /settings to check your filters and watchlist. If /status is stale or the Bot does not answer at all, that is a real fault and worth an email.

The download page says my update window ended.

Every version released inside your 12-month window stays yours to run forever, so pick an earlier version from the list and it will download normally. To reach the newer builds, use the Renew updates button on the same page: renewal never costs more than your original purchase, and renewing early adds 12 months to the end of your current window.

Is there live chat, a phone number or a ticket system?

No. There is one address per product and a person reading it. No queue position, no bot triage, no ticket number to quote back at you.

Can you help me set up my exchange keys or my server?

Within reason, yes. The Journal is self-hosted, so the machine, the database and the backups are yours, but installation questions are fair game and we would rather fix a confusing step in the docs than answer it twice. Send the exact error text and the step you were on.

Do you give trading advice or review my trades over email?

No. Nothing from either product is financial advice and support does not extend to telling you what to trade. What the Journal will do is show you your own numbers, and the AI Coach inside it runs on your own key against your own data.