Back to Documentation |

Departments & Categories

Departments & Categories

Organize your support structure with departments and categories to ensure tickets reach the right team and maintain efficient workflows.

Understanding Departments

Organizational units that group agents by expertise, function, or location

Department Purpose

Departments are organizational units that group agents by expertise, function, or geographical location to ensure tickets are handled by the most qualified team members.

Why Use Departments?

Expertise-Based Routing
  • Technical issues go to IT specialists
  • Billing questions reach accounting teams
  • Sales inquiries connect with sales staff
  • HR requests route to human resources
Workload Distribution
  • Balance ticket volume across teams
  • Prevent agent overload in busy periods
  • Enable specialized training and development
  • Maintain service quality standards
Performance Tracking
  • Department-specific metrics and KPIs
  • Team performance comparisons
  • Resource allocation insights
  • Training needs identification

Department Structure Examples

By Function
📁 Technical Support
├── Level 1 (Basic Issues)
├── Level 2 (Advanced Issues)
└── Level 3 (Escalations)
📁 Customer Service
├── General Inquiries
├── Account Management
└── Billing Support
📁 Sales Support
├── Pre-Sales
├── Demos & Trials
└── Renewals
By Product Line
📁 Software Product A
📁 Software Product B
📁 Hardware Division
📁 Cloud Services
📁 Professional Services
By Geography
🌎 North America Support
🌍 European Support
🌏 Asia-Pacific Support
🌎 Latin America Support

Best Practice

Start with 3-5 main departments and expand as your team grows. Too many departments can confuse customers and complicate routing.

Setting Up Departments

Complete configuration guide for creating and managing departments

Department Configuration

Creating New Departments

Basic Department Setup:
1
Navigate to Admin → Settings → Departments → Add New
2
Enter department information:
  • Name: Clear, customer-friendly name
  • Description: Internal purpose and scope
  • Email Address: Dedicated email for ticket routing
  • Display Order: Position in customer-facing lists
3
Configure visibility settings:
  • Public: Visible to customers in portal
  • Private: Internal departments only
  • Restricted: Limited customer access

Department Properties

Contact Information:
Primary Email: [email protected]
Phone Number: Direct department line
Manager: Department supervisor or lead
Location: Physical or virtual office location
Operational Settings:
Business Hours: Department availability schedule
Timezone: Local operating timezone
Auto-Assignment: Enable automated ticket routing
SLA Settings: Department-specific service levels
Email Integration:
Incoming Email: Monitor specific email addresses
Email Templates: Department-specific responses
Signature: Standardized email signatures
Auto-Reply: Acknowledgment messages

Department Hierarchies

Parent-Child Relationships

Hierarchical Structure Benefits:
  • • Logical organization of related departments
  • • Simplified reporting and analytics
  • • Escalation path clarity
  • • Resource sharing between related teams
Example Hierarchy:
📁 Customer Support (Parent)
├── General Support (Child)
├── Technical Support (Child)
│ ├── Software Support (Grandchild)
│ └── Hardware Support (Grandchild)
└── Billing Support (Child)

Inheritance Rules

Settings Inheritance:
  • • Child departments inherit parent settings by default
  • • Override specific settings at child level
  • • Business hours cascade from parent
  • • SLA rules can be department-specific
Permission Inheritance:
  • • Agents with parent access can view child tickets
  • • Child-only agents restricted to their department
  • • Managers can oversee entire department trees
  • • Reporting includes hierarchical views

Department Email Routing

Email-to-Ticket Integration

Setup Process:
1
Create Email Address: [email protected]
2
Configure Mailbox: Connect to helpdesk system
3
Set Routing Rules: Auto-assign to department
4
Test Integration: Send test emails and verify routing
Email Processing Rules:
  • • Incoming emails create tickets automatically
  • • Subject line becomes ticket title
  • • Email body becomes ticket description
  • • Attachments preserved and accessible
  • • Reply-to addresses maintained

Advanced Email Features

Email Parsing:
  • • Extract priority from subject keywords
  • • Identify customer from sender address
  • • Parse custom fields from email headers
  • • Route based on recipient address
  • • Handle email signatures and disclaimers
