Ticket Management
Master the complete ticket lifecycle from creation to resolution with Loopdesk's powerful ticketing system.
Creating Tickets
Manual Ticket Creation
From Admin Panel
Automatic Ticket Generation
Ticket Information Fields
Required Fields
Optional Fields
Best Practice
Use descriptive subjects that summarize the issue. Good: "Login error after password reset" Bad: "Problem with account"
Ticket Lifecycle
Status Progression
Open (Initial State)
- • Newly created or reopened tickets
- • Ready for agent assignment
- • Customer can add information
- • SLA timer starts
Pending
- • Waiting for customer response
- • Additional information requested
- • SLA timer paused
- • Automatic reminders can be set
Resolved
- • Solution provided to customer
- • Awaiting customer confirmation
- • Can be reopened if unsatisfactory
- • SLA timer stopped
Closed
- • Issue fully resolved
- • Customer confirmation received
- • Final state in most workflows
- • Can be reopened if needed
Advanced Status Options
Some organizations use additional statuses:
Status Change Rules
Automated Changes
- Open → Pending: When requesting customer info
- Pending → Open: When customer responds
- Resolved → Closed: After customer confirmation or timeout
- Any → Open: When customer reopens
Manual Changes
- Agents can move between any statuses
- Status history is tracked
- Automatic notifications sent on changes
Priorities & Status
Priority Levels
Low Priority
- • Minor issues or requests
- • Standard response time: 24-48 hours
- • Examples: Feature requests, cosmetic issues
- • SLA: Flexible based on workload
Normal Priority (Default)
- • Standard business issues
- • Response time: 8-12 hours business days
- • Examples: General questions, minor bugs
- • SLA: Standard support agreement
High Priority
- • Significant business impact
- • Response time: 2-4 hours
- • Examples: System errors affecting multiple users
- • SLA: Expedited handling required
Urgent Priority
- • Critical business functions affected
- • Response time: 30 minutes - 1 hour
- • Examples: System outages, security issues
- • SLA: Immediate attention required
Priority Assignment Guidelines
Factors to Consider
-
Impact: How many users affected?
-
Urgency: Time sensitivity of the issue
-
Business Value: Revenue or operational impact
-
Customer Tier: VIP or enterprise customers
-
Time of Day: Business hours vs. after hours
Automatic Priority Rules
- Keywords in subject/description
- Customer tier or account type
- Time since last response
- Department or category defaults
- Email sender priority
Important
Train your team on consistent priority assignment. Mixed priorities can lead to SLA violations and customer dissatisfaction.
Assigning Tickets
Assignment Methods
Manual Assignment
Automatic Assignment
Self-Assignment
Assignment Rules Configuration
Setting Up Automation Rules
- • Department equals "Technical Support"
- • Category contains "Software"
- • Priority is "High" or "Urgent"
Advanced Assignment Logic
Conditional Assignment:
Time-Based Assignment:
- • Business hours: Assign to primary team
- • After hours: Assign to on-call agent
- • Weekends: Route to weekend support team
Managing Agent Workload
Workload Balancing
- View agent ticket counts in real-time
- Redistribute tickets when agents are overloaded
- Set maximum tickets per agent
- Monitor response time performance
Agent Availability
- Mark agents as available/unavailable
- Vacation and sick leave management
- Skill-based availability
- Department coverage requirements
Bulk Operations
Selecting Multiple Tickets
Selection Methods
Bulk Action Options
Status Changes
- • Mark as Resolved
- • Close tickets
- • Reopen closed tickets
- • Set to Pending
Assignment Operations
- • Assign to specific agent
- • Assign to department
- • Remove assignments
- • Reassign from one agent to another
Priority Updates
- • Increase priority
- • Decrease priority
- • Set specific priority level
- • Reset to default priority
Organizational Actions
- • Add tags
- • Remove tags
- • Change category
- • Move to different department
Communication
Bulk Operation Examples
End of Week Cleanup
Department Reorganization
Priority Adjustment
Tip
Use bulk operations for routine maintenance like closing old resolved tickets or reassigning during staff changes.
File Attachments
Supported File Types
Security Features
File Validation
- Virus scanning on upload
- File type verification
- Size limit enforcement (10MB per file)
- Content inspection for security
Access Control
- Customers see only their attachments
- Agents can see all ticket attachments
- Download logging and audit trail
- Secure file storage with encryption
Storage Management
- Automatic file cleanup policies
- Archive old attachments
- Storage quota management
- CDN integration for performance
Best Practices
For Customers
- Compress large files before uploading
- Use descriptive filenames
- Include screenshots for visual issues
- Remove sensitive information
For Agents
- Download and verify file content
- Share internal documentation securely
- Use attachments for proof of resolution
- Maintain file organization
File Management Interface
Upload Process
Organization Features
- Group attachments by type
- Sort by date, size, or name
- Search within attachment names
- Preview supported file types
- Batch download multiple files