Open a useful support request
In Support, choose the appropriate context and describe the issue. For a project, include its name, the page, your intended action, the actual result and the time. Mask personal data in screenshots. Never send passwords, access codes or full card numbers.
Continue in the same conversation
The team can also start a conversation to contact you. Reply in the relevant ticket instead of creating duplicates for the same issue. Formal project revision requests belong in the available revision round.
Read the status and waiting side
Open, In progress, Resolved and Closed describe the request’s lifecycle. Waiting for client means the team needs your response. Internal response targets do not add a timing guarantee beyond any applicable contractual commitments.
Reopen an unresolved issue
Read the resolution or closure reason. If the problem persists, choose Reopen when available and explain what remains. Reopen before replying to a closed conversation. Create a new request for a different issue.
Dashboard notifications and email
Use the notification centre and open an event to reach the relevant section. Reading a notification does not confirm terms, payment or publication. Email can be delayed or filtered as spam; check the order page for its current status.
If you cannot sign in
Email info@siti.gratis with your account email and a short explanation. Use the same address for privacy requests, clearly stating the subject. Do not attach sensitive documents unless requested through an appropriate channel.