What is ticket?

A ticket is a support request recorded in a helpdesk, the software that stores and routes requests, with a number, a status, an owner and a history of every reply. Zendesk, Freshdesk, Zoho Desk and HubSpot work this way; Salesforce calls the same record a case. The ticket is the unit a support team is measured on: tickets opened, tickets closed, time to first response, time to resolution.

It matters to AI support in two ways. First, an AI agent can open a ticket when a chat needs follow-up nobody can give live, so the request lands where the team already works, with the transcript attached, instead of in a second inbox. Second, the ticket is the unit behind deflection: a deflected ticket is one that would have been opened and was not, because the agent answered first. Vendors that bill per resolution are, in effect, billing per ticket not created.

Where definitions split: a chat conversation and a ticket are not the same thing. A conversation is a session in a widget; a ticket is a durable record with an SLA. Some helpdesks turn every chat into a ticket automatically, which inflates ticket counts and makes deflection look worse; others create one only on handoff. Where the idea runs out: a ticket created by a bot still needs a person to answer it, so creating tickets is a handoff by another name, with the same questions attached. Who watches the queue, how fast, and what is the visitor told meanwhile.