Scenario: Organize request processing via Service Desk

This scenario helps you set up support service processes and organize request handling in BRIX Service Desk. You will set up intake channels, fill in required catalogs, define operator groups and routing rules, organize operator workflows, and enable analytical monitoring.

For example, employees can submit requests to IT support to report incidents, request access permissions, or ask questions about services. Requests arrive in Service Desk, get categorized, are assigned to assignees, and are processed through to resolution.

This scenario outlines the general setup logic and does not replace detailed instructions. Each step includes links to help articles with detailed procedures.

Before you begin

Before starting the configuration, define the following parameters:

  • Request typology. Types of requests processed by operators: incidents, service requests, questions, or requests regarding specific services.
  • Request sources. Channels through which users and clients submit requests: website forms, external portals, email, or messaging apps.
  • Categorization parameters. Categories, services, priorities, and statuses required to group requests.
  • Support structure. Support lines and expert operator groups that process requests and resolve incidents.
  • Routing rules. Methods for distributing requests among assignees: automated assignment by parameters, workload-based routing, or manual queue triage.
  • Resource planning. Need for work schedules, shift management, and tracking assignee availability.
  • Performance analytics. Key metrics to monitor on custom dashboards: response and resolution SLAs, overdue tasks, team workload, and other performance indicators.

Step 1. Define request handling scenarios

First, define your support process requirements and determine which BRIX Service Desk features are needed to implement them.

Examples of basic workflows:

  • An employee reports a technical failure > an incident is registered > processing time is determined based on request priority.
  • A client submits a service request via the external portal > the request is routed to a dedicated live chat.
  • Multiple users report server connectivity issues at the same time > an operator registers a major incident and links the requests to a single root cause.

Based on these scenarios, select the required tools: request intake channels, feedback forms, a client portal, core catalogs, automated routing rules, and reporting dashboards.

Начало примечание

Useful articles:

Конец примечание

Step 2. Set up initial Service Desk configuration

Prepare the solution for operation: enable the required modules, fill in catalogs, and configure workspace settings.

Catalogs help categorize requests, maintain a unified service catalog, and standardize incident categories, priorities, canned responses, and other operational data.

For example, for IT support, you can set up incident categories such as Access Permissions, Workstation, Email, Hardware, and Business Applications.

Начало примечание

Useful articles:

Конец примечание

Step 3. Configure support groups

Build your service team structure: assign roles and groups to users handling requests, and define their areas of responsibility.

For example, you can set up the following role-based support structure:

  • First line. Operators handle incoming requests, answer basic inquiries, and escalate complex issues to specialized groups.
  • Second and third lines. Specialists resolve complex technical incidents and fulfill service requests.
  • Supervisors. Oversee request distribution, monitor critical incidents, and balance workload across lines.
  • Support manager. Analyzes efficiency, manages Service Level Agreements (SLA), and monitors overall service quality.

Support groups are required for routing requests, assigning task execution, and controlling operational workflows.

Начало примечание

Useful articles:

Конец примечание

Step 4. Configure request intake channels

Define how users and clients submit requests.

Requests can arrive via website forms, email, messaging channels, or the Service Desk portal.

Requests submitted through the portal are logged in Service Desk automatically. External channels in BRIX connect to live chats. For each live chat, you can configure multiple intake channels, specify target storage locations, and assign designated operators. Requests submitted through the portal are logged in Service Desk automatically.

For example, internal employees can submit hardware issues through an internal live chat, while external clients send requests via email or the Service Desk portal.

Начало примечание

Useful articles:

Конец примечание

Step 5. Configure request processing and routing

Define routing rules to direct requests to the appropriate support group or designated operator.

Processing rules distribute requests based on criteria such as service, category, priority, or source. For each rule, you can specify routing target rules or SLA targets.

If automated routing is not sufficient, requests can be assigned manually.

For example, hardware requests can be routed to the Workstation Support Group, while business application issues go to Second-Line Support.

Начало примечание

Useful articles:

Конец примечание

Step 6. Configure duplicate management, problem management, and schedules

If Service Desk frequently receives duplicate or related requests, establish procedures for handling duplicate requests and managing problems. For example, if multiple users report that a specific service is unavailable, link those requests to a single problem.

If request resolution depends on shifts, business hours, or employee availability, set up work schedules.

Начало примечание

Useful articles:

Конец примечание

Step 7. Configure analytics and operational control

Determine the key metrics to track: request volumes, assignee workload and overall activity, statuses, resolution times, request distribution by category, and service quality.

For instance, a Service Desk manager can monitor incoming request volume over time, track distribution by category, identify peak load times, prevent queue backlogs, and evaluate individual operator performance.

Начало примечание

Useful articles:

Конец примечание

Step 8. Verify request workflow

After completing configuration, perform an end-to-end test of request processing from creation to resolution. Test workflows across different user roles: requester, operators from various support lines, supervisor, and support manager (not just Administrator).

Success criteria:

  • A user can submit a request through every configured intake channel.
  • The request item page contains all necessary fields and attachments.
  • Category, priority, target SLA time, and support group are assigned correctly.
  • An operator sees the request in their queue and can pick it up, reassign it, or complete it.
  • Related requests can be linked to a root problem.
  • Managers can track operational indicators via reports and dashboards.
  • Users only have access to requests permitted by security settings.

Начало примечание

Useful articles:

Конец примечание

Workflow summary

  1. Define request handling scenarios.
  2. Set up initial Service Desk configuration.
  3. Configure support groups.
  4. Configure request intake channels.
  5. Configure request processing and routing.
  6. Configure duplicate management, problem management, and employee schedules if needed.
  7. Set up operational control.
  8. Verify the end-to-end request workflow from creation to resolution.