Case study
MyHyve Ticketing Portal
A monthly support-ticket automation for stray orders at Hyve Managed Hosting, built into the production Angular and C# ticketing portal.
The problem
Stray orders needed a monthly check to become support tickets. Some maintenance tasks were recorded under the wrong category, so the team did not see them as maintenance work.
What I built
I built and deployed the workflow across the Angular portal and its C# backend. On each monthly run it checks for stray orders, creates a ticket for each one and sends the ticket to support review. Customer Experience validated the workflow after rollout.
-
1. Monthly check
Stray order #1042
Sample customer
-
2. Ticket creation
Ticket #1042 created
Queued for support
-
3. Support review
Stray order reviewed
Maintenance task flagged
Illustrative workflow with fictional data.
After rollout
The workflow surfaced maintenance work the team had been missing. It also gives each stray order a repeatable route into a support ticket and a support-review step.
Separate example: modernising the portal
The monthly workflow sat alongside a wider modernisation of the same portal. I led the Angular 19→21 upgrade and cut npm audit findings from 50+ to under 5, including three of four critical issues. The portal adopted Angular signals and rxResource, and I replaced legacy Sass with Tailwind. I also reorganised related components into feature-oriented modules.
This case study uses only details that can be stated without internal customer, order or ticket data.