Support center
Find the right path quickly
CRYA support follows real support-center categories and avoids exposing private account details in public channels.
Server limits, demo import, theme package, cache, permissions, and rollback checks.
Image sets, ZIP imports, timing, loops, visual fit, export choices, and package handoff.
desc.txt, frame folders, dimensions, file names, Samsung notes, and safe repair paths.
Submissions, ownership notes, preview evidence, compatibility labels, badges, and review expectations.
Premium, clean exports, store packs, refunds, grants, entitlement evidence, and app-safe purchase paths.
Telegram topics, AI help, moderation-safe support, group rules, status commands, and privacy boundaries.
Before asking
Collect evidence once
Support can move faster when the first message has the useful details.
Package report or exact error text.
Device model, Android version, and export type.
What changed recently and whether the package worked before.
Billing or account issue separated from public group chat.
Public community help should stay about general troubleshooting. Account data, purchases, private links, and moderation actions belong in protected support/admin workflows.
Request types
Choose the lane that matches the problem
The first support decision should be whether the issue is local package work, account access, store review, creator identity, or a live service problem.
desc.txt errors, frame folders, dimensions, static-image exports, ZIP/QMG context, preview mismatch, or app handoff problems.
Submission review, ownership notes, compatibility labels, screenshots, pack updates, badges, or creator profile corrections.
Premium status, clean export credits, receipts, entitlement evidence, refunds, grants, and account deletion requests.
Telegram topic routing, AI answer quality, moderation-safe questions, and public support conversations.
Broken docs/store/status pages, maintenance messages, mail issues, or discovery files that do not load.
Root risk, file access, notification access, app visibility, cleanup tools, firmware context, or Play-safe wording.
Support workflow
How CRYA should triage a report
A consistent support workflow turns repeated questions into better docs, safer AI answers, and cleaner product decisions.
Identify the lane: package, store, creator, account, billing, bot, website, or policy.
Ask for only the evidence needed for that lane and keep private details out of public chat.
Check docs, status, package reports, screenshots, and known device notes before guessing.
Give the user a clear next step, escalation path, or status update.
Turn repeated issues into docs, AI knowledge, store rules, or app fixes.
| Package issue | Package report, screenshots, source ZIP type, dimensions, fps, device model, Android version. |
|---|---|
| Billing issue | Account email/ID through private support, receipt/order evidence, product type, purchase date. |
| Creator issue | Pack URL, creator name, ownership note, review message, screenshots, compatibility target. |
| Website issue | Exact URL, screenshot, time/timezone, browser/device, whether Status shows maintenance. |
Escalation boundary
Public help is not private support
Users should know when a question belongs in the community and when it must move to protected support.
General troubleshooting can happen in public community channels.
Account, billing, deletion, and private links move to protected support.
Moderation, grants, payout, and admin changes stay inside Mission Control.
Root/system risk gets recovery-first guidance and never becomes a casual promise.