Ticket Lifecycle
Definition
The ticket lifecycle is the full sequence of stages a support ticket moves through from creation to closure — typically created, assigned, in progress, resolved, and closed.
How it works
A ticket is created when a customer reaches out on any channel. It's then triaged — categorized, prioritized, and routed — and assigned to an agent or queue. As work happens it's in progress (open), possibly cycling through pending while waiting on the customer or on-hold while waiting internally.
Once the issue is fixed it's marked resolved/solved, and after a quiet period with no reopen it's closed. Each stage maps to a ticket status, and moving between stages is what SLA timers, automations, and reporting all track.
Why it matters
The lifecycle is the frame every support metric hangs on — first-response time, resolution time, backlog, and reopen rate are all measured across these stages. Understanding it also shows where automation fits: AI can handle triage and routing, resolve routine tickets outright, and hand off to a human at exactly the point where the lifecycle needs one.
- Created → Triaged → Assigned → In progress → Resolved → Closed
- Each transition can trigger automations and SLA events
- Reopens loop a resolved ticket back to open
Frequently asked
What is the difference between ticket lifecycle and ticket status?
The lifecycle is the whole journey a ticket takes from creation to closure; status is the specific field marking where it is in that journey at any moment. Statuses are the checkpoints along the lifecycle.
Where does AI fit in the ticket lifecycle?
AI can act at multiple stages — classifying and routing on creation, resolving routine tickets in progress, and escalating to a human with full context when a ticket needs one — often shortening the lifecycle for common requests.
Related terms
Ticket Status
Ticket status is the field on a support ticket that shows where it is in the resolution process — common values are new, open, pending, on-hold, solved, and closed..
Ticket Routing
Ticket routing is the process of directing incoming support tickets to the right agent, team, or queue based on rules like topic, channel, language, priority, or customer tier..
SLA Policy
An SLA policy is the configured set of rules inside a help desk that assigns service-level targets — like first-response and resolution times — to tickets based on conditions such as priority, channel, or customer tier..
Reopen Rate
Reopen rate is the percentage of resolved or closed support tickets that are subsequently reopened, usually because the customer's issue wasn't actually fixed..
AI Ticket Automation
AI ticket automation is the use of AI to handle support tickets automatically — classifying, tagging, routing, drafting replies, or fully resolving them — reducing the manual work agents do on each ticket..
Put these ideas to work
Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.
Start Trial
Zendesk
Freshdesk
Gorgias
Front
Shopify
Stripe
Slack
Notion
Google Workspace
Confluence