Support
Tell us what failed.
Vesk is built to report what it could not verify. If that report is wrong, incomplete, or unclear, there should be a direct way to tell the people building it.
Support is email. The link below opens a message with space for the details that help us trace a run.
support@vesk.appWe read everything and reply as soon as we can.
A useful report
Send the evidence with the problem.
Email cannot attach run context automatically yet. These three details make a report actionable without pretending an in-app reporting system already exists.
Run identity
Include the run ID if the product gave you one. It is the shortest path from your report to the exact record that produced the verdict.
Observed result
Copy the VERIFIED, ADVISORY, FAILED, or NO DATA label and the check that produced it. Do not clean up a failure before sending it.
Expected result
Tell us what you expected the robot or generated package to do. If the report involves proprietary code, describe it without attaching anything you are not comfortable sharing by email.
Safety
Do not email credentials.
Remove API keys, access tokens, passwords, environment variables, and any customer-owned files that are not necessary to explain the issue. A run ID and the visible verdict should be the starting point.