Email Security:
  • • Spam filtering and validation
  • • Whitelist/blacklist management
  • • Encryption support (TLS/SSL)
  • • Anti-phishing protection
  • • Archive email communications

Email Setup

Use dedicated email addresses for each department to ensure proper routing and maintain professional communication.

Category Management

Classify and organize tickets by issue type for better tracking and automation

Understanding Categories

Category vs. Department

Departments

WHO handles the ticket (which team)

Categories

WHAT type of issue it is (classification)

Example Combinations:
Technical Support + Software Bug
Billing + Payment Issue
Sales + Product Demo

Category Benefits

Organization
  • • Standardized issue classification
  • • Consistent reporting across departments
  • • Trend analysis and pattern recognition
  • • Knowledge base organization
Automation
  • • Category-based routing rules
  • • Priority assignment based on category
  • • Template responses for common categories
  • • Escalation triggers by category type
Analytics
  • • Most common issue types
  • • Category resolution times
  • • Department performance by category
  • • Seasonal category trends

Creating Categories

Category Setup Process

Basic Category Information:
1
Navigate to Admin → Settings → Categories → Add New
2
Enter category details:
  • Name: Clear, descriptive category name
  • Description: Detailed explanation of scope
  • Color: Visual identifier in reports
  • Icon: Graphical representation
3
Configure settings:
  • Active: Enable/disable category
  • Public: Visible to customers
  • Default Priority: Automatic priority assignment
  • Parent Category: For subcategory creation

Category Examples

Technical Categories:
Software Installation
Hardware Issues
Network Problems
Performance Issues
Security Concerns
Integration Support
Service Categories:
Account Setup
Billing Questions
Feature Requests
Training Requests
Documentation Updates
Policy Questions
Process Categories:
Bug Reports
Change Requests
Access Requests
Compliance Issues
Vendor Management
Project Support

Category Hierarchies

Multi-Level Categories

Hierarchical Organization:
🔧 Technical Support
├── 💻 Software Issues
│ ├── Installation Problems
│ ├── Configuration Issues
│ └── Performance Problems
├── 🖥️ Hardware Issues
│ ├── Equipment Failure
│ ├── Connectivity Problems
│ └── Replacement Requests
└── 🌐 Network Issues
├── Internet Connectivity
├── VPN Problems
└── Security Issues

Category Navigation

Customer Experience:
  • • Progressive category selection
  • • Visual category trees
  • • Search within categories
  • • Popular categories featured
  • • Recent selections remembered
Agent Experience:
  • • Quick category assignment
  • • Category suggestion based on content
  • • Bulk category changes

Best Practices Checklist

Category Management

  • • Keep category names clear and descriptive
  • • Limit hierarchy depth to 3 levels maximum
  • • Regular review of category usage
  • • Archive unused categories
  • • Train staff on category standards

Performance Metrics

  • • Category performance metrics
  • • Historical category usage
  • • Department workload balance
  • • Resolution time by category
  • • Customer satisfaction scores

Routing Rules

Automate ticket assignment with intelligent routing based on department, category, and agent skills

Automatic Routing

Rule-Based Assignment

Routing Criteria:
Department Selection

Customer or system chooses department

Category Matching

Route based on issue type

Keyword Detection

Scan subject/description for keywords

Customer Properties

VIP status, account type, location

Time-Based Rules

Business hours, day of week

Common Routing Scenarios:
Priority-Based Routing:
IF
Priority = "Urgent"
THEN
Assign to "Senior Agent Queue"
ELSE
Assign using "Round Robin"
Skill-Based Routing:
IF
Category = "Database Issues"
AND
Department = "Technical Support"
THEN
Assign to agents with "Database" skill
Customer-Based Routing:
IF
Customer.Type = "Enterprise"
THEN
Assign to "Enterprise Support Team"
AND
Set Priority = "High"

Load Balancing

Distribution Methods

Round Robin
  • • Distribute tickets evenly among available agents
  • • Simple and fair distribution
  • • Good for teams with similar skill levels
  • • Prevents any single agent from being overloaded
Skill-Based Assignment
  • • Match ticket requirements to agent expertise
  • • Improve resolution times and quality
  • • Enable specialization and development
  • • Handle complex issues more effectively
