In Smart Support, Products and Departments are two key components that work together to ensure tickets are categorized correctly, routed efficiently, and handled by the right agents. This structure helps teams organize support operations around both business areas (departments) and specific offerings (products).

Understanding Departments

• Definition: A department represents a category of support responsibility, such as Technical Support, Sales, Billing, or General Support.
• Purpose: Departments allow organizations to divide customer requests into manageable groups, each typically staffed with specialized agents.
• Examples:
  • Technical: Handles bug reports, configuration issues, software problems
  • Sales: Manages inquiries about purchases, subscriptions, upgrades
  • Billing: Resolves payment issues, invoices, refunds
  • Support: Provides general guidance, troubleshooting, or onboarding help

Understanding Products

• Definition: A product is a specific item, service, or solution offered by your business that customers may need support for.
• Purpose: Products allow customers to indicate exactly what they need help with, ensuring requests are highly specific.
• Examples:
  • Software Application A
  • Plugin or Add-on B
  • Hardware Device C
  • Service Package D

How They Work Together

1. Relationship Between Products and Departments

• One-to-Many: A single department can handle multiple products.
• Exclusive Belonging: Each product is linked to one department (though it can also exist without being linked).
• Unassigned Products: If a product is not linked to a department, it appears universally across all departments.

This structure provides both flexibility and clarity:

• Businesses can assign products to specialized teams.
• General or cross-department products remain visible everywhere.

2. Ticket Creation Process

When a user creates a ticket:

1. Department Selection – The user first chooses the department relevant to their issue.
2. Product Filtering – The system automatically filters the product list:
   • Shows only products belonging to the chosen department
   • Includes any products available to all departments (unassigned)
3. Product Selection – The user then chooses the product they need help with.

This ensures the ticket is categorized correctly on two levels:

• By Department (broad responsibility area)
• By Product (specific item or service)

3. Benefits of the Relationship

• Organized Support: Requests are clearly divided into categories.
• Efficient Routing: Tickets quickly reach the right team.
• Agent Specialization: Agents become experts in certain product–department areas.
• Better Reporting: Analytics can be run by department, product, or both.
• Flexibility: Products can be reassigned if internal workflows change.

4. Agent and Workflow Impacts

• Auto-Assignment: Tickets are automatically assigned to agents within the correct department.
• Agent Visibility: Agents only see tickets for their department.
• Workload Distribution: Departments ensure even distribution of tickets to the right staff.

5. Example Workflow

1. A customer selects Technical Department when creating a ticket.
2. The system filters the list to show technical-related products plus general products.
3. The customer selects “Software Bug Report” as the product.
4. The ticket is created and automatically assigned to a Technical Department agent.
5. The assigned agent resolves the ticket, while analytics later show how many “Software Bug Report” tickets were handled by the Technical team.