Find an answer or keep the whole support conversation in one place.
Search practical guidance first. When something needs investigation, create a tracked ticket with the page and device context already attached.
One reference. One conversation. No repeated explanation.
Search first
Clear answers written for current Corexa workflows.
Report clearly
Capture the problem, expected result and operational impact.
Track replies
Continue the discussion against one ticket reference.
Frequently asked questions
Practical answers by workflow
My tickets
Support history and replies
Include operational detail, not secrets
Add record references and exact error text, but never include passwords, payment card details, API keys or private credentials in a ticket.