How to Create and Manage Tickets in Freshservice
| Quick Summary Every service desk eventually runs into the same operational question: how do you keep ticket creation fast for end users while keeping ticket management organized for agents? This guide covers how to log a new ticket manually, which fields matter most, how the priority matrix sets urgency automatically, how a ticket moves through its status lifecycle, and how scenario automation and bulk actions handle repetitive work across dozens of tickets at once. Pairing this workflow with Freshservice ITSM Software gives growing IT teams a single, structured place to track every request from intake to resolution. |
What Does Creating and Managing Tickets Mean in Freshservice?
Creating a ticket in Freshservice means capturing a request as a structured record rather than a loose email or a verbal request that nobody wrote down. Every ticket holds a requester, a subject, a description, and a set of fields that tell the rest of the team what the issue is, how urgent it is, and who owns it. Freshservice splits tickets into two broad categories: Incidents, which cover unplanned disruptions such as a laptop that will not boot, and Service Requests, which cover planned asks such as provisioning new software.
Managing a ticket, meanwhile, is everything that happens after it lands in the queue: assigning it to the right agent, updating its priority as new information comes in, attaching assets or notes, and eventually moving it to Resolved. Treating creation and management as two connected steps, rather than a single one-time form submission, is what keeps a growing Freshservice instance from turning into an unsorted pile of open tickets within a few months.
Why Does Structured Ticket Management Matter for IT Teams?
Ticket volume rarely shrinks on its own, and the agents handling that volume are working against a real capacity ceiling. HDI’s State of Tech Support 2025 report notes that support agents handle an average of roughly 21 tickets per day, which makes capacity planning, not just hiring, central to keeping queues under control. Consequently, a service desk that creates tickets consistently, with the right priority and category attached from the start, gives agents a fighting chance at clearing that volume without dropping requests.
Resolution speed also depends heavily on whether the first agent who opens a ticket has enough information to act on it immediately. SQM Group’s 2025 benchmarking study puts the average first-contact resolution rate across industries at around 70 percent, with top-performing teams reaching 80 percent or higher. Tickets that arrive in Freshservice missing a clear subject, an assigned category, or a sensible priority routinely fall into that remaining 30 percent, since the agent has to chase down basic context before any real troubleshooting can begin.
How Do You Create a New Ticket in Freshservice?
Most tickets in Freshservice originate from the support portal or an inbound email, but agents frequently need to log a request manually, for example when a user calls in directly or when proactive maintenance needs tracking. Freshservice supports both a quick manual flow and a template-based shortcut for repetitive ticket types.
How Do You Create a Ticket From the Agent Portal?
From inside Freshservice, agents go to Tickets > List and click + Create, then select Ticket. This opens the ticket creation form, where the agent fills in the requester’s name, a clear subject line, a description of the issue, and any required fields such as category or priority. If the requester does not already exist in the system, the Add new requester option creates their profile on the spot. Once the relevant fields and any attachments are in place, clicking Submit logs the ticket and assigns it the default Open status.
How Do You Speed Up Ticket Creation With Templates?
For ticket types that repeat often, such as new-hire onboarding or standard hardware requests, form templates pre-fill many of the fields automatically. Selecting a template from the dropdown on the ticket creation form saves agents from re-entering the same category, group, or description structure every time a similar request comes in, which keeps tickets consistent even when several different agents are creating them.
What Ticket Fields Should You Complete When Logging a Request?
A ticket is only as useful as the fields attached to it, and a handful of fields do most of the heavy lifting when it comes to routing and reporting later.
| Field | Purpose |
| Subject | Gives agents a one-line summary that is searchable across the ticket list |
| Type | Distinguishes an Incident from a Service Request, which affects available workflows |
| Priority | Signals how quickly the ticket needs attention relative to others in the queue |
| Category | Groups similar tickets together for routing rules and reporting |
| Group/Agent | Determines who is responsible for picking up the ticket next |
| Description | Captures the full context an agent needs before starting to troubleshoot |
How Do You Associate Assets and Tags With a Ticket?
Beyond the standard fields, Freshservice lets agents link a ticket directly to the hardware or software it concerns through the Associate Assets option on the ticket form. Once an agent links a configuration item, such as a specific laptop or server, to a ticket, Freshservice adds that ticket to the asset’s history. This makes it much easier to identify devices that generate repeated issues instead of treating each report as a separate incident.
Tags work in a similar but more flexible way: rather than tying a ticket to a specific asset, a tag like “VPN” or “Onboarding” groups tickets by theme, even across categories, so an agent or manager can filter the list view by tag and instantly see every related request regardless of who logged it or which department it came from.
How Does the Priority Matrix Set Ticket Priority Automatically?
Rather than leaving every agent to judge priority by feel, Freshservice offers a Priority Matrix that calculates it automatically from two simpler fields: Urgency and Impact. Once enabled under Admin > Service Management > Helpdesk Settings > Priority Matrix, administrators define what combination of urgency and impact maps to Low, Medium, High, or Urgent priority. The matrix can also be configured to let requesters set urgency and impact themselves while submitting a ticket through the portal, which removes the guesswork from the agent’s side entirely.
| Urgency | Impact | Resulting Priority |
| Low | Low | Low |
| High | Low | Medium |
| Low | High | Medium |
| High | High | Urgent |
How Do You Move a Ticket Through Its Status Lifecycle?
Every new ticket in Freshservice starts out as Open, regardless of whether a requester or an agent created it. From there, agents typically move the ticket to In Progress while they work on it. They change the status to Pending when they need information from the requester or a third party. Once they fix the underlying issue, they mark the ticket as Resolved. After a predetermined period configured by the administrator, a Resolved ticket automatically moves to Closed without anyone needing to take further action.
To update a ticket’s status manually, an agent opens the ticket, clicks the Properties icon, selects the new status from the dropdown, and clicks Update. Because SLA timers are usually tied to status, moving a ticket to Pending at the right moment also protects the team from an unfair SLA breach while genuinely waiting on someone else.
How Do You Manage Multiple Tickets at Once With Scenarios and Bulk Actions?
Updating tickets one at a time becomes impractical once a queue grows past a handful of open items, so Freshservice offers two related ways to act on several tickets simultaneously. Bulk Update lets an agent select up to 30 tickets from the list view and change shared fields, such as status, group, or agent, in a single action, though it cannot attach a private or public note.
Scenario Automation takes this further: once configured under Admin > Automation & Productivity > Scenario Automation, a single click can apply several actions together, such as setting priority, tagging the ticket, and notifying a group, and it can be triggered on the same batch of up to 30 selected tickets.
| Method | What It Can Do | Limit |
| Bulk Update | Change one or more shared fields like status, group, or agent across selected tickets | Up to 30 tickets per action |
| Scenario Automation | Execute several predefined actions, such as tagging, reassigning, and notifying, with one click | Up to 30 tickets per action |
How Do You Merge Duplicate Tickets in Freshservice?
Users often create duplicate tickets. This happens when two coworkers report the same issue separately. It can also happen when a requester sends a new email about an existing problem instead of replying to the original ticket thread. Freshservice handles this through ticket merging rather than manual deletion. From the primary ticket’s detail view, an agent clicks More and selects Merge, then chooses which other open tickets should be folded into it.
Once merged, all conversations from the secondary tickets move into the primary ticket in chronological order, the secondary tickets close automatically, and a note documenting the merge is added so the history remains traceable. Because the merge action cannot be undone, it is worth double-checking that the selected tickets genuinely describe the same issue before confirming it.
How Can Freddy AI Help Agents Manage Tickets Faster?
Reading through a long ticket thread before acting on it eats into the time an agent has to actually resolve the issue. Freshservice addresses this with Freddy AI Copilot’s summarize option, available directly from the ticket details page. Clicking Summarize with Freddy AI Copilot generates a short summary based on the ticket’s subject, description, and full conversation history, giving the agent the gist of the situation without scrolling through every reply. If circumstances change during the ticket lifecycle, agents can regenerate the summary from the same panel at any time. This allows them to keep the overview up to date. As the conversation grows and new information appears, the summary reflects the latest developments.
Conclusion
Creating and managing tickets in Freshservice is less about any single screen and more about the habits built around it: filling in the fields that matter, letting the priority matrix do the judgment calls, and using scenarios or bulk actions instead of repeating the same update dozens of times. Once those habits are in place, a ticket queue stops feeling like an inbox and starts behaving like an actual workflow.
Teams that want to see this in their own environment can start a trial of Freshservice ITSM Software directly and test the ticket creation and management flow against a handful of real requests before rolling it out more broadly.
Frequently Asked Questions
An Incident represents something that has broken or stopped working, such as a network outage. A Service Request represents a planned request, such as asking for a new laptop. Both begin as tickets. However, teams can route them differently and apply different approval workflows to each type.
Yes, an agent can reopen a Closed ticket. To do this, they change its status to Open or In Progress in the Properties panel. After reopening the ticket, they should review any SLA timers or automations linked to the status. They may need to adjust these settings to match the ticket’s new state.
Both Bulk Update and Scenario Automation cap out at 30 tickets per action from the list view, so larger batches need to be split into multiple rounds or handled through the Freshservice API or a scheduled workflow instead.
