The token. The system.
One place for support.
Customer service is part of ONE, not an afterthought. This center connects the website to the existing upgraded SERVICE layer and existing Telegram channel without replacing either.
One service layer.
Two support domains.
The website routes authorized support requests to your existing upgraded SERVICE layer. It does not create a second service engine or change the trading runtime.
Keep the existing bot.
Continue support for the token and the system through the same Telegram bot. The existing host retains its receiver, reply policy and delivery path.
The bot's public username has not been configured. No placeholder bot or invented contact is used.
Ask the existing SERVICE layer.
A support request does not require 10,000 PARNASA. That holding condition belongs to a separate trading-access design. Private website requests require an authenticated session; general guidance remains public.
Support essentials
Do I need 10,000 PARNASA to get help?
No holding threshold is applied to support. The 10,000-token condition belongs to separately controlled trading-system access. An authenticated session is required for private website requests, not for reading this guidance.
Does linking Telegram authorize trading?
No. A bot contact or bot-identity observation is not a wallet-account link, trading permission or approval to spend tokens.
What is confirmed by a service-plan receipt?
Only that the existing SERVICE layer returned a scoped plan, review or blocked result. Ticket creation, delivery and resolution each require a separate verified receipt.
What must never be shared with support?
Seed phrases, private keys, passwords, exchange secrets or Telegram bot tokens. Describe the symptom without credentials. Automated checks are limited and do not guarantee detection of all sensitive information.