Support starts before the ticket is opened.
This page separates documentation, functional incidents, security, and commercial questions. It helps assemble a complete diagnosis without inventing a portal, address, or response time.
Current channels
No production portal or SLA is connected. The site prepares the information and will display real channels before publication.
I need to know how
Documentation, configuration, and limitations by app.
Open the docsSomething does not work
Version, URL, steps, expected result, observed result, and a capture with no sensitive data.
Prepare diagnosticsI am reporting a security risk
Private channel still to configure; do not publish secrets or customer data.
View the procedureI am evaluating a purchase
Use case, compatibility, licensing, and deployment.
Prepare the briefThe diagnostic packet that avoids the first round trip.
Remove secrets and personal data before any capture or export.
- 01App name, version, and Jira or Confluence hosting.
- 02Non-sensitive URL or identifier for the affected surface.
- 03Minimal steps to reproduce the problem.
- 04Expected result and observed result.
- 05Time, time zone, and frequency of the problem.
- 06Exact error message and available correlation identifier.
- 07Recent permission, configuration, or dependent-app change.
Priority without a fictional SLA.
Impact, scope, and workaround determine severity. Contractual response times will be displayed only when a real support service exists.
- 01Critical: broad unavailability or data risk with no workaround.
- 02High: primary path blocked for several people.
- 03Normal: degraded function or localized problem.
- 04Question: configuration, usage, or improvement without an incident.
Prepare the context now. Connect the real channel at launch.
Start with the product documentation. If the problem persists, copy the diagnostic checklist and keep sensitive information out of public channels.