Case study · Technical support

Help desk routing for MSPs

Company-reported case study

Actigy BPO handled service-desk routing for Ridgeway IT Services. Reported first-contact resolution moved from 52% to 84% over five months, with the managed service provider retaining service ownership.

Actigy BPO confirms the engagement and supporting records. Results apply to the stated scope and measurement windows.

First-contact resolution

Result

84%

Baseline: 52%

Window: 5 months

Supporting record: ServiceNow report

Misrouted tickets

Result

4.1%

Baseline: 18%

Window: 5 months

Supporting record: ServiceNow report

Average resolution time

Result

3.2 hours

Baseline: 9.4 hours

Window: 5 months

Supporting record: ServiceNow report

Client profile

Ridgeway IT Services, a UK managed service provider with 600 staff.

Challenge and scope

Eighteen percent of tickets are assigned to the wrong team in the baseline, adding a handoff before troubleshooting starts.

A desk supporting several customers and applications can receive the same symptom under different service contracts. Routing based on the description alone can miss the supported team, entitlement, or impact. Each reassignment adds elapsed time and can generate several separate updates to the same user.

Delivery workflow

Triage and route 4,800 monthly tickets across 14 applications and three languages. Use routing rules and approved diagnostics, and raise change requests under the provider’s escalation process.

Confirm the service, customer, and entitlement in the authorized record before assigning the ticket in ServiceNow. Apply the MSP’s categories for impact and urgency and run the approved first-line checks. Give the receiver a summary of the steps already taken and any relevant monitoring event.

Record any rejected or reassigned ticket and capture the reason, such as unclear ownership, missing data, or incorrect priority. Review these cases against the routing matrix with the MSP. Update the instructions when application ownership changes and keep the client’s change and security escalation process visible.

Delivery team

Bulgaria, about 20 FTE. 1 service desk lead, 3 team leads and 16 service desk analysts.

Systems and tools

ServiceNow, Jira, client monitoring tools.

Client decision rights

The provider owns change approval, security incident command, and infrastructure decisions.

Early milestone

The week 4 record puts first-contact resolution at 66%.

Outcomes

Company-reported results, with the baseline, measurement window and supporting record described for each measure.

Reported results: Help desk routing for MSPs
MeasureBaselineResultWindowSupporting record
First-contact resolution52%84%5 monthsServiceNow report
Misrouted tickets18%4.1%5 monthsServiceNow report
Average resolution time9.4 hours3.2 hours5 monthsServiceNow report
Customer satisfaction (CSAT)3.7/54.5/55 monthsServiceNow report

Interpreting the results

First-contact resolution and misrouting can be measured on the same support population if reassignments and reopens are counted consistently. Compare resolution times by priority and application, and distinguish tickets that needed a client approval or specialized team input. Interpret satisfaction in the context of contact mix.

Recommendations for new clients

For MSPs with routing errors, define first-contact resolution across channels. Sample assignments and verify that quick resolutions do not lead to repeat tickets.

Start with a mix of everyday requests and faults across a few supported applications. Share the service catalog, entitlement and routing matrix, and approved diagnostic access. Review examples of correct first-line closure and escalation with the MSP’s technical owner before adding contracts or shift coverage.

Scope this workflow for your operation

Use the documented workflow, client-held decisions and operational checks to outline a pilot for your own workload.