Agnes Video GeneratorSupport availability
Studio support will open through a verified contact channel when live accounts and generation are activated. No monitored email address or ticket form is currently configured. Studio support does not ask you to send private materials to an invented destination. You can still use this page to prepare the information a future support request will need. Studio support availability must be checked here before assuming that a social account, page comment or unrelated address reaches the operator.
Describe the issue clearly
For studio support, begin with the action you attempted and what happened instead. Include the page path, approximate time and visible error message. A short factual account is more useful than repeatedly submitting the same failed request. Studio support should never need your password or secret API key. Before a verified channel opens, keep these details locally. Studio support will distinguish preparation issues, identity problems and generation failures so the right service can be checked.
A problem with a prompt
Studio support can investigate a form issue more effectively when the expected behavior is clear. State whether you were editing a text scene, selecting an image or adjusting the scene settings. If the page shows a capability notice, include its wording. Studio support does not need a sensitive prompt copied into a public comment. Redact personal details first. For studio support preparation, note your browser and whether the problem also occurs after a normal page reload.
An image will not load
For studio support, first check the image format and size. The preparation interface accepts JPG, PNG and WebP under ten megabytes, and rejects damaged files. A preview failure can also result from a format whose extension does not match its contents. Studio support should receive the error and file properties rather than an unapproved private photograph. Before contacting studio support, try exporting a clean copy from your own source and confirm that you have permission to use it.
A project is waiting
Studio support will need the internal job identifier for a live generation that appears stuck. A queued task and a processing task are different states, and neither promises an exact finishing time. Do not keep creating new jobs to check the old one. Studio support should inspect the durable record and provider status. Until a live job service is connected, studio support cannot recover a real generation from a local prompt draft or an illustrative scene card.
A credit question
Studio support should reconcile balances using the project or transaction identifier, the quoted amount and the observed status. Do not share full payment details in an ordinary message. A browser success page is not sufficient payment evidence. Studio support needs verified billing events and durable ledger records to resolve a mismatch. Before paid creation opens, studio support must have a monitored route and a clear process for failed-job reservations, duplicate events and purchase questions.
A download problem
Studio support will need to know whether the video played, whether the download control returned an error and whether the link may have expired. Private result links should not be posted publicly. An expired link may require a new authenticated download destination. Studio support must verify ownership before granting access. For studio support preparation, keep the job identifier and relevant timestamps, but avoid sending the full signed URL because it may grant access to the media itself.
Copyright and likeness complaints
Studio support will provide a verified complaint channel before public generation opens. A useful rights report identifies the work, the claimed ownership or authority and the specific material at issue. Do not send unnecessary identity documents through an unverified route. Studio support must examine complaints fairly and may need additional evidence before acting. Preparing a studio support report does not itself establish infringement, and a public page share link should not be confused with a private project reference.
Security and privacy reports
Studio support should receive security reports through a verified private channel, rather than through public exploitation. Describe the affected feature and the smallest safe reproduction. Do not access someone else’s media or attempt to prove a balance issue by making unauthorized changes. Studio support must prioritize exposure of personal information, authentication failures and unintended access. Until that channel is configured, studio support does not request secrets, live session tokens or private user data through this informational page.
What happens next
Studio support remains unavailable for live tickets until the operator publishes and monitors a real destination. The studio currently supports scene preparation rather than connected paid generation. Studio support expectations will be updated alongside the identity, database and billing integrations. Read the privacy policy before sharing personal information and the terms before submitting content. Studio support does not promise a response time that has not been staffed or imply official representation of the Agnes brand or provider.