Skip to main content
FlightStudioFlightStudioOpen dashboard

Support centre

A clear route from issue to accountable response.

Choose the path that matches the situation, send only the context that is safe to share, and keep operational command inside your approved procedures.

Four response pathsSafe-by-default intake

Contact support

Choose the right response path.

Each route opens a prepared email with the context that helps triage the case. Leave out anything that should not travel through email.

Evaluation

Evaluation and access

Use this route for trial access, installation questions, licensing, or help framing a technical evaluation.

Include, if safe

  • Organization and role
  • Evaluation goal
  • Preferred deployment mode
  • Target timeline
Start this request
Licensed deployment

Deployment support

Start a case for installation, upgrade, configuration, integration, or unexpected platform behavior.

Include, if safe

  • Release version
  • Deployment mode
  • Expected vs observed behavior
  • UTC time and correlation ID
Start this request
Responsible disclosure

Security report

Report a suspected vulnerability with a minimal, safe reproduction. Do not include credentials, customer data, or active exploit traffic.

Include, if safe

  • Affected release
  • Security impact
  • Minimal reproduction
  • Safe contact details
Start this request
Priority route

Operational incident

Begin vendor coordination for a material production issue after activating your organization’s approved incident procedure.

Include, if safe

  • Agreement or customer reference
  • Current severity
  • UTC timeline
  • Sanitized symptoms and correlation IDs
Start this request

Case preparation

Give support a clean starting point.

A concise case is easier to route and reproduce. Capture the environment, the smallest repeatable sequence, and the evidence that identifies the same event across services.

  1. 1
    Identify

    Release, deployment mode, affected service, and tenant-safe scope.

  2. 2
    Reproduce

    Minimal steps, expected result, observed result, and frequency.

  3. 3
    Correlate

    UTC timestamps, correlation IDs, and the smallest sanitized log excerpt.

Self-service

Check the published source first.

These resources stay available without opening a case or sharing deployment data.

Documentation

Product behavior, deployment concepts, and published technical reference.

Field playbooks

Structured operating guidance for standards, integrations, and evidence.

Trust Center

Dated verification evidence and precise product-assurance boundaries.