Overview
This glossary explains common Helpdesk terms in simple and practical language so new users can understand screens and instructions faster. It is designed to remove confusion when people see unfamiliar words in tickets, reporting, settings, or portal workflows. Keeping a shared understanding of terms helps teams communicate better and work more consistently.
How It Works
Each term is presented with a plain-language definition and a real-world example to make learning easier for non-technical users. You can quickly scan the table whenever you get stuck, then return to your task with confidence. These definitions are written for day-to-day operations and onboarding, not for technical development use.
Step-by-Step Guide
- Open this glossary when you see an unfamiliar word.
- Find the term in the table below.
- Read the meaning and example.
- Go back to your ticket and continue with confidence.
Fields Table
| Field Name | Description | Example |
|---|---|---|
Ticket |
A support request raised for a customer issue. |
Customer reports payment failure. |
Ticket Number |
Unique reference ID for one ticket. |
TIC/2026/0127 |
Status |
Current stage of ticket progress. |
Assigned, In Progress, Resolved |
Priority |
How urgent the ticket is. |
Urgent issue for production outage |
SLA |
Service time commitment for response and resolution. |
Respond within 2 hours |
Escalation |
Sending a ticket to higher support level when needed. |
L1 team escalates to L2 specialist |
Category |
Main topic group for the issue type. |
Billing, Technical, Account Access |
Tag |
Extra label for filtering and reporting. |
VIP Customer |
Channel |
Source from which ticket came in. |
Email, Phone, Social Media |
Assignment |
Action of giving ticket ownership to an agent. |
Assigned to Rahul |
Reminder |
Scheduled follow-up alert for a ticket action. |
Follow up tomorrow at 9:00 AM |
Knowledge Base |
Library of reusable help articles and FAQs. |
Password reset article |
Linked Record |
Related business data connected to a ticket. |
Linked invoice or sales order |
Merge |
Combining duplicate tickets into one. |
Two same complaint tickets merged |
Split |
Breaking one complex ticket into smaller tickets. |
One ticket split into billing + delivery issue |
Portal |
Customer-facing page to submit and track tickets. |
Customer checks ticket status online |
Notification Preference |
User choice for alert types and channels. |
Email only for SLA breaches |
Resolution Time |
Total time taken to fully solve a ticket. |
Resolved in 6 hours |
Response Time |
Time until first reply to customer. |
First response sent in 45 minutes |
SLA Breach |
Ticket that missed SLA commitment. |
No response within agreed 2 hours |
Fields Explanation
Ticket
Core unit of support work.
Ticket Number
Best way to reference a case quickly.
Status
Shows progress at a glance.
Priority
Helps teams focus on urgent issues first.
SLA
Defines expected service quality.
Escalation
Protects critical cases from delay.
Category
Organizes issue types.
Tag
Adds flexible labels for filtering.
Channel
Shows where issue came from.
Assignment
Creates clear ownership.
Reminder
Prevents missed follow-ups.
Knowledge Base
Speeds repeat issue handling.
Linked Record
Brings relevant business context.
Merge
Removes duplicate effort.
Split
Improves control of multi-part issues.
Portal
Gives customers self-service access.
Notification Preference
Reduces alert overload.
Resolution Time
Measures full completion speed.
Response Time
Measures first-contact speed.
SLA Breach
Signals missed commitments.
Tips
- Share this glossary link with new agents during onboarding.
- Use terms consistently in team communication.
- Review this page when new features are added.
Common Mistakes
- Confusing response time with resolution time.
- Marking tickets urgent when they are routine requests.
- Using tags and categories as if they mean the same thing.