Contact Lithi
How to write a clear support message about a Compute or Connect problem, without passwords, keys or private files.
Start with one clear problem
Say what you tried, what you expected, and what happened instead. Name the affected area, such as Compute, Connect, account access, billing, or a security concern.
Include the approximate time with its time zone and any safe reference you already have. Do not repeat a payment, submission, or configuration change just to create more evidence.
Remove private details first
Leave out passwords, API keys, access codes, authorization headers, signed URLs, bank details, private messages, customer files, and unrelated personal information. Review screenshots before sharing them.
Use identifiers that are safe to disclose, such as the relevant job, quote, invoice, or support reference when one exists. Describe the problem; do not paste a full request, response, environment file, or customer payload.
Send the request through the current contact route
Open Contact Lithi. Choose Send us a message for the general enquiry form. The form asks for contact details and a message; it is not a surface for uploading customer files.
If the form cannot be used, the same Contact page offers hello@lithi.ai as its email fallback. For a suspected vulnerability or exposure, use the dedicated security reporting route instead.
Read the submission result correctly
A successful form submission shows the message-sent confirmation and creates its intake receipt. That confirms the contact intake accepted the request. It does not mean the underlying technical, billing, privacy, or security issue is resolved.
If the form reports an error, keep the text of that error and use the email fallback. If the outcome is unclear, do not send repeated copies automatically; state that the first submission may be unresolved.
Know when to stop
Stop before including secret or customer content that the support team has not specifically requested through a protected process. A support acknowledgment is not payment confirmation, incident closure, deletion evidence, or permission to run new work.
Keep the original safe reference so follow-up stays tied to the same problem.