Contact support and send feedback

Gather where the issue happened, what you did, and what resulted, then contact the team providing your AIRI loci service. In a team workspace, your administrator can first confirm permissions, allowances, and support channels.

Include useful details

Provide the time, workspace and project, steps, expected and actual results, exact error text, and relevant order or task identifier. You do not need to reconstruct the entire project history.

Time: …
Workspace / project: …
Action: Uploaded two files, waited for processing, and requested a brief comparison.
Expected: Read both files and compare their differences.
Actual: One reference is unavailable. Exact error: …
Tried: Selected the file again; the issue persists.
Attachments: Error screenshot, filename, and format.

Add issue-specific evidence

For uploads, include type, size, and whether the file opens locally. For generation, include the conversation, materials, and model. For export, include selection, format, and error. For payment, include order number, time, amount, and payment status.

Capture the affected area and surrounding messages. Before sharing original files, confirm the permitted scope and hide unrelated personal information. Passwords, verification codes, and payment passwords are never required.

Product feedback

Describe the goal you struggled with, your workaround, and where assistance would help. “I found the image but cannot reference it in this task” is more actionable than “the interaction is poor.”

Keep the same issue record and identify follow-up material. A button click alone does not prove submission succeeded; look for a success message, ticket, or explicit receipt.

Task failures · Export issues · Payment issues · Documentation