Glossary
Ticketing system
A ticketing system records every request as a case of its own with a status, an owner and a history.
In support and in IT, the ticket is the unit of work: it records who reported something, what it is about, who is responsible and what has already been done. Requests reported by phone are easily lost without a ticket, because they exist only as a note or in one person’s head.
An AI phone assistant can create a ticket straight from a call. To do so it asks for the mandatory details, such as customer, affected device or product, description of the problem and urgency, and selects the matching category. For existing cases it can state the status or add a remark. A clear rule for urgent cases makes sense: an outage should not merely end up as a ticket but should also notify someone or be put through.
In practice
First determine which details a ticket needs so that someone can start work without asking back, and have the assistant collect exactly those. Keep the list short, because every additional mandatory question lengthens the call. Design categories and urgency levels so that they can be told apart on the phone: “nothing works any more” is easier for callers to grasp than “priority 2”. At the end the assistant gives the ticket number or says how the confirmation will arrive. Check regularly whether tickets created by phone reach the right queue.
An example
One morning an employee of a law firm calls an IT service provider: the printer in the office does not print, and three colleagues are waiting. The assistant asks for company, site and device, checks whether other devices are affected and creates a ticket in the category “printer” with normal urgency. Shortly afterwards another customer reports that the internet is down in the whole office. That ticket gets the highest level, and the on-call technician’s phone rings as well.
A common misunderstanding
A ticket that has been created is easily mistaken for a request that has been solved. For the caller, something has only happened once somebody responds. So make sure tickets from phone calls do not vanish into a catch-all category nobody looks at. The second typical mistake is duplicates: when the same person calls twice, the assistant should ask about an existing case instead of opening a new ticket.
At Call0
The Call0 integration directory contains over 500 entries, including ticketing systems.
On this topic:
As of: 12 October 2026