Ticketing (support)

Ticketing is the practice of recording every support issue as a ticket, a record with a requester, an owner, a priority and a status, and moving it through a defined lifecycle until it is closed.

A lifecycle in practice. Zendesk’s standard statuses show the usual shape:

• New: no action taken yet. A ticket cannot return to New once it changes.
• Open: assigned, and waiting on the support agent.
• Pending: waiting on the requester. It returns to Open automatically when they reply.
• On-hold: waiting on someone other than the requester. It is optional, enabled by an administrator, and hidden from the requester.
• Solved: the agent has submitted a solution.
• Closed: set by the system a fixed time after Solved, never by hand. The requester can no longer reopen it.

Queues and SLAs. Tickets wait in queues where staff triage and assign them. In Jira Service Management, queues are often sorted by service level agreement, and a rules engine applies SLA targets automatically as requests arrive, showing them on each request. Ticket fields such as assignee, reporter and priority drive routing and reporting.

Tickets and A2A tasks. An A2A task has its own lifecycle, with states such as TASK_STATE_WORKING, TASK_STATE_INPUT_REQUIRED and TASK_STATE_COMPLETED. The two map naturally. A task in TASK_STATE_INPUT_REQUIRED, waiting on the customer’s agent, resembles a Pending ticket. A task that a person on the business side must decide resembles an Open ticket in a human queue. When agent traffic reaches a person, linking the A2A task ID to the ticket keeps a single record of the whole exchange.

Neighbouring terms. The help desk is the function and software that holds the tickets. Escalation moves a ticket to a higher tier. First contact resolution measures how many tickets close without a follow-up contact.