To raise a ticket means to log a support request so that it becomes a tracked record instead of a message someone might forget. The moment it is raised it gets a reference number, a status and an owner, and if the team uses service level targets, a clock starts running.
There is no difference in meaning. They are regional habits for the same action.
Raise a ticket is British, Irish, Indian and Commonwealth IT usage, and it is the phrasing you will hear in most managed service and enterprise IT teams. Open a ticket and submit a ticket are more common in American English. Log a ticket turns up in both, and tends to be used where the emphasis is on record-keeping.
If someone tells you your ticket has been raised, opened, logged or submitted, they are all telling you the same thing: your request now formally exists in a queue, with a reference attached.
Raising a request converts it from a message into a record. Five things attach to it at that moment:
Being told your ticket has been raised is not a promise about when the work will be finished. It means the request exists, someone owns it, and the time taken is being measured.
In most organisations there are three routes, and which one you use rarely matters because they all end in the same queue.
Whichever route you use, the useful habit is the same: say what you expected, what actually happened, and when it started. A ticket raised with those three things can usually be worked on immediately, rather than costing a round trip to ask.
In an IT company the phrase covers the same action, but the requests fall into recognisable types. An incident is raised when something that used to work has broken. A service request is raised when someone needs access, hardware, software or a change to an account. A change request is raised when the work would alter a live system and therefore needs approval before anyone touches it.
Tickets may be raised by employees against their own internal IT team, or by customers against a supplier. The mechanics do not change. What changes is who is measured: internal desks tend to report on volume and resolution time, while a supplier is usually measured against the response and resolution targets written into a contract.
For a fuller walkthrough of how the queue itself works, see the ticketing system guide, or the help desk guide for how a support desk is structured around it.
| Term | What it means |
|---|---|
| Ticket raised | The request has been logged and is in the queue with a reference attached. |
| Raising a ticket | The act of logging the request, by email, portal or form. |
| Raise the ticket | An instruction to log a specific request, usually so that the work is tracked rather than done informally. |
| Ticket | The record itself: the request plus its ID, status, owner, priority and full history. |
| Escalate a ticket | Move an existing ticket to a higher priority or a more senior team. Different from raising one, which creates it. |
| Close a ticket | Mark the request finished. The record stays for reporting and for reopening if the problem returns. |
It means your request has been logged as a tracked record with a reference number, a status and an owner. It is confirmation that the request exists and is being measured, not a commitment to a completion date.
Yes. Raise, open, log and submit all describe the same action. Raise is British and Commonwealth usage, open and submit are more common in American English.
Anyone the desk supports. On an internal desk that is employees; on a customer-facing desk it is customers. Agents can also raise a ticket on someone's behalf when a request arrives by phone or in person.
What you expected to happen, what actually happened, and when it started. Add the exact error text and anything that changed recently. That is usually enough for work to begin without a round trip for more detail.
Raising creates the ticket. Escalating takes a ticket that already exists and moves it to a higher priority or a more senior team, usually because it is at risk of missing a target or needs different expertise.
Give your team a support address and a portal, and every request becomes a tracked ticket with an owner and a clock. Free for 5 agents and 500 tickets a month, with no credit card.
Free foreverNo credit cardNot a 6-month trial