Best use
Escalate real blockersSupport is for product problems, blocked work, and investigation paths that need a human.
Account
Contact Support and Report Issue
Support in opheli.ai is designed to feel contextual and trustworthy. Use it when a real blocker remains after Help Center, Mission Replay, Mission Orb, and Copilot have stopped being enough.
Guide summary
Use this page to understand the surface before you act inside it.
Know what support receives, what it does not receive, and how to report a run or related product issue safely.
Guide type
AccountThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
4Written against the current product structure and core execution workflow.
What gets attached
Safe contextRelated object, page context, and bounded status data can be included.
What does not
Provider keys and hidden promptsThose are intentionally excluded from automatic collection.
Guide section
What it is
Support is the user-facing escalation path for product blockers and investigation requests.
When to use it
Use it after workflow guidance, Replay, or Copilot no longer explain or recover the issue.
Where to find it
Find it in Help Center, Mission Orb, the account menu, profile/account help surfaces, and contextual report actions such as Report this Run.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Sending a duplicate request before checking existing requests
Related action
Use Report this Run from the run detail page when the issue is execution-specific.
Guide section
Why it matters
It gives users a clean way to report issues without turning the product into a generic ticketing portal.
Guide section
How it fits into the workflow
Support is the recovery lane when execution, provider posture, context, or artifact flow stops making sense.
Guide section
Step-by-step usage
- Open Contact Support or Report Issue from the most relevant context.
- Choose the category and write a precise subject.
- Describe what happened, what you expected, and what you already tried.
- Submit the request and review the confirmation on the detail page.
- Use My Support Requests to check current status later.
Guide section
Inputs and outputs
Inputs needed
Category
Subject
Message
Related mission/task/run/artifact when possible
Outputs produced
A support request record
A reviewable support status
A cleaner investigation trail for admins
Guide section
Common mistakes
- Sending a duplicate request before checking existing requests
- Pasting secrets or full stack traces
- Reporting a run generically without attaching the run
Guide section
Troubleshooting
If support still needs more context, open the request detail and verify whether the correct related object was attached.
Guide section
What support context is attached
Support requests do not automatically include Provider keys or full Context content. Report this Run attaches safe status and object references only.
Included
Route and page context
Related mission/task/run/artifact IDs when present
Safe status or phase posture
Not included automatically
Provider API keys
Encrypted credentials
Hidden prompts
Full stack traces
Private source uploads copied in full
Warning
Do not paste secrets into support
Support requests should stay safe even if the request later needs to be reviewed across support tools.