Support
There is one person here, and he answers.
Published by Scena Studio LLC and engineered by founder Alex Mercer. No ticket bot and no first-line call-center script — every reply comes straight from the lead engineer who can actually fix the code, and here is honestly how long it takes.
Last updated 29 Oct 2026
Fastest
From inside the app
Attaches the log, the failing job and your build number, so the first reply can be an answer instead of a request for more detail. Help → Report a problem Usually answered within a day
Email
Write directly
For licences, invoices, refunds and anything you would rather not post in a group. Reaches one person, not a ticket queue. support@scenastudio.app One to two working days
Community
Ask the group
Someone has usually hit it already. Build announcements and workarounds land here first, often before they reach the status page. Telegram · Facebook · Discord Minutes to hours, from anyoneWhere the conversation happens
Five channels, because people are already in different places. They carry the same announcements; pick whichever you already have open.
Q&A · SHOWCASE
Facebook group
showcase and Q&A
English · Tiếng Việt
fb.com/groups/scenastudio
Join Facebook
HD WALKTHROUGHS
YouTube channel
walkthroughs
English, subtitled
youtube.com/@scenastudio
Watch YouTube
What makes a report useful
For an API issue, include the provider, the error message and whether you used shared credits or your own key. Scena Studio covers shared API use at the start of the Open Test on enabled services and sets no per-user usage quota or credit cap on shared use. Once shared access ends, you must use your own API keys for AI generation. Provider rate limits, availability and anti-abuse rules apply. Usage on your own key may incur charges from the provider. See Pricing for post-test software plans. What you expected to happen, and what happened instead. One sentence each is plenty. The build number from Help → About, because the fix may already be out. Whether it happens every time or only sometimes — that difference changes where to look. The job that failed, if it was a queue problem. Report a problem attaches it for you. A screenshot if it is visual. Not the whole desktop, just the part that is wrong.
A report that can be reproduced earns a Studio lifetime key for every 1.x release — whether or not the bug turns out to be mine.
Report a bug
How long things take
Measured over the last two months, not aspirational.
Blocking bug, reproducible
same day
Licence, invoice or refund
1–2 days
Feature request
answered, not promised
Question already in the FAQ
you get a link
Weekends and public holidays
slower
If a message has gone unanswered for more than three days, it was missed rather than ignored — send it again in the group and it will be picked up.
