Owning surface
Mission Control, Mission Orb, the account menu, and Help CenterStart where the product already explains or controls the problem.
Support
Can’t find something
opheli.ai is designed around execution flow, so the right answer is often “open the surface that owns the next step” rather than “search every navigation label.”
Guide summary
Use this page to understand the surface before you act inside it.
Use the product structure, Mission Orb, and admin separation rules to locate the right surface quickly.
Guide type
SupportThis guide reflects the current product workflow and surface ownership.
Sections
5Summary first, then steps, mistakes, and recovery notes.
Related guides
3Written against the current product structure and core execution workflow.
Escalation rule
Use support with contextAttach the relevant run, mission, task, or artifact whenever possible.
Related action
Contact Support only after inspectionSupport is strongest when the dominant symptom is already known.
Guide section
Symptoms
These signals usually indicate this specific class of problem.
What it is
Use the product structure, Mission Orb, and admin separation rules to locate the right surface quickly.
When to use it
Use this guide when these symptoms match what you see in the product.
Where to find it
Start from the owning surface: Mission Control, Mission Orb, the account menu, and Help Center.
What happens next
You narrow the problem before you retry or escalate.
Common mistake
Escalating too early without checking whether the owning surface already explains the blocker.
Related action
Open the owning surface first, then return here if the diagnosis is still unclear.
- You know the feature exists but cannot remember where it lives
- The surface you opened does not seem to own the problem
- Admin and normal user areas feel blurred
Guide section
Likely causes
- The feature belongs to a different layer of the workflow
- Mission Orb already has the direct path but was ignored
- The surface is admin-only or account-only
- The issue is help/IA confusion rather than broken logic
Guide section
How to fix it
- Use Mission Orb when it offers a next-best action
- Use Help Center home to browse by workflow stage
- Use the account menu for Help Center, Contact Support, and account/security areas
- Remember that admin surfaces do not appear in normal user navigation
Guide section
Where to inspect next
Use the product surface that owns the problem first.
Where to find it
Mission Control, Mission Orb, the account menu, and Help Center
What happens next
The owning surface should tell you whether the next move is fix, retry, continue, or support.
Related action
Move into Mission Control, Mission Orb, the account menu, and Help Center now if you have not already done so.
Guide section
When to contact support
Contact support if the navigation or IA itself feels misleading rather than just unfamiliar.
Tip
Report with the right object
A linked run or artifact is much easier to investigate than a generic support request with no runtime context.