Workload Balancing
  • • Consider current agent ticket counts
  • • Factor in ticket complexity and priority
  • • Account for agent availability and capacity
  • • Optimize overall team performance

Agent Availability

Status Management:
Available: Ready for new assignments
Busy: Working on current tickets
Away: Temporarily unavailable
Offline: Not accepting new tickets
Capacity Planning:
  • • Maximum tickets per agent
  • • Skill-based capacity limits
  • • Priority-based reservations
  • • Overtime and weekend coverage

Custom Routing Logic

Create advanced routing rules for complex ticket assignment scenarios

Advanced Routing Rules

Complex Conditions

Complex Routing Example:
IF
(Customer.Region = "North America"
AND
Time.BusinessHours = TRUE)
OR
(Priority = "Urgent"
AND
Department = "Technical")
THEN
Assign to "NA Business Hours Team"
ELSE
Assign to "Global Support Team"
Multi-Factor Routing:
  • • Customer tier + Issue category + Time zone
  • • Agent skills + Current workload + Priority
  • • Department capacity + SLA requirements + Escalation level

Rule Testing & Optimization

Testing Methods:
  • • Dry run with historical tickets
  • • A/B testing with rule variations
  • • Performance monitoring and adjustment
  • • Agent feedback on routing accuracy
Optimization Strategies:
  • • Regular rule performance reviews
  • • Adjust based on resolution time data
  • • Update skills and capacity settings
  • • Refine keyword and category matching

Optimization Tip: Monitor routing effectiveness weekly and adjust rules based on resolution times, customer satisfaction, and agent feedback.

Department Analytics

Monitor and analyze department performance with comprehensive metrics and reporting

Performance Metrics

Key Performance Indicators

Volume Metrics
  • • Total tickets handled per department
  • • New tickets vs. resolved tickets
  • • Ticket backlog and aging
  • • Peak volume times and patterns
  • • Seasonal trends and variations
Efficiency Metrics
  • • Average resolution time by department
  • • First contact resolution rate
  • • Escalation rates to other departments
  • • Agent utilization and productivity
  • • SLA compliance percentages
Quality Metrics
  • • Customer satisfaction scores
  • • Ticket reopen rates
  • • Quality assurance scores
  • • Knowledge base article usage
  • • Customer effort scores

Departmental Comparisons

Benchmark Analysis:
  • • Compare department performance metrics
  • • Identify best practices and improvement areas
  • • Resource allocation insights
  • • Training needs assessment
  • • Goal setting and target achievement

Category Analytics

Issue Trend Analysis:
  • • Most common issue categories
  • • Category resolution time analysis
  • • Seasonal category variations
  • • Emerging issue identification
  • • Category migration patterns
Knowledge Gap Identification:
  • • Categories with high resolution times
  • • Frequent escalation categories
  • • Low satisfaction score categories
  • • Categories needing documentation
  • • Training opportunity categories

Reporting Dashboard

Real-Time Monitoring

Live Dashboard Features:
  • • Current ticket queues by department
  • • Agent availability and workload status
  • • SLA breach alerts and warnings
  • • Escalation notifications
  • • Performance trend indicators

Historical Reports

Comprehensive Analytics:
  • • Monthly and quarterly performance reports
  • • Year-over-year trend comparisons
  • • Department efficiency analysis
  • • Category distribution reports
  • • Customer satisfaction trends
Customizable Reports:
  • • Filter by date ranges, departments, categories
  • • Export to CSV, PDF, or Excel formats
  • • Scheduled automatic report generation
  • • Custom metric combinations
  • • Drill-down capabilities for detailed analysis

Department Organization Checklist

Define clear department purposes and boundaries
Set up department email addresses and routing
Create comprehensive category structure
Configure automatic routing rules
Assign agents to appropriate departments
Test routing and escalation procedures
Set up monitoring and analytics dashboards
Train staff on department procedures

Calculate Your Savings

See how much you can save with Loopdesk compared to leading competitors

agents in your team
1 25 50 75 100

Provider A

/year

Provider B

/year

Provider C

/year
BEST VALUE

Loopdesk

/year
Best Price!

Your Potential Annual Savings

vs Provider A
vs Provider B
vs Provider C