Account and support

Send a useful support request

A clear report helps support distinguish an account issue, a settings difference, an update delay, and a reproducible bug. Keep one issue in one conversation and add the relevant evidence.

Before you contact support

CheckTry the relevant checksUse the troubleshooting section for the symptom you see.Open the checklist
CaptureCapture the contextSave the selected settings, data time, and exact error or unexpected behavior.Use the template
ReportSend one focused reportExplain what you tried and what changed. Continue in the same thread.Choose a channel

A support-request template

Technical issue

Tool and view: Page URL, TradingView indicator name, Discord command, API route, or MCP tool.
Selection: Symbol, exact expiration, aggregation mode, and any relevant settings or Manual Override.
Time: When it happened, the timezone, and the displayed data snapshot time.
Expected / actual: What you expected, what happened instead, and the exact error text.
Reproduction: The shortest sequence of actions that produces the issue, plus the browser or client version.
Checks completed: What you tried and the result, with a relevant redacted screenshot if useful.

For an account or billing issue

Use private support. Identify the account email or TradingView username, state the change or problem, and include the relevant invoice reference, date, amount, or confirmation. Only include the details needed to locate the issue.

Keep secrets out of the report

Send the context, not the credentials.

Remove email login codes, bearer tokens, authorization headers, full card details, and unrelated personal information. Public Discord screenshots should also hide account emails and identifiers.

For an API example, redact credentials while retaining the route, parameters needed to reproduce the issue, response status, error code, and request ID. Do not upload an unreviewed environment file or complete browser session export.

Keep the follow-up together

Add new evidence to the original conversation instead of opening duplicate requests.
If the issue resolves, explain what worked.
For a trial or renewal, use the billing portal’s recorded cancellation and confirmation rather than assuming an unanswered message changed the subscription.
Ask support to correct account details rather than creating replacement accounts or repeat trials.

Choose a channel on Where to ask, or review Troubleshooting and the FAQ.

TanukiTrade documentation. Levels are context, not a recommendation. tanukitrade.com