A structured ticketing process for IT support
What happens to an IT request when the person who usually helps is away?
At the DAAD, requests often went to the last person who helped. If that person was away, the team had to reconstruct the history. Frequent questions about the SAP portal were answered one at a time.
I helped introduce a central ticketing system with clear ownership. Calls, emails and forms could reach the right team. We recorded standard solutions to recurring questions so colleagues could provide cover.
€m
Annual revenue · Standardised support processes help coordinate varied requests and the work involved in resolving them.
Process model
Employees · Capture recurring requests centrally, share service knowledge and reduce pressure on support teams.
Traceable ticket handling
Improve services
Capture IT requests centrally, assign them to the right teams and make reusable solutions available.
Reliable support
01 · OBJECTIVES
Project objective
The goal was central intake and handling of internal and external IT requests. Clear ownership, structured reporting and automated replies were intended to ease staffing pressure and improve service quality.
The service needed to work reliably when responsibilities changed and staff were absent. The team needed access to request histories and shared knowledge.
02 · IMPLEMENTATION
Approach
- Introduce a central ticketing system with defined support groups.
- Route requests by responsibility and record how they are resolved.
- Record standard answers and guidance for recurring questions.
- Bring cross-team work into the shared service process.
Technical implementation went hand in hand with a common workflow. Intake, routing, feedback and escalation were designed as parts of one service process.
03 · CHALLENGE
Challenge
Requests arrived through different channels, often directly with individual staff. This limited visibility and knowledge sharing. The rollout also had to address concerns about performance monitoring and dependence on particular individuals.
The technology and the way of working both had to change. Support teams and people raising requests needed to see the value of central intake.
04 · IMPACT
Benefits
Requests were recorded centrally, assigned and escalated where necessary. Recurring incidents became easier to identify and resolve using stored solutions. Shared records made it easier to provide cover across teams.
The team could also analyse support more effectively by grouping individual requests and using recurring themes to improve the service.
PROJECT BACKGROUND
Context and implementation
Project context
The DAAD is an international academic exchange organisation supported by German universities and student bodies. Its IT supports internal work and specialist applications for external users.
The project covered shared systems, email, internet services and an SAP portal for applications and assessments. These different audiences needed dependable, accessible support.
My contribution
I helped introduce a central ticketing system that brought together previously separate support contacts. Requests sent through an intranet form, a shared email address or by phone could be recorded consistently and routed to the appropriate team.
Reusable answers were a design priority. We provided consolidated solutions, attachments and links to the online manual for common SAP portal questions. Early replies pointed people to relevant help as soon as a request arrived.
Starting point
Internal requests often went to whoever had helped most recently, regardless of responsibility or availability. Email, phone and other channels led to inconsistent handling and made cases difficult to track.
External SAP portal users also asked many recurring questions, which were answered individually. This made it difficult to analyse patterns and causes.
Results and impact
Central handling helped the team group recurring incidents and investigate underlying problems. Standard answers reduced effort and supported consistent service.
Shared information made it easier to cover holidays and sickness. It also provided a basis for better reporting and for bringing external providers into the support process later.
Further reading
ITIL5: Alles was man wissen muss
Services, processes and value creationIT, AI, GOVERNANCE & MANAGEMENTLet’s stay in touch
Would you like to discuss any of these topics?



