For an order or a settlement
Give the record reference, the step concerned and what you expected. If the problem concerns payment, add the method chosen, the time of the transfer and the message shown in the tracking. Keep the details provided by your wallet so you can find them again if needed.
After a transfer, first use "I've paid" in the corresponding intent. If the report is already recorded, do not send another payment to try to change the status. A support request lets you describe the point to be examined while keeping the record context.
For a launch or an unexpected output
Specify the program, the relevant versions, the launch command and the first abnormal message. Distinguish an environment that does not start, a model that does not load and an incorrect result after computation. Mention the changes that occurred since the last known attempt.
Share a short excerpt and remove any secrets. You don't have to hand over all your data, prompts or code to explain a first anomaly. A reduced example, the expected behavior and the observed behavior make the problem easier to examine.
Keep access to tracking
Requests are tied to your Kernodeck account. Log in with your email and password to find your references and exchanges, from your usual browser or another device. Logging out closes access to this information without deleting its tracking.
If you can no longer log in, see the account access guidance. There is no automatic reset by email. An email address on its own or a public transaction reference is not enough to open a case.