LeenOpsDocs
Support

Support

Open a LeenOps support request with the context needed for a fast response.

Email support@leenops.com to open a LeenOps support request.

Current support channel

LeenOps does not currently expose a customer ticket portal or a My requests screen in the console. Email is the documented support intake path. Keep the sent email as your request record until a tracking number is returned.

What to include

Use this subject:

[LeenOps Support] Workspace name — short problem summary

Include:

  • Workspace name.
  • The LeenOps page or product involved.
  • What you expected to happen.
  • What happened instead.
  • Approximate date and time, including your time zone.
  • Assistant, installation, conversation, run, or deployment ID when available.
  • Exact error text.
  • Safe reproduction steps.
  • Browser and operating system for console problems.

What not to send

Never include:

  • API keys or provider secrets.
  • GitHub, Supabase, or cloud access tokens.
  • Hermes install or telemetry tokens.
  • Passwords, recovery codes, or session cookies.
  • Full .env files.
  • Customer personal data that is not necessary to investigate the issue.

Redact screenshots and logs before attaching them.

Severity guide

SeverityUse whenInclude
CriticalProduction is unavailable or a security incident is suspectedImpacted workspace, start time, affected users, safe contact details
HighA core workflow is blocked with no workaroundFailed run or deployment ID and last known successful time
NormalA feature is degraded, confusing, or produces an incorrect resultReproduction steps and expected behavior
QuestionYou need setup or product guidanceGoal, current setup, and relevant product

For a suspected security issue, put Security in the subject and do not include exploitable credentials.

Useful self-service checks

Request template

Workspace:
Product or page:
Severity:
Expected:
Actual:
Started at (with time zone):
Relevant IDs:
Safe reproduction steps:
Error text: