Hello Alex Docs

Support Tickets

Open, track, and resolve requests that need human support follow-up. Read the Account guide in Hello Alex documentation.

Overview

Support tickets keep issue handling organized because one thread preserves context, updates, and resolution history.

A ticket captures issue details, priority, and attached page context so support can reproduce and triage faster.
Replies and status changes stay in the same record, which avoids fragmented troubleshooting across duplicate requests.

Subject: Short summary shown in your ticket list.
Priority: Normal or urgent; use urgent only for production-blocking issues.
Context: Auto-attached pathway or page context when opened from Report Issue or Docs.

Good to know: including launch name, call IDs, or pathway references usually shortens time to diagnosis.

List view gives operational visibility into open workload and response state.

Open active tickets and add missing reproduction details where needed.

Status and priority columns show which threads need action now and which are waiting on support.
Opening a row reveals full context and message history, so follow-up stays consolidated.
Subject: Short summary in the ticket list.
Good to know: clear subject naming helps teams route urgent requests quickly.
Daily support queue review
Urgent issue triage

Creation quality influences support speed because better context reduces back-and-forth clarification.

Submit the ticket and monitor for first-response guidance in the detail thread.

Subject, priority, and reproducible description establish issue scope and expected urgency.
Attached pathway or launch context provides technical breadcrumbs that accelerate investigation.
Priority: Use urgent only for production-blocking issues.
Good to know: urgency is most effective when paired with clear business impact and concrete reproduction steps.
Bug reporting
Workflow clarification requests

Detail view is the single source of truth for support communication on one issue.

Provide requested logs or examples in the same thread until status moves to resolved.

Threaded replies preserve chronology, making decision history and requested actions easy to audit.
Centralized context avoids duplicate tickets and keeps fixes tied to the right incident.
Context: Auto-attached page or pathway context.
Good to know: replying in-thread rather than opening new tickets improves continuity and response quality.
Ongoing incident collaboration
Resolution verification

Open a ticket with reproducible details and keep follow-up in the same thread until resolution.