📡 Support SOP (Standard Operating Procedure) — CryptoSlug Clan Field Manual

When the bot stalls, every minute matters. The goal is clear communication, visible trace, and disciplined execution between official support and the Clan.

• Open a ticket in the right channel (official and/or CryptoSlug).
• Share those ticket links in the Clan channels.
• Close the loop with evidence: logs, steps, and final outcome.

🏢 Official Gunbot & CryptoSlug Support — Freshdesk/email (support@gunbot.freshdesk.com) — licenses, activation/transfer, updates, core technical errors.

🛡️ CryptoSlug & Gunbot Community — Discord/Telegram for setup/execution, presets, log reading, best practices, and risk management.

For non-technical matters (strategy, risk, daily ops), start with the Community — hands-on practice speeds up progress.

• Official (helpdesk/email): open with a surgical subject + objective description — contact: support@gunbot.freshdesk.com.
• CryptoSlug Support (GitHub): open with a clear subject + objective description.
• Community (Clan): open a topic on Discord/Telegram and paste the links to the tickets (official/GitHub).

• Gunbot version + OS (Win/Linux/Mac)
• Exchange, pair(s), and timeframe
• Problem description + repro steps (1-2-3)
• Short logs (error snippets) and/or screenshots
• Recent changes (update, API keys, strategy, preset)
• What you already tried (system clock sync, API perms, alt preset)
• Approximate timestamp of the error

• System clock synchronized
• API permissions correct (trade on; withdraw off if applicable)
• Coherent parameters: min order, step, TP
• Quick test with another pair/TF or a clean preset
• Run through FAQ/troubleshooting for common errors

Surgical subject: [Binance] “Invalid API timestamp” after 29.5 update — Win11

One-line context (expected vs. observed) · Numbered steps · “Lean” logs (3–10 lines) · Environment (version/OS/exchange/pair/TF/preset)

Template — official ticket (helpdesk/email)

Subject: [EXCHANGE] [ERROR SUMMARY] — [OS] — [GUNBOT VERSION]

Context (1 line): Expected [X], got [Y].
Steps: 1) … 2) … 3) …

Environment:
- Gunbot vX.Y.Z | OS: Windows 11
- Exchange: Binance | Pair/TF: BTC/USDT 5m
- Preset: StepGridHybrid (default)

Logs (short snippet):
[HH:MM:SS] [PAIR] [ERROR] Invalid API key/timestamp ...
(Attaching full logs and a screenshot.)

Already tried:
- Clock sync ✅
- Recreated API keys (correct permissions) ✅
Contact: support@gunbot.freshdesk.com

Template — CryptoSlug ticket (GitHub)

Title: [EXCHANGE] [ERROR SUMMARY] — [OS] — [GUNBOT VERSION]

Summary (1–2 lines): …
Repro: 1) … 2) … 3) …
Environment: version/OS/exchange/pair/TF/preset
Short logs: …
Screenshots: …
Links: official ticket + Discord/Telegram topic

Template — Discord/Telegram topic (Clan)

Links: [OFFICIAL TICKET] | [GITHUB TICKET]
Summary (1–2 lines): …
Already tried: …
Need help with: step/TP/logs/risk…
Screens/logs: (image or short snippet)

• Invalid license/subscription → revalidate credentials/license
• API “timestamp/keys” → sync clock + recreate keys (trade only)
• No orders / bot idle → wrong step; review min order and trend filter
• Growing bags → exposure cap, safety orders, quote buffer; define a stop-adding rule

• Never share API keys or files with secrets
• Mask sensitive data in logs/images
• In public spaces (GitHub), remove personal info

• Open official ticket and/or CryptoSlug ticket (GitHub) and share the links in the Clan’s Discord/Telegram
• Include version/OS/exchange/pair/TF, steps, logs, and what you already tried
• Do the preflight (clock, API, presets)
• Keep everything traceable → faster and more precise answers 🚀