Support · product, security, procurement, incidents

Support for product, security, procurement, and incidents. Routed to the right owner.

Product questions, security review, procurement, and incidents on separate paths. Every request is acknowledged within one business day, with a named owner and a live status page you can check first.

Open desk · acknowledged · routed to owner
Six desks · one record

Pick the desk that matches the ask.

Separate paths for product questions, security review, procurement, and incidents. Each one acknowledges with an owner and a next step.

Product email
support@auraone.ai

Email the team.

Questions about workflows, deployment, SDK setup, or how a module behaves. Includes acknowledgment with an owner attached.

DeskProduct supportlive
FormatEmail threadtracked
OwnerAssigned at intakenamed
Security review
Trust desk

Security review.

Security review materials, Sensitive data safeguards, Data processing review, data processing, sub-processor list, and architecture review materials. For procurement, vendor risk, and InfoSec.

DeskTrustlive
MaterialsPosture · controls · DPAshareable
PathReview file · call · sign-offtracked
Procurement
Vendor intake

Procurement help.

Contracting, MSA, order forms, finance terms, and vendor onboarding. For legal, sourcing, and finance teams running an evaluation.

DeskCommercialnamed
MaterialsMSA · order form · pricingshareable
PathIntake · redline · countersigntracked
Incident report
Severity intake

Report an incident.

A failure mode, a regression, or model behavior you need on the record. Include the run, the environment, and the evidence already captured. Check live system status before you file.

DeskIncident responselive
FormatTicket · captured to recordtracked
PathTriage · reproduce · resolveowned
Documentation
Self-serve

Read the docs.

Deployment patterns, SDK references, API surfaces, and operating notes. Most product questions resolve here before a ticket opens.

DeskDocsself-serve
CoverageSDKs · APIs · operating notesindexed
UpdatesVersioned with releasescurrent
Pilot review
Customer success

Pilot review.

Active programs get scoped review calls with the customer success desk. Workflow audits, evaluation review, and rollout planning.

DeskCustomer successnamed
FormatScheduled reviewtracked
PathAudit · plan · sign-offowned
First response within one business day · priority and severity-one windows shorter by plan
How we respond

Intake. Triage. Resolve.

The same shape every time. Acknowledgment with an owner, reproduction with the evidence attached, resolution with a record you can keep.

STEP 01
INTAKE

Intake.

Every request lands with an owner, a desk, and a severity. Acknowledgment goes back with the path and the next step named.

INTAKE · ACKNOWLEDGED
STEP 02
TRIAGE

Triage.

We reproduce against your environment, attach the evidence already captured, and route to the engineer or reviewer who owns the surface.

TRIAGE · ACKNOWLEDGED
STEP 03
RESOLVE

Resolve.

Resolution lands with the fix, the regression saved to the bank, and a record of the decision. Nothing closes without an owner signing it off.

RESOLVE · ACKNOWLEDGED
Record · ticket SUP-2041

Acknowledged · routed · resolved.

Desk
Product support
Owner
Assigned at intake
Reproduction
Customer environment
Record
Signed · kept · referenceable
00·00 IntakeResolve 04·18
Bring the ask · we'll route it

Help is a path, not a queue.

Tell us what you need. We'll acknowledge with an owner, route to the right desk, and keep the record.

Intake details
Open
First responseWithin 1 business day
OwnerNamed on first reply
PathIntake → Triage → Resolve
StatusLive page · incident history
Create a ticket

Send the details to support

Tell us what happened. The request is only accepted when support delivery is configured for this deployment.

Severity
Response targets are defined by your support plan

What happens next?

  • 1. Intake details are validated and delivered through the configured support provider.
  • 2. The support desk triages severity, product area, and the evidence you include.
  • 3. Response targets and escalation rules apply based on your plan.
Escalation paths and response targets are defined in your support plan.
Support | Documentation and help for live programs | AuraOne